Q&A: With the API revolution and the advent of microservices ushering in a new era of software development, CA says we've only scratched the surface.
CA Technologies, which focuses on helping enterprises transform for the application economy, has delved into the DevOps and Agile development spaces with product and services support. The company also has amassed some serious microservices expertise with its API Academy, as it works to help empower developers to more easily build software, perhaps even leading to software factories. In this Q&A, Matt McLarty, software architect and vice president of the API Academy at CA, explains microservices, the API economy and where the technology is taking us. McLarty is the co-author of O'Reilly's Microservice Architecture: Aligning Principles, Practices, and Culture.
What is your definition of microservices?
That can be answered in one sentence, or in an entire book. Here's as succinct a definition as we could come up with for the book we wrote: "A microservice is an independently deployable component of bounded scope that supports interoperability through message-based communication. Microservice architecture is a style of engineering highly-automated, evolvable software systems made up of capability-aligned microservices."
But that just scratches the surface. There are many associated factors. The best description of those is in a blog post from James Lewis and Martin Fowler. I see "microservices" as a software architecture movement that has come out of the Agile software development movement by way of DevOps. It has similarities and differences with the SOA [software-oriented architecture] movement. Lastly, maybe the best way of describing microservices is through what it intends to deliver: speed of delivery in harmony with system safety at scale.