read.mir0n.pro

I am Yuri Miroshnikov,
founder and sole developer of Esquire Application Frameworks for backoffice systems — the kind where the org chart is the permission model. It is running, and every article here links into it.

On this page I write about the parts of the Esquire work that are arguments rather than features: what I found reading other people's code, what the measurements said, and where my own system does not do what I say it does.

• A missing filter looks exactly like a correct query

  Seven codebases that scope permissions by hierarchy. In three of them the scope can be forgotten, and a query missing it looks like a correct query. Including the one I found in my own.

• Decomposition is not microservices

  Two decisions got welded together. Where the seams are is design; how many processes you ship is deployment. Folding eight processes into four cost 0.3%.

• An environment for Domain-Driven Design

  DDD says get the generic subdomains cheaply. This is what it looks like when somebody hands them to you already joined — measured against the method, including where it does not measure well.

• Server-defined UI is not a legend

  The form builders that scarred everyone were describing screens. Describe the entity instead, keep the vocabulary small enough to finish, and let a real application do the drawing.