DEV Community

Discussion on: Is Microservices a good choice ?

Collapse
 
oscarcalderonc profile image
Oscar Calderon

Not a good idea to implement microservices. Your dev team is too small. It would make more sense if your team is composed of squads (each squad being a team of people, not a single person) to own certain services. Otherwise it would be a big burden to own and maintain them

Collapse
 
andycharles6 profile image
andycharles6

Agree with Oscar. Microservices in your case has more downsides than upsides

Collapse
 
tmpalma profile image
Thiago Palma

I agree with Oscar, and I'd like to add a point: one could argue that spliting a large codebase into several smaller ones could actually benefit the team, and for that I'd say: be aware that you will end up with more "moving pieces", so it might be a bit of a trap: trading coding complexity for operational complexity.
One other thing: presuming this code has little to no coverage, I would first aim at integration tests rather than unit tests - test bigger chunks first, making sure that bigger flows are actually understood (and at the time building a sort of documentation for this code), and then moving in to unit testing smaller pieces.