A housing-authority team labels “intake,” “inspection,” and “payments” as microservices but packages them as libraries loaded into one OS process so they can share memory. What essential microservice property have they lost?
Select an answer to reveal the explanation.
Short Explanation
If three “services” share one process, you have renamed a monolith—not created microservices. Independent deployability means separate processes and release trains. Shared memory convenience puts shipping, scale, and failure back on one fuse.
Full Explanation
A microservice is its own process and release cadence so teams can ship, scale, and fail independently. Folding several modules into one OS process for shared memory recreates monolith coupling. HTTPS at the edge, language uniformity, and Object Storage access are unrelated to that decomposition property.