commandmosaic.org

What It Is

CommandMosaic is a service-building framework for Java built around the idea of “one dispatch endpoint, many commands.” Instead of forcing every business operation into a REST CRUD model, it lets each business action implement Command<T>, while CommandDispatcher handles discovery, parameter deserialization, permission checks, execution, and response serialization. In the examples, operations such as ProcessPayment and CreateOrder carry both parameters and business logic as command objects.

Core Capabilities and Ecosystem

Based on the captured content, it supports multiple runtime environments, including Plain Java, Spring Boot, Servlet Java EE/Jakarta EE, and AWS Lambda with Plain Java or Spring Boot. Spring integration is a major focus: commands can use features such as @Autowired and transactions, but the documentation specifically emphasizes that commands should not be annotated as @Component or @Service. This is because commands contain request-injected @Parameter fields and need to be created by the framework as prototype beans to ensure thread safety.

API, Documentation, and Integration

The documentation provides Maven dependencies, configuration classes, Servlet setup, the JSON format for REST calls, and curl examples, making the hands-on integration path fairly clear. Requests use a unified JSON structure containing command, parameters, auth, and protocol: CM/1.0. It is suitable both for embedding into existing systems and for building new Spring Boot or Lambda services. The documentation mentions built-in declarative and annotation-based security, but does not go into detail on the permission model.

Pricing and Open-Source Information

The page does not provide pricing, licensing, code repository, or commercial support information, so it is not possible to determine whether it is open source or closed source, nor what its long-term maintenance model looks like. For production use, it is worth further checking its Maven Central availability, source-code license, release frequency, and security response process.

Pros, Cons, and Best Fit

Its main advantage is that it significantly reduces boilerplate code for controllers, routing, and API Gateway configuration. Commands are plain Java objects, making them easy to test with JUnit, and they can be reused across Plain Java, Servlet, Spring Boot, and Lambda environments. The downside is that it weakens traditional HTTP resource semantics, so it is not a good fit for scenarios that must expose standard public REST APIs, rely on GET caching, or require fine-grained semantics such as PUT idempotency. It is better suited to complex domain operations, systems with dozens of small business actions, simplified Serverless entry points, and gradual modernization of legacy Java EE systems.

Access from China

The captured content does not provide access, mirror, or payment information, so availability from mainland China is unknown. If Maven dependency downloads are unstable, configuring a domestic Maven mirror may help. Alternatives include traditional REST with Spring MVC/JAX-RS, Axon Framework, or building a custom command-dispatch layer.