Backlog of Refactorings

The refactorings listed on this page have not yet been written down yet, but are on our radar for future work.

Message and Operation Level

Any Message:

  • Introduce Generic Command Element a.k.a. Relax Type Information

Refactoring to patterns and technologies:

  • Introduce API Key
  • Upgrade from API Key to OAuth2/OIDC

API As a Whole

API economics:

  • Introduce Rate Limit a.k.a. Limit API Traffic, Establish Quota

API hosting/deployment:

  • Move endpoint from one API provider to another, a rough IRC pendant to the Context Mapper refactoring that moves an Aggregate from one Bounded Context to another

API Architecture

Client-server cutting as featured in Step 3 of the Stepwise Service Design activity in the design-practice-repository:

  • Split Application Frontend, variants: Provide Remote User Interface, Move Dialog Control to Client
  • Split Application Kernel, variants: Introduce Microservices, Apply Strangler Fig Pattern
  • Split Application Backend, variants: Provide Remote Database, Split/Distribute Database

More Event-Driven-Architectures (EDAs):

  • Introduce Event Streaming (coming from a request-reply exchange)
  • Switch from Full State Transfer to Event Sourcing
  • Add Snapshotting

Version 1 already has Segregate Commands from Queries. Selected EDA Concepts are featured in a Context Mapper tutorial.