Three forces are fueling microservices architectures, the editor of Service Oriented at ZDNet discuses the main forces fueling microservices architecture.
""Sure, microservices, distributed architectures and containerization might make sense for the Googles and Facebooks of the world, but what about everyone else who doesn't operate at Web scale?""
Joe McKendrick covers Pruss, a blogger, who defines microservices as the building and deploying of applications ""as suites of discreet, modular services, each running its own process with a minimal amount of centralized management.""
Joe comments on the overlap of SOA and microservices "The idea of discrete, independently functioning services was the original goal of service oriented architecture. But SOA often got mired within the back-end monoliths it was supposed to replace."
SOA which often became a wrapper of existing legacy applications instead of a way to build new services is one difference between microservices which are more geared toward greenfield services than legacy wrappers.
Joe brings out that Pruss brought out the following key points:
"Microsoervices is a more modular answer to the monolithic apps that have evolved in many enterprises. Making a change against one of these enterprise behemoths means bringing down an entire assembly of downstream apps for revision. In theory, when a microservice goes down, other, surrounding services will be unscathed." says Joe.
Microservices is more than a sum of its parts. "Employment of these highly independently functioning granular services that represents ""an organizational shift in how software development pipelines are constructed and managed,"" requiring tools and platforms that address the oft-neglected people and processes aspects of solution delivery. Expect to see a vibrant new industry spring up around these requirements," Pruss predicts.
Read the full article at: Three forces are fueling microservices architectures.
Read the full blog post from Pruss at: The Case for Microservices in the Enterprise.