Backbase / golden-sample-services

This project is a development of a small set of [Backbase Service SDK](https://community.backbase.com/documentation/ServiceSDK/latest/index), Spring Boot and Spring Cloud based Microservices projects that implement microservices design patterns, cloud-native recommendations, and coding best practices.
38 stars 19 forks source link

Backbase Backbase

Backbase Golden Sample MicroServices system

System Boundary - Microservices Landscape

The microservice-based system landscape that we will use it consists of two core microservices, the Product, Review and services, all of which deal with one type of resource, and a composite microservice called the Product Composite service, which aggregates information

System Boundary

To keep the source code easy to understand, they have a minimal amount of business logic. The information model for the business objects they process is kept minimal for the same reason. In this section, we will go through the information that's handled by each microservice, plus infrastructure-related information that microservices handle.

Product service

The product service manages product information and describes each product with the following attributes:

Review service

The review service manages product review and stores the following information about each review:

Store service

The store service is a product composite service that aggregates information from the core services and presents information about a product as follows:

Required software

The following are the initially required software pieces:

  1. Backbase SDK

  2. Git: it can be downloaded and installed from https://git-scm.com/downloads.

  3. Java 17 EA: it can be downloaded and installed from https://jdk.java.net/17/.

  4. Spring Boot Initializer: This Initializer generates spring boot project with just what you need to start quickly! Start from here https://start.spring.io/.

  5. Docker Desktop: The fastest way to containerize applications on your desktop, and you can download it from here https://www.docker.com/products/docker-desktop

    For each future stage, We will list the newly required software.

Follow the installation guide for each software website link and check your software versions from the command line to verify that they are all installed correctly.

Using an IDE

We recommend that you work with your Java code using an IDE that supports the development of Spring Boot applications such as Spring Tool Suite or IntelliJ IDEA Ultimate Edition. So you can use the Spring Boot Dashboard to run the services, run each microservice test case, and many more.

All that you want to do is just fire up your IDE -> open or import the parent folder backbase-golden-sample, and everything will be ready for you.

Lombok plugin is required for your IDE: https://projectlombok.org/setup/overview

Playing With Backbase Golden Sample Project

Cloning It

The first thing to do is to open git bash command line, and then simply you can clone the project under any of your favorite places as the following:

> git clone 

This project will be developed in steps, and each such step will be a release in its own, so you can go back and forward between versions to see the differences and how adding things solve specific problems we face.

The main idea of the project for now is three microservices: Store, Product and Review. Product and Review microservices are CRUD applications saving data in a MySQL Database, and Store Service calls the other two services (Product and Review) statically to generate client aggregate response for a specific product.

Steps

https://github.com/Backbase/golden-sample-services/issues

Getting started

The first stage, aka (Release v1.0), is about creating and implementing a set of Microservices exposing a RestAPI and with Database access.

Creating a Set of communicating Microservices (Release v1.0)

The following points are covered in this 1st stage (other stages topics will be documented in each release notice):

Resources

Contributions

Please create a branch and a PR with your contributions. Commit messages should follow semantic commit messages