This SkillsCast is currently only available to registered attendees of iSAQB Software Architecture Gathering — Digital 2022
It will be freely available to all Skills Matter members once the iSAQB Software Architecture Gathering — Digital 2022 early-access window expires on November 16, 2023.
Micro services are ubiquitous. However, most companies that implement micro services do not reap their full benefits - at best. At worst, it’s an epic failure. There are reasons for micro services: independent deployment of business capabilities. However, the unspoken assumption is that you need to deploy all capabilities all the time. My experience has shown me that it’s plain wrong. Some capabilities need frequent deployment, while some are much more stable. In “the past”, we used Rule Engines to allow updating business rules without deployment. While it solved the problem, this approach had issues. Between introducing a Rule Engine and migrating your complete system to micro services, I believe that there’s a middle path, and that this path is Function-as-a-Service. In this talk, I’ll detail every point I’ve made above, and show how one can use Serverless to pragmatically design a system that allows deploying as often as you need.
YOU MAY ALSO LIKE:
- A Change-Data-Capture Use-Case: Designing an Evergreen Cache (SkillsCast recorded in October 2021)
- It's Just Naming Things (SkillsCast recorded in November 2022)
- Microservices From the Trenches. A Real-Life Practical Guide Through the Architecture, Design, Code (SkillsCast recorded in November 2022)