Results for “business-architecture”

Compare tradeoffs and recommend architectural patterns — dependency injection, service-oriented architecture, repository, domain events, circuit breaker, and anti-corruption layer. Use when choosing between design patterns, planning microservices boundaries, evaluating system design alternatives, or asking 'which pattern should I use' for a specific coupling or resilience problem.

Design system architecture, evaluate microservices vs monolith, create architecture diagrams, analyze dependencies, choose databases, and make technical decisions with architecture decision records.

Estructura aplicaciones Flutter en módulos independientes y reutilizables con flutter_modular, incluyendo diseño de paquetes, dependencias y configuración de Melos.

Translate design decisions into business value by reading financials, mapping competitive landscapes, and defending design work in ROI terms.

Application architecture patterns and code organization — clean architecture, hexagonal architecture, feature-based structure, dependency inversion, module boundaries, SOLID principles at module scale. Activate on "clean architecture", "hexagonal architecture", "feature-based structure", "dependency inversion", "module boundaries", "architecture pattern", "folder structure", "fat controller", "circular dependency", "IoC container". NOT for microservice decomposition (use microservices-patterns) or database schema design (use database-design-patterns).

Designs distributed system architectures, decomposes monoliths into bounded-context services, recommends communication patterns, and produces service boundary diagrams and resilience strategies.

Applies SOLID principles, clean architecture layers, dependency injection, and patterns like CQRS and event sourcing to design scalable, maintainable systems.

Produce the architecture: a lean spine of invariants that keeps everything built from it consistent, projected into whatever format the work needs. Use when the user says "create the architecture", "create technical architecture", "architecture spine", or "create a solution design".

Guides module boundaries, dependency direction, and domain structure. Do not use for local edits that leave architecture unchanged.

Plan backend domains, services, jobs, integrations, and failure handling for a product or major feature. Use when UX and product scope are defined and the team needs a production-minded backend design without defaulting to premature microservices.

Enforces system design, project structure, dependency management, error handling, testing, and documentation standards at principal-engineer level.

Builds, configures, and debugs enterprise Java applications with Spring Boot 3.x, microservices, or reactive programming, including WebFlux endpoints, JPA optimization, and Spring Security with OAuth2/JWT.

Organizes Flutter code by business features instead of technical layers, with self-contained folders for UI, logic, and data, plus a recommended project structure and dependencies.

Generate production-ready Dataverse SDK solutions with architecture recommendations, data models, and implementation code for common business use cases.