Download to read offline
Uploaded byRamit Surana
Building Big Architectures
This document provides an overview of microservices architecture compared to monolithic architecture. It discusses key concepts like SOA, containers with Docker, principles of microservices including loose coupling and decentralization, and industry examples from Netflix, Twitter, and others. The presenter's goal is to explain why microservices are important and how organizations can transition applications from monolithic to microservices using tools like Docker and orchestration.
More Related Content
Similar to Building Big Architectures
Building Big Architectures
- 1. Ramit Surana @ramitsurana/in/ramitsurana
- 2. Agenda • Why isthis important ? • Defining SOA • What are Monoliths ? • What are Microservices ? • About Docker • Principles of Microservices • Refactoring • 12 Factor App • Conway's Law • Coupling • Case Studies
- 3. About Me • OpenSource Guy • Contributor to Docker, CoreOS and Kubernetes community. • Open Source community speaker. • Contact me: ramitsurana@gmail.com
- 4.
- 5. Why is thisimportant ?
- 6. SOA(Service Oriented Architecture) Architecturalpattern in computer software design in which application components provide services to other components via a communications protocol, typically over a network.
- 7.
- 8.
- 9. Overview of MonolithArchitecture
- 10. Monolithics • Single Runtime •Single Codebase • Layered architecture • Initialization of the system may be tricky or laborious. • Change to the control flow is impossible. • An application where all of the logic runs in a single app server.
- 11.
- 12. Overview of MicroservicesArchitecture
- 13. Microservices • Loosely coupledservice oriented architecture with bounded contexts. • Design for failure • Decentralized Governance • Decentralized Data Management. • Componentization via Services
- 14.
- 15. About Docker • Openplatform for developers and sysadmins to build, ship, and run distributed applications. • Docker enables apps to be quickly assembled from components. • It eliminates the friction between development, QA and production environments.
- 16.
- 17.
- 18.
- 19. Using Docker Hubwith Microservices Developer Developer Developer Developer Developer Configure Configure Configure Configure Configure Release Cycles Production Docker Hub
- 20.
- 21.
- 22.
- 23. Principles Governing Microservices
- 24. Coupling • Tight couplingleads to huge, monolithic systems that are difficult to maintain or improve upon • If changing one module in a program requires changing another module, then coupling exists.
- 25.
- 26. Conway's Law "Any organizationthat designs a system … will inevitably produce a design whose structure is a copy of the organization's communication structure."
- 27. Refactoring • Process tochange the existing code without changing its external behavior. • Refactoring improves nonfunctional attributes of the software.
- 28.
- 29. But What aboutDevOps ?
- 30. DevOps • DevOps isa company culture where the Developers movement or practice emphasizes the collaboration and communication of both software developers and other information-technology (IT) professionals. • It helps in automation and making delivery fast.
- 31.
- 32.
- 33.
- 34.
- 35. How does Googledoes it?
- 36.
- 37. Thank You May youhave a nice day ahead !