The document summarizes Matt McLarty's presentation on a design-based approach to microservices at a conference on September 10, 2018. It discusses applying five design disciplines (program, service, system, practice, and foundation design) to transform an enterprise architecture to be microservices-based. It also promotes attending a CA Technologies virtual summit on microservices and APIs on October 11 for more information on the methodology.

1. Microservices Conference
A Design-based Approach to Microservices
September 10, 2018
Matt McLarty, Vice President, API Academy, CA Technologies

2. Let’s begin with a story…

4. Once upon a time…

15. μ

24. From http://networkstatic.net/the-control-plane-data-plane-and-forwarding-plane-in-networks/

26. From https://martinfowler.com/articles/microservices.html

27. From https://martinfowler.com/articles/microservices.html

28. From https://martinfowler.com/articles/microservices.html

29. From https://martinfowler.com/articles/microservices.html

36. From https://sebiwi.github.io/comics/service-mesh/

37. Security • Access Control, Authentication, Crypto
Traffic
Management
• Rate Limiting, Traffic Shaping, Service
Discovery, Dynamic Routing
Observability • Monitoring, Logging, Message Audit

38. Security • Access Control, Authentication, Crypto
Traffic
Management
• Rate Limiting, Traffic Shaping, Service
Discovery, Dynamic Routing
Observability • Monitoring, Logging, Message Audit

49. Consumer Tasks Dependencies
Qualities
Interface
DataLogic/Rules
Queries Commands Event
Subscriptions
Event
Publications
Consumer …
• Task list…
Consumer …
• Task list…
.
.
.
Service …
• Task list…
Service …
• Task list…
.
.
.
Service Name: Description:

50. Consumer Tasks Dependencies
Qualities
Interface
DataLogic/Rules
Queries Commands Event
Subscriptions
Event
Publications
Consumer …
• Task list…
Consumer …
• Task list…
.
.
.
Service …
• Task list…
Service …
• Task list…
.
.
.
Service Name: Description:

51. Service
Perspective

52. Service
Perspective
System
Perspective

53. Service
Perspective
System
Perspective
Ecosystem
Perspective

54. Program Design
Service Design
System Design
Practice Design
Foundation Design

55. 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)?

56. 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)?

57. 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?

58. 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?

59. 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?

60. 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