Endpoint to get the transaction in its most recent state

GET /sap-transactionservice/get/v1/{txnId}

Should return the latest entry for the txnId

At the moment, ConsentAsAService is being designed using the microservices approach. Is this really the best option given the circumstances?

Taking the following "advantages" of microservices:

Decomposing

"So, instead of having one large application, we decompose it into separate, different, mini-applications (services)"

As this is a prototype project developed by one person for a University Dissertation, will it grow substantially large enough that it makes sense to decompose?

Single Function

How much scope would each microservice have on a project of this size?

Well-Defined interfaces

Can also be considered with a monolith

Independence

See Single Function

Small Teams / Collaboration / Minimising Need for communication between teams

Single dev project so this doesn't really apply

Other considerations

Microservices increase the tech debt I would have on this project as each microservice would need a client implementation on top of the client implementation required for the user-facing gateway. Is this a WORTHWHILE use of time?

Add the necessary components needed for SAP-TransactionService to work

SAP-TransactionService-IMPL should be compiled into the SAP-TransactionService-WAR project and all endpoints must be exposed from Tomcat

POST request for updating an existing transaction:

POST /SAP-TransactionService/update/v1/

Should take TxnId, TxnStatus as a parameter eg

{
     txnId: 1f473f4c-f02d-4642-8f3a-8f88e367f915
     status: FULFILLED
}

Should return the UUID for the updated transaction

Common dependencies and tasks should be offloaded into a custom gradle project for simpler SAP generation

Add A Spring Eureka Discovery Service

This story focuses on developing the first iteration of the transaction service as well as setting up any tooling required for future SAP services.

Story Goals

• Compiles to a WAR #2
• Configure Database Connections and create required tables/transactions for SAP-TransactionService #9
• Gradle plugin for simpler SAP creation #3
• Endpoint to create a new transaction #4
• Endpoint to update a transaction (takes a given txnId) #5
• Endpoint to get transaction details #6
• Add a Spring Discovery Service for simplified microservice configuration #7

The current architecture of DA-Lib is causing circular dependency issues & complications when implementing. The following model needs to be applied:

POST request for creating a new transaction:

POST /SAP-TransactionService/new/

Should take TxnStatus as a parameter eg

{
     status: CREATED
}

Should return the UUID for the transaction