SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.
SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.
Successfully reported this slideshow.
Activate your 14 day free trial to unlock unlimited reading.
5.
A monolithic design is characterised by such a tight coupling
among modules that they have no independent existence.
6.
challenges
• If one things fails, everything fails
• Can’t scale the database any further
• Expensive hardware
• Maintenance is scary
• Platinum support contract costs
7.
We used to innovate to get ahead,
now We have to innovate just to keep up
8.
goals
• Scaling individual parts of the system
• Lower hardware costs
• No platinum support
• Environment to quickly evaluate ideas
• No estimations, you are wrong anyway!
9.
Top inspirations
• Larry Constantine - Structured Design (1960)
• Douglas McIlroy - Programs (1965)
• Ken Thompson - Unix (1973)
• Antony Williams - COM (1987)
• Udi Dahan - Autonomous Components (2004)
• Greg young - CQRS (2008)
• Fred George - Micro Services (2013)
10.
–Ken Thompson, Unix Philosophy 1973
“Design programs to be connected to other
programs. “
11.
–Mc Mcllroy, Unix Time-Sharing System Forward”. 1978
“Expect the output of every program to become
the input to another, as yet unknown, program.”
12.
μServices architecture
service
subscribe to events
publish events
exposes http api
GET /profile
event stream
storage
reads and write to own storage