One city team wants Python for a GIS microservice while another prefers Java for billing, as long as the published HTTP contract stays stable. What makes that polyglot choice viable?
Select an answer to reveal the explanation.
Short Explanation
Services talk through a doorway (the contract), not by sharing the same living room. Once the doorway stays the same shape, each room can be furnished in a different language.
Full Explanation
Independent processes communicate through published interfaces, so language and runtime can differ per service. Polyglot is a consequence of that isolation, not a mandate to use every language. An in-process shared framework would collapse the boundary and remove that freedom.