Anthony Simon

Hey I'm the author of the post. We ran Panelbear for about a year before merging it into Cronitor's codebase. Cronitor is also a Django monolith but on EC2 and was already humming along nicely for several years through frequent traffic spikes. We had no reliability issues with K8s, but came down to: as a small team we decided to have less moving parts. The new setup is not too different from what I describe here: https://anthonynsimon.com/blog/kamal-deploy/

I replicated Anthony Simon's architecture [0] in a few days and it has worked beautifully so far with a toy project [1]. Probably overkill for OP, but the combination of GH Actions & Flux [2] means that starting (and killing) namespaced projects – with all the cluster benefits of automatic TLS certification, DNS record management, rate limiting, pod restarts, logging, autoscaling, CD, etc. – is a single push to a git repository. Really nice if you're taking a shotgun approach and trying different ideas quickly. [0] https://anthonynsimon.com/blog/one-man-saas-architecture/ [1] https://www.wyzetickets.com/ [2] https://fluxcd.io/

ah the solo dev tech stack! a very popular category, but this is the first one that is hardware focused. software ones i have collected: - https://draculatheme.com/pro/journey - https://www.indiehackers.com/post/launched-my-first-course-earned-over… - https://panelbear.com/blog/tech-stack/ - https://jake.nyc/words/tools-and-services-i-use-to-run-my-saas/ - https://www.listennotes.com/blog/the-boring-technology-behind-a-one-pe… - https://anthonynsimon.com/blog/one-man-saas-architecture/ - https://news.ycombinator.com/item?id=25614966