Building Event-Driven Microservices - Chapter 9 - Microservices Using Function as a Service

Function-as-a-Service (FaaS) is an area of cloud computing that is growing rapidly.
There are following issues to conside here:
- Principles of FaaS
- Open source and 3rd party FaaS providers
- 4 components to consider when building microservices as functions
- Cold Start vs Warm Start
- Different Triggers that can start FaaS: Triggering Based on New Events, Triggering Based on Consumer Group Lag, Triggering on a Schedule, Triggering Using Webhooks, Triggering on Resource Events
- Maintaining State
- Two patterns of functions calling other functions: Event-driven and Direct-call
- Termination and Shutdown
- Tuning and Scaling
All of these is disclosed in the Chapter 9 of the book we are currently studying:
“Building Event-Driven Microservices: Leveraging Organizational Data at Scale” by Adam Bellemare
Sharing my mind map with all the details as usual:

See also:
- Building Event-Driven Microservices - Chapter 12 - Lightweight Framework Microservices
- Building Event-Driven Microservices - Chapter 11 - Heavyweight Framework Microservices
- Building Event-Driven Microservices - Chapter 13 - Integrating Event-Driven and Request-Response Microservices
- Building Event-Driven Microservices - Chapter 10 - Basic Producer and Consumer Microservices
- Building Event-Driven Microservices - Chapter 8 - Building Workflows with Microservices