Most modern applications are distributed, integrate with third-party services, and expose APIs. And although the cloud, serverless, and automation have made distributed systems management easier, fundamental challenges like coupling, latency, or delivery semantics remain.
As the “Fallacies of Distributed Computing” are widely documented (and largely focus on the network and transport layer), it’s time to discuss some truths about distributed system design that focus on coupling, in-order delivery, retries, and control flow.
As the “Fallacies of Distributed Computing” are widely documented (and largely focus on the network and transport layer), it’s time to discuss some truths about distributed system design that focus on coupling, in-order delivery, retries, and control flow.
Gregor Hohpe
Gregor helps technology leaders transform both their organization and their technology platform. You’ll find him riding the Architect Elevator from the engine room to the penthouse, perhaps automating serverless solutions in the morning and preparing board presentations in the afternoon. His favorite pastime is dissecting buzzwords and replacing them with meaningful decisions and architectural trade-offs.
Gregor has served as Director at AWS and Google Cloud’s Office of the CTO, as Smart Nation Fellow to the Singapore government, and as Chief Architect at Allianz SE, where he oversaw the architecture of a global data center consolidation and deployed the first private cloud software delivery platform.
Gregor has served as Director at AWS and Google Cloud’s Office of the CTO, as Smart Nation Fellow to the Singapore government, and as Chief Architect at Allianz SE, where he oversaw the architecture of a global data center consolidation and deployed the first private cloud software delivery platform.