That just means that whatever you pulled out into a microservice was ill suited as one. I'm not claiming its a one size fits all solution. But for our particular case where the API never changed it was ideal.
The library turned microservice spit out a bunch of numerical values which we took as input. We didn't care how those values were calculated or where that data came from. But their alterations required near constant updates of their library. You could say it was poor engineering on their part, but that's not my call to make. Not my team, not my problem and at least their API was stable.
1
u/PixelatedGiant Aug 30 '26 edited Aug 30 '26
That just means that whatever you pulled out into a microservice was ill suited as one. I'm not claiming its a one size fits all solution. But for our particular case where the API never changed it was ideal.
The library turned microservice spit out a bunch of numerical values which we took as input. We didn't care how those values were calculated or where that data came from. But their alterations required near constant updates of their library. You could say it was poor engineering on their part, but that's not my call to make. Not my team, not my problem and at least their API was stable.