Developing Applications

This section describes how to code, develop and configure Talon applications.

From a developer's perspective, a Talon application is comprised of the following artifacts:

  • Message Model

    • The application has a single ADM based XML message model shared across all the application's microservices. This model contains the definition of all messages shared across all the application's microservices. The model is used to generate classes that are used as messages exchanged between microservices.

  • Microservices

    • The application is comprised of one or more microservices. The development artifacts for each microservice are as follows:

      • State Model (only for State Replication microservices)

        • A State Replication microservice defines its state in an ADM based XML state model. Each state model is private to the microservice and generates classes that serve to store application data and state. EventSourced microservices store data and state in regular Java objects and so do not need a state model

      • User Code

        • User code in a microservice is comprised of the following:

          • The HA Policy Declaration

          • Lifecycle Methods

          • Microservice Initializers

          • Message Filters

          • Message Handlers

  • Configuration

    • The application has a single DDL based XML configuration model shared across all the application's microservices. This model contains application wide configuration, such as configuration of the underlying messaging bus (see Messaging Model) and configuration of the platform runtime of each of the application's microservices. The configuration model configures the Talon runtime and, therefore, needs to be provided to the microservices only when the microservices are run.

For more information

PreviousOperating ModelNextMicroservice Template

Last updated