Show Notes
Architecture Corner Newsletter Podcast - exploring documentation strategies that scale with your event-driven architecture Event Catalog offers capabilities beyond basic service documentation, providing structured approaches to manage complex distributed systems. This episode examines practical features that support enterprise-scale event-driven architectures. In this episode we will cover: Organizational patterns - subdomain modeling and versioning strategies for evolving systems Lifecycle management - deprecation workflows, changelog practices, and governance reporting Infrastructure mapping - channels, flows, and message routing documentation Deployment approaches - single repository vs federated documentation strategies Integration capabilities - embedded diagrams, schema generation, and cross-system dependencies
For more details check here. If you are interested in more information about software development and architecture, subscribe for free to our newsletter. --- https://architecturecorner.substack.com
More from Architecture Corner
Architecture Corner Newsletter Podcast AI coding budgets are getting torched, and 2026 is the year the bill finally came due. In this episode, we dig into how token consumption became a productivity metric (and why that backfired), and what the industry is doing about it now that the free-for-all is ending. We will cover: Why token usage became a proxy for developer productivity — and how Goodhart's Law caught up with it The provider-side shifts (usage windows, model restrictions, pricing model changes) that reshaped agentic coding through early 2026 What's really driving your AI bill: subscriptions vs. API, caching mechanics, and model/thinking-effort tradeoffs Practical tokenmining strategies — from scripting deterministic steps to tuning your harness and mixing models Where the industry goes next as cost-conscious AI development becomes the norm
Are you flying blind with your AI coding agent? In this episode, we detail what actually happens inside tools like GitHub Copilot and Claude Code beyond the prompt you type.
Once you ship a public API, you've made a promise. Keeping it while still moving forward turns out to be harder than most teams expect. In this episode, we will cover: What qualifies as a backward-compatible change, and what doesn't Why does introducing a new API version cost more than just writing new code The real reason clients delay upgrades, and what you can do about it How to support multiple versions without duplicating your entire codebase The adapter pattern is a practical way to isolate version changes at the edges Know more here: https://medium.com/itnext/the-challenges-of-evolving-your-service-api-versioning-8008349a1154 Subscribe, for free, to the Architecture Corner Newsletter at https://architecturecorner.substack.com
The AI development landscape keeps shifting, leaving many developers frustrated as they try to keep up with each new model, tool, and workflow. But what if the answer isn't chasing every update, but building a more intentional approach?
Welcome to the Architecture Corner Podcast