Skip to content

Deck Plan Fundamentals

Deck Plan Composition

Deck Plan is composed by many elements. Below there is a diagram that tries to illustrate the composition:

Deck Plan Composition

In detail, the key components are:

  • Deck Plan Application: This is the front-end application on which the map and locations are displayed. Deck Plan currently uses Leaflet javascript library to serve the maps.
  • Deck Plan BFF: Exposes all the required endpoints to suffice the front-end application needs.
  • Deck Plan File Server: It is a file server similar to the virtual directories used in IIS for AMA Deck Plan. For more information, source.
  • Deck Plan Application Service: Its a back end service that exposes mutations, localizations and some other resources the application will need to work.
  • General Arrangements microservice: this service is in charge of maintaining most of the key entities of deck plan. For more information read, general arrangements.

  • Integration Services: Deck Plan has some integrations with other services, whose are defined by the current architecture. Currently, there are two types of integrations:

    1. Integrations with optional Services.
    2. Integrations with required Services.

    The integrations will be boarded in detail at the integrations section