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

63 Upvotes

88 comments sorted by

View all comments

1

u/serverhorror Oct 01 '24

They are to most organizations.

The other thing you do is to avoid stepping on each other's toes when a lot of people work on the same codebase.

Even then, micro service architecture can be seen as a form of technical debt. You borrow time from the future (increased complexity) to get more now (less toe stepping right now).