1. Independent Systems Architecture: ISA
Creator: INNOQ |

2. Principles of Microservices
Creator: INNOQ |

3. 2 | Macro / Micro Architecture
1 | Modules
2 | Macro / Micro Architecture
3 | Container
4 | Integration & Communication
5 |Authentication & Metadata
6 | Independent Continuous Delivery Pipeline
7 | Standardized Operations
8 | Standards: Interface only
9 | Resilience
Creator: INNOQ |

4. ! ! ! Why ISA? Best practices for microservices
Introduction
Why ISA?
Best practices
for microservices
for Self-contained Systems (SCS) ! ! !
Creator: INNOQ |

5. 1 | Modules
Creator: INNOQ |

6. Modularization for a system
1 | Modules
Modules: Old idea
Modularization for a system
Creator: INNOQ |

7. High cohesion, low coupling, Separation of concerns,
1 | Modules
Reuse “Module” ideas:
High cohesion, low coupling,
Separation of concerns,
Single Responsibility …
Creator: INNOQ |

8. Modules provide interfaces Access only through interface
Creator: INNOQ |

9. 1 | Modules
Information hiding
Microservice must not use other microservices’ internals (e.g. database schemas).
Creator: INNOQ |

10. 2 | Macro / Micro Architecture
Creator: INNOQ /

11. Macro Architecture Decisions for all modules
2 | Macro / Micro Architecture
Macro Architecture
Decisions for all modules
Creator: INNOQ |

12. Micro Architecture Decisions per module 2 | Macro / Micro Architecture
Creator: INNOQ |

13. Why Macro Architecture?
2 | Macro / Micro Architecture
Why Macro Architecture?
All modules part of one system
Goal: Minimal Macro Architecture
Macro Architecture stable
Creator: INNOQ |

14. 3 | Container
Creator: INNOQ /

15. Modules = containers (or VMs, processes …)
Creator: INNOQ |

16. Process, Container, VM Decoupling
Independent … – technical decision – scalability – deployment
Creator: INNOQ |

17. 4 | Integration & Communication
Creator: INNOQ |

18. Integrate modules to become a system Synchronous, asynchronous, or UI
4 | Integration & Communication
Integrate modules to become a system Synchronous, asynchronous, or UI
Creator: INNOQ |

19. Limit options Just one: not enough 4 | Integration & Communication
Creator: INNOQ |

20. Define technical communication protocol REST, messaging …
4 | Integration & Communication
Define technical communication protocol
REST, messaging …
Creator: INNOQ |

21. 5 | Authentication & Metadata
Creator: INNOQ |

22. Standardize metadata e.g. for authentication or tracing
5 | Authentication & Metadata
Standardize metadata e.g. for authentication or tracing
Authorization in each module
Creator: INNOQ |

23. 6 | Independent Continuous Delivery Pipeline
Creator: INNOQ |

24. Microservices can only be deployed independently …
6 | Independent Continuous Delivery Pipeline
Microservices can only be deployed independently …
... if pipelines are independent
Creator: INNOQ |

25. 7 | Standardize Operations
Creator: INNOQ |

26. Configuration, log analysis, tracing, monitoring, deployment
7 | Standardize Operations
Configuration, log analysis, tracing, monitoring, deployment
Reduce effort
Creator: INNOQ |

27. 8 | Standards: Interface only
Creator: INNOQ |

28. Standardize e.g. configuration … or log interface
8 | Standards: Interface only
Standardize e.g. configuration … or log interface
Do not standardize the library!
Creator: INNOQ |

29. 9 | Resilience
Creator: INNOQ |

30. Module still work … if other modules fail
9 | Resilience
Module still work … if other modules fail
Creator: INNOQ |

31. Module still work … if moved somewhere else
9 | Resilience
Module still work … if moved somewhere else
Creator: INNOQ |

32. Macro / Micro Architecture Container
Independent System Architecture
Modules
Macro / Micro Architecture
Container
Integration & Communication
Authentication & Metadata
Independent Continuous Delivery Pipeline
Standardized Operations
Standards: Interface only
Resilience
Creator: INNOQ |

33. COPYRIGHT
This presentation is copyrighted under a Creative Commons Attribution-ShareAlike 3.0 / Unported License
Creator
Creator: INNOQ |