-
Messenger Ravens and Royal Couriers: Building with Messages and Events
Not every message requires the messenger to wait at the castle gate. A traveler arrives at the castle gate with an urgent request. The guard carries it to the steward, the steward consults the royal records, and the traveler remains outside until someone returns with an answer. This arrangement works when the traveler needs an immediate response, and the castle can provide one quickly. It becomes fragile when the work takes several minutes, the responsible official is unavailable, or five hundred travelers arrive at once. The problem is not that the road is poorly built. The problem is that every participant must remain available throughout the conversation. In the previous…
-
The Castle That Appears on Command: Serverless Architecture
Sometimes the finest fortress is the one that exists only when it is needed. A Fortress Without a Permanent Gate: What Serverless Actually Changes For most of software history, deploying an application meant giving it somewhere permanent to live. A server was provisioned, a runtime installed, and a process waited for requests whether anyone arrived or not. Virtual machines changed how servers were acquired, and containers changed how applications were packaged, but the assumption remained: something was running, and engineers were responsible for keeping it alive. Serverless challenges that assumption by asking whether the fortress needs to exist when nobody is visiting. The name is misleading because servers still exist.…
