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
Architect Elevator Blog
When working for a product company, there’s no better place than working on product.
No-code, low-code has become a popular quest. Architects are called in to separate fact from fiction. No French were harmed.
Architects dive deep to come back up with new insights. Here’s is what I brought back from the serverless cloud integration engine room.
How to architect your organization to do architecture with or without architects.
Growing an architect is different from growing a system. This bookshelf will help.
Architecture isn’t linear but we can overlay a useful path for architects to follow.
A better brush won’t make you a Leonardo.
Maps don’t show every tree. And that’s OK.
Architecture isn’t binary.
A black box isn’t good enough for architects. They want to know how it’s wired together.
It’s hard to think about volume in a two-dimensional space.
They let others do the blueprints.
Conscious decision making is a major step towards better architecture.
Good platforms are like fruit salads. But some people will want to pick out just their favorite fruit.
Many architects consider lock-in their archenemy. But it’s rarely that simple.
Giving features rigid names can set a frame of mind that hinders incremental value delivery.
Architecture diagrams tend to show all the individual parts rather than illustrating the system’s key purpose. Inverting this not only produces more expressive diagrams, it also improves decision making.
The key mechanism to tackle ever increasing complexity is abstraction, such as frameworks or interfaces. Some things, however, can’t be abstracted away.
Enterprise IT is routinely plagued by excessive complexity. It might be subject to the Second Law of Thermodynamics but it’s certainly subject to Gregor’s Law.
For governance to remain effective in a high-velocity environment, it needs to be automated. Surprisingly, it also produces more reliable results.
How do you explain the value of architecture to business stakeholders? Deferring to the Nobel-prize winning economists Black and Scholes can work surprisingly well.
Today’s cloud automation goes far beyond provisioning servers. Let’s apply architecture models to the latest trends.
Cloud automation isn’t just about infrastructure anymore. This also affects automation language design.
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.
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?
Cloud automation using object-oriented languages gives us the power of abstraction. But those abstractions aren’t easy to come by.
Design patterns have helped us improve software design for decades. In the cloud, they can also reduce our switching cost. That’s magic!
Architects aren’t there to make all decisions. They use models to help others make better decisions, including whether to multi-cloud or not.
Cloud is different, so picking a provider also is.
Organizational change is typically slower than technical change and will therefore hold back your cloud journey’s value creation.
When making cloud enterprise ready, be careful not to throw the cloud baby out with the enterprise bathwater.
Enterprises can’t avoid hybrid cloud. Here are eight ways to get there.
Multi cloud means different things to different people. A decision model helps bust the buzzwords and show the options clearly.
A lot of modern cloud technology leverages containers. However, a non-trivial portion of enterprise applications don’t run easily in containers. The answer to this conundrum lies in taking a step back and asking a more fundamental questi...
What better day to launch The Grim Wrapper than Halloween?
Rhythm, Mixing, Transitions, Waveforms, Improvisation (Complex Topics, Part 7)
A Steady Rhythm Keeps Your Listeners On Track
Weaving two threads into a single presentation.
Weaving multiple threads into a single presentation.
How to overcome the first curse of speaking: linearity.
A list of ingredients doesn’t make a recipe. You need to know the right dosage.
Ethos, Logos, and Pathos have to be built-in, not tacked on.
You don’t always need to be right if you’re well prepared for being wrong.
Doing the exact same thing twice is a wasted opportunity.
What’s better than talking to CTOs? Listening to CTOs! That’s what our CTO Round Table is for.
The 9 commandments of effectively talking to technical executives.
When buying a software or hardware product for your enterprise, the future product roadmap is as much a consideration as the current product state. However, this is where some vendors play games with their customers.
Enterprise IT generally follows a “buy over build” strategy because in most cases it yields lower risk and better economics than doing it yourself. But there are a few things that you should keep to yourself.
Whether architects must code or not has been much debated. Why not try debugging?
No one can transform an organization from the outside. But on the inside you’re bound by legacy rules. Catch-22?
You can make transformation lemonade from organizational lemons–sweetened up with the right dose of creativity.
Once again we can learn about IT strategy and architecture from popular culture: the engine room matters.
Success comes in small dosages.
Slow Chaos isn’t Order.
Finding business value without the business is going to be difficult.
Hitting the wall faster is unlikely to do you any good.
Agile methods and architecture both thrive in times of uncertainty.
More steering committees don’t necessarily lead to better decisions.
Three plus one questions you should ask before you place trust in someone offering you advice.
A classic movie recipe has a seemingly law-abiding person hire someone from the underworld to do unpleasant work for them. And it all goes predictably and awfully wrong. Don’t let the same happen in your IT transformation!
When shifting gears, both a car and an organization need a clutch. But careful, it can be a grinder!
Everyone does the right thing, yet nothing much gets done. How to break self-reinforcing bad habits.