Live data from Hacker News

Technology Choices for My SaaS in Retrospect

thomasbandt.com

71–74 of 74 posts

Re: Technology Choices for My SaaS in Retrospect

#71
post #67

Other than already mentioned backups I see no mention of: * staging environment for development * at least another baremetal machine for a copy of production and a loadbalancer in front of them, to prevent from 100% downtime in case your machine is down

The article wasn't about infrastructure or resilience, it was about technology stacks. Maybe those other things were there, maybe they weren't but it wasn't about what you should do, just what he did.

First of all there's literally a paragraph called Infrastructure. Then one of the arguments is how cheap it is.

I don't find it fair to praise your tech-stack for simplicity and being cheap (awesome features btw) and fail to mention resilience. Unless you run a service that can be down 10% of time for example. Not the case here I guess since we talk about SaaS.

Re: Technology Choices for My SaaS in Retrospect

#72
post #39

As someone who's working on something similar (one-man project), what I struggle the most is with the infra details. Author mentions that there's a single machine for the api, db and nginx; this means the machine is publicly accesible to everyone, and so is the db (although the port the db is running could be only accessible to localhost). I don't really feel comfortable doing that (so I force myself to out the db wi…

His server runs 3 containers, so it should be just a generic Linux + apt install docker, and then a docker-compose file.

Re: Technology Choices for My SaaS in Retrospect

#73
post #70

Earlier quoted context omitted.

Disclaimer: I work for AWS in Professional Services. I specialize in “application modernization”. Basically that means a focus on serverless technology. That being said, if someone who doesn’t know “cloud” and has a deadline just to get something done like the author asked for advice, even I would suggest they just throw a monolith on a VM. If they really wanted the optionality to go all in on AWS later, I would sugg…

I think the use cases where you do not need to „know cloud“ are quite limited. Where does knowing the cloud start? When you use a transactional email provider? When you start using an auth. provider? When you integrate an external monitoring framework? When you use a cloud-based object or key-value storage? In my opinion, cloud integration is almost inevitable, but you might realize that a bit later when starting wit…

According to the former CEO of AWS, current CEO of Amazon and my skip*10 manager, only 5% of all IT spend is on any of the major cloud provider

https://accelerationeconomy.com/cloud/amazon-shocker-ceo-jas...

People really overestimate how many companies use the cloud in any form for anything.

Re: Technology Choices for My SaaS in Retrospect

#74
post #70

Earlier quoted context omitted.

I think the use cases where you do not need to „know cloud“ are quite limited. Where does knowing the cloud start? When you use a transactional email provider? When you start using an auth. provider? When you integrate an external monitoring framework? When you use a cloud-based object or key-value storage? In my opinion, cloud integration is almost inevitable, but you might realize that a bit later when starting wit…

According to the former CEO of AWS, current CEO of Amazon and my skip*10 manager, only 5% of all IT spend is on any of the major cloud provider https://accelerationeconomy.com/cloud/amazon-shocker-ceo-jas... People really overestimate how many companies use the cloud in any form for anything.

IMHO a more interesting metric would be the ratio of successful startups using cloud technologies over the last years. I think the cloud is especially interesting to get a competitive advantage early on.
Post reply on HN