Should that be a microservice? Factors to keep in mind

Re:Should that be a microservice? Factors to keep in mind by mwcampbell on Sunday April 21, 2019 @09:31AM (#19711997)

> 6. Freedom to choose the right tech: This is true, but as they say having all these extra technologies comes with a lot of extra dev training, dev hiring and ops costs. Maybe it would have been better to use a 'second best' technology that the team already has rather than the best technology that it doesn't, once those costs are accounted for.

A variation of this pushed me to implement a couple parts of an application as micro-services even though I wanted to stick with a monolith. I wanted to use existing open-source packages written in languages other than the primary one that I had chosen for my monolith. It's really a shame that a cross-language, in-process ABI like COM didn't catch on outside of Windows.

[ Parent | on HN ]

Re:Should that be a microservice? Factors to keep in mind by lalaland1125 on Sunday April 21, 2019 @10:55AM (#19712314)

A cross language, in process ABI does exist for all platforms. It's called the C ABI. Almost every programming language can export and import C ABI functions and data.

[ Parent | on HN ]

Re:Should that be a microservice? Factors to keep in mind by mwcampbell on Sunday April 21, 2019 @12:30PM (#19712882)

Sure, but that's lower level than COM or WinRT. And in practice, does anyone embed, say, a Node.js module inside a JVM application via a C library?

[ Parent | on HN ]