Overview
Syllabus
Intro
Writing Applications for Virtual Machines Computing resources were much more prevalent • Code efficiency was no longer a major concern • Software libraries became fashionable • Debuggers became a lot more forgiving • Code had to be recompiled per platform to work, even if they were all
MicroServices and the Microservices Archited Defines an architecture that structures the application as a set of loosely coupled, collaborating services
What is a "Serverless" Microservice? Serverless microservices are deployed within a serveres vendor's infrastructure and only run when they are needed by the application
Key Benefits: • Resilience: Because the application is divided up, one part of the application breaking Crashing does not necessarily affect the rest of the application • Selective scalability: Instead of scaling the entire application, only the microservices that
Service Decomposition - The Old School Way! We need to partition the system into separate discreet services BEFORE we can isolate them into microservices. But how do we segment ther? Decompose by business capability Define services corresponding to business
The Benefits of Service Decomposition Effective service DECOMPOSITION provides the following benefits: • Each service has only a small set of responsibilities
Is the Microservice Architecture Better? The Best Answer is... It Depends!
Why Bare Metal and Benefits? Why: • Workload resource demand • Less potential for noisy
Why Containers? Containers are the Microservices Platform of Choice: • Enable software to run predictably and well when moved from one server
Run Applications on "Who Cares?" Okay! You took things off of bare metal, you virtualized the applications, you decomposed and placed things in containers! Now what?
A Little Light Reading. Containerless Computing: The Ultimate Service Decomposition
Taught by
Linux Foundation