Application Model

As with the backend, you can mix and match from the features you want to use. But there is a convenience wrapper that will help you configure it all in the form of a custom component that provides the ApplicationModelContext and configures other application model contexts in one go.

However, if you're looking to use some of the microservice capabilities, you will have to use the ApplicationModelContext to provide the name of the currently running microservice. Internally, the application model uses this information to add the correct headers / query string parameters to distinguish one microservice from the other in a composition with a single ingress in front of it.

To add the application model, you simply add the following to your application:

export const App = () => {
    return (
        <ApplicationModel>
            {/* Your application */}
        </ApplicationModel>
    );
};

It has a set of configuration options you can pass it:

Option	Type	Purpose
microservice	String	Name of the microservice, which will add necessary HTTP headers on Commands and Queries
development	Boolean	Whether or not we're running in development, defaults to false
basePath	String	Base path for the application
apiBasePath	String	Base for prepended to the Command and Query requests

Example:

export const App = () => {
    return (
        <ApplicationModel apiBasePath="/some/location">
            {/* Your application */}
        </ApplicationModel>
    );
};