Micro-capabilities¶
Jumpmind Commerce's framework supports the creation and integration of micro-capabilities. A micro-capability -- often abbreviated as "micro-cap" -- extends the concept of modular, fine-grained microservices by augmenting those services with the user interface elements associated with a given domain. Micro-caps solve the common software engineering puzzle where the benefits expected of a microservice architecture -- among them, improved scalability, better fault isolation, and faster time to market -- are muted or even neutralized by a front end which is monolithic across all domains represented by microservices.
JMC's micro-cap solution allows for the screens, widgets, and front-end state-management components specific to a business domain to be packaged, developed, deployed, and run independently of other micro-caps and without any mandated interdependencies. Individual micro-caps may integrate with each other via access controls (e.g. a button on one micro-cap's UI brings the user to another micro-cap) and via remote service calls using JMC's dynamic service invocation and discovery framework. But a micro-cap can also be launched in a "standalone" mode, where all its local functionality is available to the user without the need to have other micro-caps running and accessible. Standalone mode can greatly facilitate rapid development within a given domain.
Architecture¶
Catalog¶
The following is a catalog of JMC's current micro-capabilities. Each has its own documentation on how to configure the files, data, webhooks, and inter-micro-cap integrations necessary to fully enable it.