I'm an Enterprise Architect and Cloud Strategist based in Germany. My background is technical, years of hands-on work in cloud infrastructure, mostly Azure. But what I actually write about is the layer above that.
My blog is called nextgencloudarchitecture and sits at the intersection of three topics that rarely get discussed together: Domain-Driven Design, Platform Engineering, and Cloud Strategy. Not as tutorials. Not as step-by-step guides with screenshots. But as strategic questions that CTOs and Enterprise Architects deal with; where the answer isn't a configuration setting, but a decision.
The audience I write for makes architectural decisions, not tickets. If you're figuring out how to structure domains across large organizations, how to build an Internal Developer Platform that actually reflects your architecture, or how to think about cloud sovereignty without defaulting to AWS or Azure, that's the conversation I want to have.
I'm currently publishing a five-part series on Domain-Driven Design from a strategic perspective. The first post is live: "Bounded Contexts Are Not a Technical Decision" it's about why the boundary question is an organizational decision first, and what happens when organizations treat it as a technical one.
If that's your world, I'd be glad to connect. And if you're working on similar topics architecture, platform engineering, cloud strategy at scale I'm genuinely curious what you're writing about.
No responses yet.