A software design approach associated with Robert C. Martin (Uncle Bob) that splits a system into decoupled modules with clear interfaces and a single purpose each; it applies to low-code solutions as well as pro-code.
Power Platform solutions often start as quick low-code apps and end up business-critical, integrated and hard to maintain. In this interview Ian Tweedie explains to Power Platform makers, developers and architects how modular features, server-side logic, Key…
Software doesn't become difficult to maintain because developers write bad code—it becomes difficult because it wasn't designed to evolve. In this episode of the M365 FM Podcast, Mirko Peters is joined by Microsoft MVP and veteran software architect Miguel…
In this episode of the M365.fm podcast, Mirko Peters explores why many microservice architectures gradually become slower, more fragile, and harder to manage despite originally being designed for speed and agility. What begins as a clean and scalable…
Why Strong Data Modeling Still Matters in the Age of AI · Mirko Peters Welcome back to the blog! If you have spent any time in the tech world over the past couple of years, you know that Artificial Intelligence is dominating every conv…
Warning signs include tight coupling, shared databases and synchronous communication. They turn a clean architecture into a web of dependencies, where even small changes need coordination across services and teams. · From the episode: Why Microservice Architecture Slows Software…
Short info above, community knowledge below: add practical tips, examples or corrections. New contributions are reviewed first; trusted members publish directly.
Experts and companies for this topic
Nobody has listed this topic yet. Add it to your profile.