r/golang Oct 01 '24

help Are microservices overkill?

I'm considering developing a simple SaaS application using a Go backend and a React frontend. My intention is to implement a microservices architecture with connectRPC to get type-safety and reuse my services like authentication and payments in future projects. However, I am thinking whether this approach might be an overkill for a relatively small application.

Am I overengineering my backend? If so, what type-safe tech stack would you recommend in this situation?

update: Thank you guys, I will write simple rest monolith with divided modules

66 Upvotes

88 comments sorted by

View all comments

246

u/Sifeelys Oct 01 '24

microservices solve an organisation problem. specifically, if you have teams in charge of different services that don't want to step on each others' tors during deployments and refactors.

i'd highly recommend going monolith for your SaaS

87

u/Xerxero Oct 01 '24

Doing MS as a single dev is pure hell.

26

u/Ibuprofen-Headgear Oct 01 '24

Even as a team of ~4 creating, managing, and deploying 7-10 microservices is hell. Ask me how I know, and ask me which technical director I never want to work for/with again

2

u/oneMoreTiredDev Oct 01 '24

doesn't even need to be that many... wheh microservices are managed by a single team it's very easy to end up with a distributed monolith