firefly-conventions

Apply Firefly conventions to enforce uniform naming and package structure across kernel, web, cqrs, and starter modules. This standardizes code organization, reduces cognitive load, and ensures consistent reactive programming practices across your codebase.

Firefly conventions enforce strict WebFlux Mono and Flux usage with non-blocking practices across modules. Applying these reactive programming rules ensures consistent asynchronous data flow and prevents blocking calls in your codebase.

Establish a uniform error handling hierarchy by applying Firefly conventions for exception usage across modules. This standardizes error handling practices, ensuring consistent exception management and reducing integration issues across reactive services.

Yes, Firefly conventions align multiple services to a single standard during migration. Applying these conventions across modules reduces integration issues by enforcing consistent build profiles, BOMs, and configuration practices across your codebase.

Firefly build and configuration conventions enforce consistent BOMs, profiles, and processors across modules. Applying these standards ensures uniform build practices, reducing configuration drift and integration issues across multiple services.

Avoid applying standardized Firefly build conventions when existing modules require highly customized configurations or non-standard BOMs. These conventions enforce strict uniformity, which may conflict with specialized build profiles or unique project constraints.