1. Microservices architecture
Two programmers were arguing from where the power of Unix comes. One said: “The
applications give us the power.”
The other said: “No, it’s the operating system kernel which enables the applications to
be powerful.”
Master Foo happened to be passing by. He told them: “Not the applications, not the
OS kernel; it’s the Unix spirit which gives us the power.”
branislav.majernik@oracle.com
2. What customer expect from apps today
• Lot of and fast business functionality.
• App business performance.
• Quick extension of business functionality, fast adapt to changes.
• Multifrontend (Mobile, SPA, MPA Web).
• Multichannel (Whatsapp, Viber, Facebook, …)
Source of pictures://Microservices from design to deployment by Chris Richardson & Floyd Smith
Business experience
DevOps experience
• Simple and fast functionality implementation.
• Scalability, elasticity.
• Quick change request, testing, deployment.
• Isomorphic programming and frameworks.
• Simple thirth API implementation.
16. Creating small well apps
Source of pictures://Microservices from design to deployment by Chris Richardson & Floyd Smith
• Order a taxi
• Track the cab
• Make the payment
• Receive notifications
• Leave commentaries
Challenge
The customer wanted to order a taxi-hailing platform development.
One of the requirements was to make it cross-platform (operate either as a web application or as a phone app).
The standard functionality was required:
• Passenger Management
• Driver Management
• Trip Management
• Dispatcher
• Payments
• Notifications
• Billing
Approach
Services decomposition, focus on business domain services