How do you start learning this breadth of software engineering? I consider myself good in the python / django space, but where do I start with learning these infrastructure technologies? I find that I use them once or twice periodically, and then don't touch them for so long, so I forget much of what I have learned.
The architecture behind a one-person tech startup
41–50 of 334 posts
Re: The architecture behind a one-person tech startup
#42Earlier 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…
By the edge locations, I'd assume he's serving cached static files, such as his blog or tracking scripts from there using CloudFlare. Assuming CloudFlare is not falsely advertising their GDPR compliance, the author is also fine.
Re: The architecture behind a one-person tech startup
#43Super interesting! Definitely feels like a lot of fairly low-level tech to have to deal with for a one-person company, but I guess that doesn't surprise me any more :)
Re: The architecture behind a one-person tech startup
#44I always feel like these write-ups about SaaS's are written by people who make SaaS's for other SaaS's. Application monitoring, email marketing, etc.
Re: The architecture behind a one-person tech startup
#45This 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…
Re: The architecture behind a one-person tech startup
#46In my situation I am finding the lack of consistent environment a reoccuring issue, the developer environment does not match production. However I kept it simple with Google App Engine Standard and Flex environments, I found the deployment process simple and was enough for me (at the time) - however I am finding we are going to step into dockerland; however I feel like it is very over my head!
Re: The architecture behind a one-person tech startup
#47This 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…
Kubernetes, The Good Parts: See Hashicorp Nomad ;)
Re: The architecture behind a one-person tech startup
#48This 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…
Re: The architecture behind a one-person tech startup
#49Ideally, you would get it to the point where a newbie can use it as a reference.
Re: The architecture behind a one-person tech startup
#50That's not to take anything away from the excellent writeup, but more so that someone who is thinking about starting a SaaS maybe doesn't jump to the conclusion of "I should go learn Kubernetes".