New

For People Who Work On Heavily Microserviced Projects, How's Things?

My CTO is looking to take our 250K line code base and split it into a whole bunch of microservices. We have a lot of integrations with third party products (OneDrive, Google Drive, Gmail, Business Central, various smaller industry providers) along with a good number of shared interfaces that are not client specific (boilerplate that will be the same for every client that is shared across clusters)

Our current code base is complex - there are some architectural decisions that were made a long time ago that makes things a pain to deal with, so I can see a desire to simplify things especially for our small team of 5 or so backend devs.

We're in a growth phase at the moment and will need to bring more people on board soon so I can see a desire to let those people not have to deal with the whole picture but I'm slightly worried that we're going to end up with a bunch of what are essentially API calls with extra steps and that things are going to prove difficult to debug and work through when interfaces change and things break.

So, I wanted ask for the perspective of people who are working on large projects that make extensive use of microservices, how are things working out? Do you have any tips for how to structure it? Do you think that just sticking to a monolith would be a preferable solution?

submitted by /u/Jazzlike-Compote4463
[link] [comments]

Back to Listing

credit:

For People Who Work On Heavily Microserviced Projects, How's Things?

Popular Products