This presentation compares the history of modern transportation to the evolution of software architectures, and provides practical guidance on moving a large organization to microservices.
What do consumers need to use the service for?
What interactions are needed to support those tasks?
What qualities does the service need to support the tasks?
How will the service be implemented (reuse existing,
modify existing, build new)?
What is the scope of the system of microservices?
What service domains are involved?
What services are required?
What non-functional domains are involved (security,
service levels, more)?
What technological capabilities are needed to support the
system of microservices?
How will these capabilities be implemented? Using which
technologies?
What standards and guidelines need to be put in place?
What are your goals for moving to a microservice
architecture?
What are the main obstacles to this change?
What are your core microservice principles?
What is needed to build momentum for the change?
What practices need to be adopted in order to deliver the
system of microservices?
What institutionalized organizational practices need to be
used for the delivery of the microservices system?
What organizational blind spots need to be addressed?
How can adaptability be incented in the organization?
Microservice-based Enterprise Transformation Architecture
A methodology that applies these five design disciplines
To learn more, attend the CA Microservices and APIs
Virtual Summit Series on October 11:
http://cainc.to/VNZ2Fx