2 ms·
> Service A could be written in Java, service B could be written in Go, service C could be written in Whitespace, if you’re brave enough. I've always found thi
by btbuildem 5y ago
> Service A could be written in Java, service B could be written in Go, service C could be written in Whitespace, if you’re brave enough.
I've always found this to be such a huge strawman. I've yet to encounter an organization that uses a variety of technologies. Usually it's one of the top most popular, sometimes two, rarely three different languages. Devs migrate between teams, hiring is done to match the skills already onboard. Coding styles (even if they differ slightly between teams) usually follow corp "best practices"
Even if it's a multitude of services, the culture of the codebase is usually very monolithic.
- salt-thrower 5y agoAnecdotally, I've seen the strawman become real. Usually it's not more than two different languages. But at my current job, we've got a split between Typescript, vanilla Node.js, and Scala on the backend. All the results of various migrations and refactors spearheaded by different people at different times but not completed. The current vision is to have a unified Scala backend someday, but I'm not holding my breath.