3 ms·
Or move everything to a microservices architecture and use the best suited language for each subsystem. It would force both camps to engineer for composability
by thedevopsguy 11y ago
Or move everything to a microservices architecture and use the best suited language for each subsystem. It would force both camps to engineer for composability and open service apis. My tupence.
- rco8786 11y agoI assure you that Uber is built using "micro services". That doesn't mean there isn't value in having some language uniformity in the org and it doesn't solve the language preference between people problem.
- gansai 11y agoLooks like Uber has moved to a microservices architecture. Check their engineering blog: (https://eng.uber.com/soa/ https://eng.uber.com/soa/)
- thedevopsguy 11y agoWasn't aware of their move. A microservices architecture then makes the technical conversation about the service, it's latency, performance rather than implementation details. Is it such a bad thing to have many different languages in play as long as the SLAs are met?
- deleted 11y ago[deleted]