Hacker News new | past | comments | ask | show | jobs | submit login

Often what you end up will have been driven by the founder CTO or first technical hire. And it will be whatever they had most familiarity/experience with.

For a monolith and size you are talking about a sensible approach would be pretty minimal infra. The app would be hosted on a managed service (e.g cloud run, elastic beanstalk, app engine etc…) along with some kind of managed database service.

You might also see a kubernetes cluster being used - generally happens if that’s what the original devs knew.

Adventurous places may have the monolith deployed on serverless which can be pretty cost effective.

Heroku like services are also still popular.

In my previous place we had the monolith on cloud run.

Anything more complex than the above would to me be a bad smell - unless there were some very good reasons.




> In my previous place we had the monolith on cloud run.

How was managed a new deployment ? Could anyone push a new version ? Did it go through CI/CD ?

And about CI/CD, did you have something vaguely resembling it ? Was it all hosted ?

> Anything more complex than the above would to me be a bad smell - unless there were some very good reasons.

Yes, you would probably not need something more complex in that case, but then again, some companies with 5 devs start with microservices


All through CI/CD running on GitHub actions. There's really no excuse nowadays for not having good CI/CD processes.

We could have used googles cloud build, but the team knew GitHub actions well.




Consider applying for YC's Fall 2025 batch! Applications are open till Aug 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: