Live data from Hacker News

The architecture behind a one-person tech startup

anthonynsimon.com

81–90 of 334 posts

Re: The architecture behind a one-person tech startup

#81
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.

Another way to do something similar would be to use Cloud Run https://cloud.google.com/run and that way you can avoid vendor lockin since you can move your manifests to another knative hosting provider or spin up your own K8s cluster and deploy knative

Re: The architecture behind a one-person tech startup

#82

Earlier quoted context omitted.

People here underestimate google app engine a lot. But I doubt if there is better one person Saas service out there.

Digital Ocean is fantastic.

Would you mind being more specific? Is it the price / functionality balance that makes DO fantastic?

Re: The architecture behind a one-person tech startup

#83
Nice 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

#84

Earlier quoted context omitted.

People here underestimate google app engine a lot. But I doubt if there is better one person Saas service out there.

Digital Ocean is fantastic.

Agreed, would have gone with their managed app platform if I was using one of the supported techs. For search I use a $5/mo meilisearch DO droplet that took almost no time to set up and I never have to pay attention to.

Re: The architecture behind a one-person tech startup

#85
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.

Interesting, thanks. I used to use Google AppEngine a lot and very much liked it, but haven’t touched it for years. Now, I like the idea of using Heroku better, and just pay a little more.

Heroku my feels cheaper when you think about how long you can punt on having ops proper person(s) & how much time you save rolling your own everything.

Re: The architecture behind a one-person tech startup

#86
post #11

Earlier quoted context omitted.

> From a GDPR perspective it's not even clear if this is even lawful It is pretty clear it is

No it's not, you can check e.g. the EDPB's recommendation [1] on this. At the very least you'd need to use data mapping and ensure EU citizens data stays within the EU, the author's service advertises "200 edge locations around the world" so I'm skeptical whether data won't leave the EU. Not many companies care about this and there's little enforcement so far, I think it's fair to think about this though if you're ru…

Edge locations refer to the CDN which his static assets are served from, i.e. HTML, JS, CSS, images.

Not customers data.

Re: The architecture behind a one-person tech startup

#87

This goes against the HN trope that "you don't need Kubernetes unless you are Google-size". It turns out Kubernetes is actually perfect for small teams as it solves many hard operational issues, allowing you to focus on the important part of the stack: the application. The key is to stick to a simple setup (try not to mess with networking config) and use a managed offering such as GKE. We may need a Kubernetes, The G…

I think main point is: "don't run your own k8s cluster unless you are google size".

Running stuff on some k8s managed for you is imo perfectly fine.

Re: The architecture behind a one-person tech startup

#88
post #84

Earlier quoted context omitted.

Digital Ocean is fantastic.

Agreed, would have gone with their managed app platform if I was using one of the supported techs. For search I use a $5/mo meilisearch DO droplet that took almost no time to set up and I never have to pay attention to.

I'd actually use Caprover then manage my services using that... it's as close to a self-managed platform as you can get for one-click deploys.

Re: The architecture behind a one-person tech startup

#90
Interesting post. I would advice people against running a kubernetes / docker setup if you don't know it well. It's quite complicated and most small companies don't really need it.

As the author say, he already got a lot of experience of it so it worked out great for him but it is probably easier just to install the tech needed for a small company.

Unless you have something very special going on, the dependencies (like databases) are probably not going to be that many.

Post reply on HN