Is AWS Lambda a Halo Product?
Shiny, advanced, a strong fan following, but lack of mainstream adoption—the trademarks of a halo product. Sounds like AWS Lambda?
Architect Elevator Blog
Real life writes the best stories, so ride the architect elevator up and down Enterprise IT with me. Never miss a post – follow me on Twitter or Linkedin or subscribe to my feed.
See all posts by category:
Recent Posts:
Why Are Business Architects Always Grumpy?
Or: why do IT architects have more fun?
Old Books that Every Architect Should Read
If architecture is timeless, so should be the books about it. Here’s a book list with some classics.
The Many Facets of Coupling
Dissecting a buzzword takes more than a single blog post.
The Economics of Writing Technical Books
Yes, you can make money writing books. But never do it for that.
Ford vs. Ferrari vs. Porsche
Cultural lessons from a racing movie.
The Serverless Illusion
Abstractions can become illusions. Is Serverless one of them?
Spooky: Platform Strategy Awakens
What better day to launch The Grim Wrapper than Halloween?
IxC: Infrastructure as Code, from Code, with Code
Today’s cloud automation goes far beyond provisioning servers. Let’s apply architecture models to the latest trends.
Application Architecture as Code
Cloud automation isn’t just about infrastructure anymore. This also affects automation language design.
Cloud Automation à la DDD: From stringly typed to affordances
Domain-driven design very much applies to technical domains. Let’s try it on event-driven cloud systems to see why I am such a big fan of object-oriented automation languages.
Programming without a stack trace: When abstractions become illusions
As the complexity of our platforms increases, we keep looking for better abstractions. Cloud compilers might help, but only if they include one key feature: the stack trace
I made everything loosely coupled. Will my cloud bill go up?
Loose coupling is an essential property of fine-grained, event-driven systems. However, cloud resources that decouple event producers and consumers incur a run-time cost. How to weigh the trade-offs?