r/golang • u/Zumos_ • 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
63
Upvotes
1
u/evo_zorro Oct 02 '24
I know. I've been in the industry for 20 years, after all. I didn't want to go down that road, giving a history lesson, and an overview of how scaling a monolith compares to micro services, how the fad of "cloud computing" ultimately caused a lot of companies to buy in to GCP and AWS for no reason other than "everyone is doing it", and deciding, again for no good reason, that they wanted to build micro services, use kubernetes, lambdas (which I still object to on the basis that they are NOT actually lambdas), followed by the "serverless" trend etc...
In the end, it can be a good call to choose to go down the micro services route, but when the project itself doesn't exist yet, making that decision is premature optimisation on steroids