DEV Community

Discussion on: Functional Debt: The Price of “Yes”

Collapse
 
jeastham1993 profile image
James Eastham

I'm finding this exact situation with a legacy API I'm working with at the moment. It's currently a monolith, that a single client has driven a lot of the functionality for.

We are now in a tricky situation in that some clients want slightly different functions, but not enough to warrant a completely different application.

My long term plan, is breaking the monolith into microservices but that takes team. But I'm feeling the functional debt pain right now.

Love your writing by the way Matt, keep it up :)

Collapse
 
integerman profile image
Matt Eland

Thanks for the encouragement! That means a lot.

As for your specific case, I can empathize to some extent as a manager managing an API development team.

Breaking a monolith into microservices is a good plan. You might want to consider Bob Martin's strangler application pattern on that journey.

Thankfully, API developers have more options in introducing new endpoints or versions as needed and are less tied to user interface concerns.

Collapse
 
jeastham1993 profile image
James Eastham

I've read about the strangler pattern before, and it's exactly how I'll manage it I think.

Agreed on the options for API developers though, it's a nice place to be. The API itself has versioning in the URL string, so it should be extremely easy for me to migrate.

Thanks for the response!!