This is probably not the best place to ask this question, but as a solo founder or just to reduce costs/time are there some standard free software packages that are used when creating sites? For example most sites need a user sign up mechaism, a authN and authX mechanism to gate access to different pages. Are there open source projects that provide this? Or do site owners develop these from scratch every time?
The architecture behind a one-person tech startup
151–160 of 334 posts
Re: The architecture behind a one-person tech startup
#152Anthony - if you're reading this, thank you!! To arrive at this architecture takes 100s if not 100s of hours, and to share it with the community is dang inspiring. I was feeling a bit down on my projects, but this has me amped up seeing how the ultimate goal of working on features rather than deployment is possible, and very real! Best of luck with Panelbear!
Thank you! I appreciate it. Glad you found it helpful.
Also interested in the costs for your setup. My costs are in my other comment [1].
Re: The architecture behind a one-person tech startup
#153My one-man-SaaS setup: - Static frontend hosted on Netlify (free unlimited scale) - Backend server on Google App Engine (connecting to Gcloud storage and managed DB via magic) I realize I'm opening myself up to vendor lock-in and increased costs down the road (if I even get that far), but I've wrangled enough Docker/k8s/Ingress setups in the past to know it's just not worth the time and effort for a non-master.
What product is this?
Re: The architecture behind a one-person tech startup
#154(Render founder) This is incredible work, and underscores the reason Render exists and is recommended by OP. Everything mentioned in the post is baked into Render already: * Automatic DNS, SSL, and Load Balancing * Automated rollouts and rollbacks * Health checks and zero downtime deploys (let it crash) * Horizontal autoscaling (in early access!) * Application data caching (one-click ClickHouse and Redis) * Built-in…
Re: The architecture behind a one-person tech startup
#155A lot of people are going to jump on the "he used k8s and he doesn't even work at Google scale!" part of this writeup, but I think it's a perfect demonstration of the concept of innovation tokens [1]. He admits in TFA that clickhouse was the only new piece of tech in his stack, and he was already familiar with k8s et al - so he's able to focus on actually building the products he wants. I could see somebody unfamilia…
That said I agree with the innovation token concept. None of this junk makes you money, solve a problem first.
Re: The architecture behind a one-person tech startup
#156Earlier quoted context omitted.
That's right, I'm exaggerating. At current rates I'll hit that limit at 7.5MM pageviews/month. I've also paid for extra builds once or twice in the past (automatically charges a few dollars when you cross the build time limit), and I pay them $9/mo for analytics.
How much is 1MM? I'm unfamiliar with that suffix.
Re: The architecture behind a one-person tech startup
#157Nice read. I haven't seen any references to Ansible or similar tools. For the ones who know: given the architecture described in the article, does Ansible fit in the picture? I don't know a lot of k8s but I wonder how VMs are provisioned (e.g., how docker is installed?)
Re: The architecture behind a one-person tech startup
#158I am running a few one man saas's on a 2.99$ vps (1 per project) with php, mysql and nginx.
Re: The architecture behind a one-person tech startup
#159Re: The architecture behind a one-person tech startup
#160For my typing SaaS, I found firebase hosting/realtime DB a ginormous time saver. And since it hasn't taken off (and probably won't ever), it just costs me a pennies a month since I'm under their free limits, plus the domain.
But you should be careful if it actually does takeoff. Firebase is freaking amazing, but the pricing can get crazy expensive.
Firebase's database is a NoSQL database, whereas almost all my data for the apps and (micro-)SaaS I was building had relational data.
Their frontend data fetching felt clunky and did not fit my requirement.
Also, the fact that Firebase is a closed-source backend felt scary in the hands of Google (https://killedbygoogle.com/).
Firebase's problems and my desire to have the perfect backend made me build an open-source alternative to fix all the shortcomings. PostgreSQL instead of NoSQL. GraphQL instead of REST. 100% open source. That is now https://nhost.io.