Giters

tushark-16bit / books-service-entrypoint

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Book Ecommerce Microservices

this project implements backend of a book ecommerce platform as microservices

Tech Stack

Server:

  • Spring Boot
    • Web
    • Actuator
  • Spring Cloud
    • Eureka Service Registry
    • Resilience4j
    • Tracing(Zipkin/Micrometer)
    • Api Gateway
    • Open Feign(Microservice Communication)
  • Spring Security
    • OAuth2 (Client / Resource Server)
    • Okta
  • Spring Data
    • JPA
    • Hibernate
  • Messaging
    • Kafka

Documentation

There are three microservices implemented around domain:

and Api-Gateway is used as security endpoint and load balancer for services

These microservices were developed using Hexagonal Architecture(Ports and Adapters) using DDD principles. The microservice created around a domain implements business rules which are independent of techinal implementations.

The project structure implemented as:

  • domain
  • application
  • infrastructure

Where Domain is responsible for the representation of domain objects, e.g. Book in Book-Service, Cart in Cart-service and Purchase-Order in Purchase-service.

Application layer handles the business logic implemented with interfaces for the logic that may interact with outside. Also called Ports layer. Application layer is further divided into in and out. where in represents the input/ entrypoint into the service/ or driving port and out represents the connections to database or another microservices, Also called driven ports.

Infrastructure layer represents the implementation of application layer ports, where a web controller as driving port implementation or a database adapter as driven port implementation may be used.

The Incoming Request into application are seggregated as command and queries using CQRS principles, where the command(update) responsibilty is separated from Query(read) responsibilty.

Deployment

To deploy this clone to local and run

  docker-compose up

Your Docker Daemon needs to be running for this command. This command will automatically fetch the packages deployed in different docker container registries and put up the application.

Initially, the user will have to login from browser using

    http:localhost:8080/auth/login

A sample Okta user has been created for running with security:

    username: sample.tester@gmail.com
    password: Okta@1User

The access token retrieved with this can then be used to authenticate requests to gateway exposed at port localhost:8080

The endpoints exposed can be viewed from respective swaggers as:

  http://localhost:8080/book/swagger-ui/index.html
  http://localhost:8080/cart/swagger-ui/index.html

PLEASE AUTHENTICATE ALL REQUESTS OTHER THAN ACTUATOR AND SWAGGER WITH OAUTH2.0 AND ACCESS TOKEN AS RETRIEVED ABOVE.

Tracing of requests through the microservices exposed at http://localhost:9411/zipkin

Routing

Api gateway routes requests as following:

  • http://localhost:8080/cart/** -> Load Balanced Instance of Cart-Service registered with Service Registry

  • http://localhost:8080/book/** -> Load Balanced Instance of Book-Service registered with Service Registry

  • http://localhost:8080/purchase/** -> Load Balanced Instance of Book-Purchase-Service registered with Service Registry

For example: to read all books: localhost:8080/book/read/all as GET Request with OAuth2.0 Access token applied

Author

About