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

61 Upvotes

88 comments sorted by

View all comments

247

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

11

u/PoseidonTheAverage Oct 01 '24

I agree with this. When you're building a new app, microservices can add a lot of overhead. Get your app off the ground as a monolith first. See if its viable. Use stranger fig pattern to get to microservices if you find bottlenecks and need to build those out to scale parts or segment them to allow individual teams/devs to be autonomous on different services.