Platform experience
Long experience with distributed systems, modular design, and developer workflows informs the model behind UMA.
About Enrico Piovesan
Enrico Piovesan is a platform software architect with more than two decades of experience building modular, cloud-native, and event-driven systems. His work focuses on architectures that can scale technically without becoming harder for teams to reason about, operate, or evolve.
Architectural perspective
Universal Microservices Architecture comes from a practical concern: modern systems keep spreading across runtimes faster than their architecture evolves. The result is often duplication, hidden dependencies, and governance that arrives too late. Enrico writes from the perspective of someone trying to preserve architectural clarity under real product pressure rather than from a distance from implementation.
Professional background
Enrico’s work spans modular systems, event-driven architecture, platform design, and developer experience. That mix matters because Universal Microservices Architecture is not just a theory about service boundaries. It is also a response to the operational and organizational costs of systems that grow faster than their architectural model.
Product reality
The architectural ideas are grounded in systems that must survive scaling pressure, delivery pressure, and team boundaries.
System thinking
The work is driven by the idea that software architecture should remain understandable as systems become more distributed.
Long-term durability
The aim is not novelty for its own sake, but an architecture that lasts longer under change.
Why this site exists
This site is the public hub for the book, the learning path, the examples, and the related writing. Medium remains the main publication channel for long-form posts, while this site acts as the authority and navigation layer around the book and the UMA model.
That division is intentional. Medium is where broad topic discovery happens. This site is where readers can connect the book, the learning path, the examples, and the core architectural pages in one place.
What readers can expect here
Readers who arrive through the book or Medium should be able to understand what UMA is, why it exists, how the examples map to the ideas, and where to go next. The site is meant to reduce friction, not add another layer of explanation without structure.
Frequently asked question
Why separate the site from Medium?
Medium is the ongoing publication channel. The site is the stable authority hub for the book, the learning path, and the examples. Keeping both allows discovery and conversion to support each other instead of competing.
You can find the broader writing, publication links, and social channels in the footer below, or continue through the book and examples from here.