Start typing to search articles and topics.
Architecture
System design, modularity, boundaries, and integration patterns for web platforms that need to remain understandable, maintainable, and resilient as they grow.
Technical debt is not a backlog of everything that could be cleaner. In a mature Umbraco platform, the useful question is economic and operational: what cost...
Performance diagnosis is not a sequence of optimizations. It is an evidence loop: define the symptom, reproduce or observe it, decompose the latency, form a...
Umbraco projects rarely become expensive because of one catastrophic decision. Cost grows when content architecture, custom code, data, search,...
ASP.NET Core does not force you into one application architecture. That freedom is useful, but it also makes it easy to accumulate layers, abstractions and...
Umbraco 9 did more than replace one runtime with another. Moving from .NET Framework to ASP.NET Core changed where Umbraco could run, how projects were...
A production-focused guide to designing explicit contracts, handling realistic failures, protecting trust boundaries, and recognizing defensive-programming...
An Umbraco project can be stable in production and still be expensive to change, difficult to upgrade, fragile under failure, or dependent on assumptions...
Authenticate an existing WordPress user from a .NET application by sending the user's credentials to the JWT Authentication for WP REST API token endpoint....
Large DELETE operations can generate substantial transaction-log activity, increase blocking, and make rollback expensive. This guide shows a...
Good Umbraco performance is not a cache setting or a collection of isolated tricks. It is the result of keeping expensive work on the right path, at the...