Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

\uD83D\uDDD3 Date

\uD83D\uDC65 Participants

\uD83D\uDDE3 Discussion topics

How to approach the development of the “minimum viable” application.

⤴ Decisions

  • Technology stack for the “Driver” and other mock application components. Reasoning: Mature, widely used, actively developed, and familiar to the team.

    • Java 17/Spring Boot 3.1 (latest stable versions)

    • Gradle as a build tool

    • Packaged as containers, minimal Helm chart for Sanbox Kubernetes deployment

  • Components to build in the first phase to get the development ongoing:

    • Driver application skeleton

      • “Hello world” REST API

      • No authentication yet (eventually there will be, but it can be added later)

      • Deployable to Sandbox (Helm packaging, CircleCI pipelines)

    • A mock of Payment BB (will be replaced by the real one; helps development because the driver can make actual calls through IM)

    • IM configuration

      • Subsystem config for driver app

      • Subsystem and service definition for the mock application

    • Frontend app skeleton (using the same technologies as the showcase demo)

  • No labels