2023-05-17
-
The document “starting” the process of transforming how Amazon went from a two-layer monolithic, stateless app and database, to a “workflow-approach”(long-running process).
-
How to test for behaviour, not implementation.
How and where to test your app(using clean architecture).
-
Clean architecture by Uncle Bob.
-
How to control Long-running processes.
Does anyone control the process, or does it simply “jump” from one service to the next?
-
What are Long-running processes?
-
In LinkedIn, a “log” is a an append-only, totally-ordered sequence of records ordered by time.
They built Kafka to handle this.
-
How to build the correct thing right from the start, and how to test for it.
Make specifications: What the system does.
2023-05-16
-
How Ubers design process focus on keeping it simple.
-
How projects can be run without Scrum.
-
Nice overview of how to think of, and implement RPC instead of REST.
”POST ”startCar”” vs
“PUT /cars/id/engine/state/on”
-
Long-running processes are stuff that takes “a long time” to complete. How to do that?
-
Some nice-to-know stuff about distributed systems.
-
Transitioning your architecture from microservices to a monolith.
-
-
-
No system can be thought of as “tested” until after it has hit Prod. Build resiliency into your app.
-
Separate Deploys from Releases
-
How to test for behaviour, not implementation.
-
-
How to design event-driven architecture, and to do long-running processes.