Aim of this project is to provide a basic working example of a microservice application from scratch (Not entirely from scratch. We will be linking small subset of existing projects that I have built overtime) with Spring Boot with a set project starters, Netflix OSS(Zuul,Eureka, and Feign), Hibernate, and JJWT
The Project will divided into 4 sub-modules:
- friflow-admin
- friflow-api
- friflow-service-registry
- friflow-api-gateway
Here's our functional services.
The friflow-admin will act as our Identity management service that handles token issuance, persisting user information such as roles,username,password, and etc. We can roll up our own or use an existing identity management API like Auth0
Database Config. (Change them accordingly)
spring.datasource.url=jdbc:postgresql://localhost:5432/friflow-admin
spring.datasource.username=postgres
spring.datasource.password=postgres
spring.datasource.driver-class-name=org.postgresql.Driver
spring.jpa.database-platform=org.hibernate.dialect.PostgreSQLDialect
spring.jpa.show-sql=true
spring.jpa.generate-ddl=true
spring.jpa.hibernate.ddl-auto=updateThe database config for friflow-admin can be found under
friflow-admin\src\main\resourcesrunning friflow admin - under friflow-admin execute the mvn spring-boot:run command
mvn spring-boot:runThe Friflow-api is an existing system we will be plugging in. It contains the some of the core business logic of our application. The Friflow-api is a ticketing service/a small workflow management system that issues various types tickets such as quotation tickets which contains product inquiries,pricing,materials used.
Database Config. (Change them accordingly)
spring.datasource.url=jdbc:postgresql://localhost:5432/friflow
spring.datasource.username=postgres
spring.datasource.password=postgres
spring.datasource.driver-class-name=org.postgresql.Driver
spring.jpa.database-platform=org.hibernate.dialect.PostgreSQLDialect
spring.jpa.show-sql=true
spring.jpa.generate-ddl=trueThe database config for friflow-admin can be found under
friflow-api\src\main\resourcesrunning friflow api - under friflow-api execute the mvn spring-boot:run command
mvn spring-boot:runThere are several patterns in distributed systems that can aid us in making our Functional/Core services work together -- and they are called as Infrastructure Services. Spring cloud provides those tools to implement some of those Patterns and these are the ff:
The Friflow-api-gateway is our Edge service. It would act as main entry point of clients. It’s primary purpose to aggregate results from different service if needed, and act as router/or proxy for our backend service. This is implemented using Zuul, And Feign, and Eureka. . More information about The Api Gateway Pattern can be here
The friflow-service-registry is the Service registry of our applications. Services self-registered. More information about service registry can be here Our Service Registry is implemented using Eureka Look, a list!