4 ms·
How would you build and keep in sync the same library with the same functionality in 10 different languages? Every new feature would have to be implemented 10 t
by lijok 3y ago
How would you build and keep in sync the same library with the same functionality in 10 different languages? Every new feature would have to be implemented 10 times. Sounds quite foolish
- from-nibly 3y agoWhy would a single project need to be in charge of this for every language?
- lijok 3y agoTo handle cross-cutting concerns for all supported languages in a polyglot environment
- camgunz 3y agoI think what happens outside of microservices shops is that "the Java people" write their own library, "the Python people" write their own, etc. Is that a little bonkers? No more bonkers than wrapping services with other services to get them to behave reasonably.
- camgunz 3y agoThis is a big thing that happens w/ microservices: your system is implemented as a Tower of Babel (it's oddly touted as a feature). In that scenario, you no longer have good choices, you're constantly reimplementing things with slight differences in multiple languages, the maintenance overhead and defect rate is sky high, etc. The big bad here is having the "10 different languages" problem in the 1st place.
- lijok 3y agoMicroservices or not, at a certain scale, depending on the industry you're in, your company will go polyglot.
- camgunz 3y agoI don't think this is really a truism, but maybe! But like, even Google says, "you can choose any language as long as it's C++, Go, Java, or mayyyyyybe Python". That's pretty manageable, and probably the worst problem you'd ever reasonably have. I think most people should probably be restricting themselves to Python/Go/Node, which again is very manageable--certainly better than 10 languages.