Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The architecture behind a one-person tech startup

anthonynsimon.com

Post reply on HN
Print view View original

71–80 of 334 posts

Re: The architecture behind a one-person tech startup

#71

Post by waylandsmithers »

rory wrote: post #28

My 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.

I'm curious, as someone knows probably only enough about this stuff to get myself into trouble, what am I missing out on by just pushing to heroku?

Re: The architecture behind a one-person tech startup

#72

Post by darkhorse13 »

0xdba wrote: post #36

For 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.

Re: The architecture behind a one-person tech startup

#73

Post by sa1 »

The author almost seems to apologize for having a django monolith.

But it's worth realising that one purpose of code organisation in larger companies is to mirror the team organisation. That's a constraint on code that can interfere with the best technical architecture.

You can do better with a monolith in a one-man team!

Re: The architecture behind a one-person tech startup

#74

Post by rory »

I_am_tiberius wrote: post #56
rory wrote: post #28

My 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.

I wouldn't say Netlify has free unlimited scale. There are some limitations, especially the data transfer limit of 100GB.

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.

Re: The architecture behind a one-person tech startup

#75

Post by sammorrowdrums »

waylandsmithers wrote: post #71
rory wrote: post #28

My 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.

I'm curious, as someone knows probably only enough about this stuff to get myself into trouble, what am I missing out on by just pushing to heroku?

Netlify free tier is pretty great, giving custom DNS and support for NextJS build was so simple.

Heroku is similar, but Netlify is at least equally simple I found. Maybe someone else can shed more light on differences.

Re: The architecture behind a one-person tech startup

#77

Post by rory »

amzans wrote: post #58
rory wrote: post #28

My 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.

I agree with you in terms of using what you already know best. > If you're not already familiar with these tools consider using a managed platform first, for example Render or DigitalOcean's App Platform (not affiliated, just heard great things about both). They will help you focus on your product, and still gain many of the benefits I talk about here. And: > I use Kubernetes on AWS, but don’t fall into the trap of t…

Makes sense, didn't mean my comment as a criticism of your setup Anthony. The product and infra look very cool! Just highlighting that things can be a lot simpler for those of us with more mundane requirements.

Re: The architecture behind a one-person tech startup

#79

Post by anarsdk »

say_it_as_it_is wrote: post #20

I was under the impression that Kubernetes was a complicated beast not meant for small teams / startups. What is the value of it in this monolith environment? Is the key to using it in a startup context to use it as a basic monolith auto-scaling orchestrator but no more than that? If you or anyone else here can comment about how to use Kubernetes strategically without falling into an unnecessary over-engineering rabb…

Drive-by addressing the HorizontalPodAutoscaler (HPA) question you have.

It depends. If you want to scale on other metrics than cpu/mem, then HPA can do custom metrics too. See https://kubernetes.io/docs/tasks/run-application/horizontal-...

Specifically the Prometheus Adapter.

Re: The architecture behind a one-person tech startup

#80

Post by fnord77 »

rory wrote: post #28

My 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.

cloud vendor lock-in fears are overblown. pricing and features will always be competitive between the big vendors. I suspect people waste a lot of time/money trying to be cloud agnostic.

Real vendor lock-in is when you have decades of code written against an Oracle DB and you're getting charged outrageous Oracle rates and it would also cost a fortune migrate.

Post reply on HN