An example project based around a 'offer' demonstrating Spring Boot and exposing a REST API.

Technologies used:

• Spring Boot
• H2 database
• PlantUML for diagrams. Diagrams generated by gravizo.com.

Clone this repository and then run:

mvn clean install

Please note: this project has been tested on Windows 10 and Linux (Ubuntu) using JDK 8.

This project has a number of modules, which albeit don't contain much code, but are there to show how a complex system could be split up:

• Database - contains schema DDL and DML to populate tables with initial data.
  • Database creation and data population performed by running standard Maven clean install, there is a simple Spring Boot application and this effectively bootstraps the database creation using some POC (Proof Of Concept) type features that Spring Boot has (schema.sql and data.sql).
• Domain - domain object(s).
• Persistence - Persistence layer for domain objects.
• Service - Service layer interacting with persistence and controlling transactions.
• Web - REST controllers.

The project could have been split into other module structures, namely something like the below:

• Core
• Web

• Single module - i.e. like Spring Boot starter.

After building the project:

cd offer-example-web

then:

mvn spring-boot:run

This will start the Spring Boot fat JAR webapp.

Please note: the documentation is basic and manually generated - see "Things To Do", such as improving the documentation.

This API aimed at being 'Level 2' on the REST maturity model: https://martinfowler.com/articles/richardsonMaturityModel.html

Resource: /v1/offers/{merchantIdentifier}
Method: POST  <-- Note: this is POST instead of PUT because the Create Offer operation is not idempotent - the Offer Identifier is generated by the server-side.
Request body: Offer JSON (see below)
Response code: 201 for Offer created, 400 for bad request - invalid offer.
Response body: Offer Identifier of newly created Offer

Offer JSON - offerIdentifier not required because it is assigned by the service.

{
  "merchantIdentifier": "merchant-123",
  "description": "DESCRIPTION-123",
  "offeringIdentifier": "offering-123",
  "price": 1.23,
  "currencyCode": "GBP",
  "activeStartDate": "2018-01-01 00:00:00.000",
  "activeEndDate": "2019-02-03 23:59:59.000",
  "statusCode": "A"
}

Resource: /v1/offers/{merchantIdentifier}/{offerIdentifier}  
Method: DELETE  
Response code: Return 200 for OK, 404 for Offer not found

Resource: /v1/offers/{merchantIdentifier}
Method: GET
Response code: Return 200 for OK
Response body: active Offers JSON

Resource: /v1/offers/{merchantIdentifier}/{offerIdentifier}
Method: GET
Response code: Return 200 for OK, 404 for Offer not found
Response body: active Offer

• Change timestamp to local date time.
• Document REST API
• Add caching of currencies, so that currency code can be quickly checked, rather than simply relying on the database foreign key constraint.
• Tidy up application.properties, as currently in a few modules.
• Look at the //TODO: comments, add issues or remove.
• Auditing and accountability columns omitted from schema.
• Request correlation id.

• Application context slicing by virtue of repository module.
• Application context slicing using Spring Boot's support.
• DateTimeService created so more control over dates could be added - i.e. to control what date/time it is beyond simply getting current system time.
• Please note: be careful with H2 local file locking - i.e. make sure it isn't locked by another process or a locking exception will be raised.
• Offer identifier, merchant identifier and offering identifier (the link to a product/service) are strings to allow UUID values, helping bridge microservices, where unique identifiers might need to be embedded from one microservice to another based on the service's bound context. For example, product/service and merchant might be separate microservices.

Timezones have been ignored.

Bump