Great insights, thanks for sharing. Recently I found myself plotting how much extra time I spend on maintaining and configuring, which is basically the money vs time problem. No conclusion reached yet on my side.
Hey thanks for the tips. I think stackdriver is really eating up a lot, will probably scratch that.
These are completely unrelated projects so I'd like to avoid keeping them on the same cluster. I also created separate projects for them from the console.
+$70 per cluster wow. That's the type of news that feels like it should be next to some good news.
Do you know any way I could get my hands on Google cloud credits?
There is similar stuff to what you described in the next few hundred designs that will be uploaded. I think those 40 fields should be segmented and grouped based on relevance. It is quite scary as a user to be bombarded with so many inputs at once. The task of filling them all out gives them anxiety. Try to auto-fill whatever you have access to, try to segment as much as possible, and if you have the possibility break it down to smaller steps. If you can, show them progress and encourage them along the way. I hope that helps!
I agree. I'll look into the DO Kubernetes offering, maybe that's more sustainable. I'd really like to keep running on k8s, but if it doesn't work out... I guess I'll just have to bite the bullet and do my walk of shame back to droplets.
Thanks! The ads are on the website itself. I wrote a custom ad service for it. Currently it supports 3 types of ads. 2 native ones in the gallery, and one on the post page.
Hey thanks a lot! Yep crazy high to the point of scary high lol. It's Kubernetes on Google Cloud. It is awesome no doubt, but man ... this could be ran on a $5/mo DO droplet. Was thinking of migrating tbh.
Feedback/Critiques:
- Make the ads more distinguishable from the designs in the gallery.
- Subscribe popup on the post page comes in with delay and is annoying.
- Developers do not understand the software icons listed, they need labels.
- There was some confusion about the “open-source design” term, somebody thought it is created with open source software, instead of the design source file being available.
- Some developers don’t know how to open the source files. A tip should be included that Figma is free and it opens up most file formats.
- Find a license that is more in line with our permissive approach. Maybe public domain?
Bugs:
- 13 different bugs found in production
- 79 total errors thrown in production
- 27 users experienced issues in production
Operational Cost:
- $8 - $13 per day, most of which is egress traffic and server log storage.
Conclusion:
The soft went much better than expected, and it revealed some interesting insights about this project. We are going to make all the requested adjustments, fix the bugs, and prepare for the official launch.
Well most things still work through API calls (Postman), but the front-end for the CMS might be ready in the next couple months. Right now is the only administrative UI component is the upload form that lets my wife upload her designs.
The source file content is served from disk, and everything else from the database.