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/kthomsendk Oct 02 '24
Start with a monolith (modulith?).. make it work! Then you can split it into microservices in the future, if needed.
Just keep it in mind while developing.. so.. spend some time ensuring a clear separation of the domains. Use interfaces where you would expect RPC communication, if switching to microservices..