The Standard Architecture

The Florance pattern is an architectural design standard that separates systems into Brokers, Services, and Exposers to enforce a strict single flow of data and consistent exception taxonomy across scalable systems.

Structure your scalable architecture by scaffolding explicit roles: Brokers for data access, Services for Foundation, Processing, Orchestration, and Aggregation logic, and Exposers for endpoints, ensuring a strict single flow of data.

You should use ValueTask-based async methods when enforcing The Standard architecture's async contract, which enforces consistent asynchronous conventions across all brokers, services, and exposers during design reviews and refactors.

Yes, you can use these architecture templates for refactoring an existing codebase by applying The Standard's rules to restructure your code into Brokers, Services, and Exposers with strict naming and dependency injection wiring.

The best way to enforce consistent exception taxonomy is to apply The Standard architecture rules, which codify strict naming, enforce the Florance pattern, and standardize exception handling across all services and brokers.

No specific external dependencies are required to implement The Standard architecture; it provides scaffolders and guidance for dependency injection wiring and standardizing brokers, services, and exposers in your environment.