Our great sponsors
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
-
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
-
-
-
-
-
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
In order to create a scalable back-end I use micro-service architecture. Current version of HRV-Mart back-end consist of Product-Microservice, User-Microservice, Auth-Microservice, Order-Microservice, Cart-Microservice, Like-Micorservice and API-Gateway. Above micro-services are loosely couple and communication between them happens via Apache Kafka. In order to make them more secure, I added unit tests. The master branch is protected via branch protection rules
In order to create a scalable back-end I use micro-service architecture. Current version of HRV-Mart back-end consist of Product-Microservice, User-Microservice, Auth-Microservice, Order-Microservice, Cart-Microservice, Like-Micorservice and API-Gateway. Above micro-services are loosely couple and communication between them happens via Apache Kafka. In order to make them more secure, I added unit tests. The master branch is protected via branch protection rules
In order to create a scalable back-end I use micro-service architecture. Current version of HRV-Mart back-end consist of Product-Microservice, User-Microservice, Auth-Microservice, Order-Microservice, Cart-Microservice, Like-Micorservice and API-Gateway. Above micro-services are loosely couple and communication between them happens via Apache Kafka. In order to make them more secure, I added unit tests. The master branch is protected via branch protection rules
In order to create a scalable back-end I use micro-service architecture. Current version of HRV-Mart back-end consist of Product-Microservice, User-Microservice, Auth-Microservice, Order-Microservice, Cart-Microservice, Like-Micorservice and API-Gateway. Above micro-services are loosely couple and communication between them happens via Apache Kafka. In order to make them more secure, I added unit tests. The master branch is protected via branch protection rules
In order to create a scalable back-end I use micro-service architecture. Current version of HRV-Mart back-end consist of Product-Microservice, User-Microservice, Auth-Microservice, Order-Microservice, Cart-Microservice, Like-Micorservice and API-Gateway. Above micro-services are loosely couple and communication between them happens via Apache Kafka. In order to make them more secure, I added unit tests. The master branch is protected via branch protection rules
In order to create a scalable back-end I use micro-service architecture. Current version of HRV-Mart back-end consist of Product-Microservice, User-Microservice, Auth-Microservice, Order-Microservice, Cart-Microservice, Like-Micorservice and API-Gateway. Above micro-services are loosely couple and communication between them happens via Apache Kafka. In order to make them more secure, I added unit tests. The master branch is protected via branch protection rules
In order to create a scalable back-end I use micro-service architecture. Current version of HRV-Mart back-end consist of Product-Microservice, User-Microservice, Auth-Microservice, Order-Microservice, Cart-Microservice, Like-Micorservice and API-Gateway. Above micro-services are loosely couple and communication between them happens via Apache Kafka. In order to make them more secure, I added unit tests. The master branch is protected via branch protection rules
In HRV-Mart organisation, their are some libraries created which are meant to use by multiple micro-services. For example, Custom-Pageable is use to add pagination in Backend-Product, Backend-Order, Backend-Like and Backend-Cart, Cart-Response contains cart model, Product-library which contains product model, user-library is use to receive create user request from auth micro-service and order-library is use to receive order request. Both of them receive requests via Kafka. Both Cart-library and Product-library are use to calculate total cost of cart. They get data from REST-endpoint of Cart and Product respectively by using API-Call library.
In HRV-Mart organisation, their are some libraries created which are meant to use by multiple micro-services. For example, Custom-Pageable is use to add pagination in Backend-Product, Backend-Order, Backend-Like and Backend-Cart, Cart-Response contains cart model, Product-library which contains product model, user-library is use to receive create user request from auth micro-service and order-library is use to receive order request. Both of them receive requests via Kafka. Both Cart-library and Product-library are use to calculate total cost of cart. They get data from REST-endpoint of Cart and Product respectively by using API-Call library.
In HRV-Mart organisation, their are some libraries created which are meant to use by multiple micro-services. For example, Custom-Pageable is use to add pagination in Backend-Product, Backend-Order, Backend-Like and Backend-Cart, Cart-Response contains cart model, Product-library which contains product model, user-library is use to receive create user request from auth micro-service and order-library is use to receive order request. Both of them receive requests via Kafka. Both Cart-library and Product-library are use to calculate total cost of cart. They get data from REST-endpoint of Cart and Product respectively by using API-Call library.
In HRV-Mart organisation, their are some libraries created which are meant to use by multiple micro-services. For example, Custom-Pageable is use to add pagination in Backend-Product, Backend-Order, Backend-Like and Backend-Cart, Cart-Response contains cart model, Product-library which contains product model, user-library is use to receive create user request from auth micro-service and order-library is use to receive order request. Both of them receive requests via Kafka. Both Cart-library and Product-library are use to calculate total cost of cart. They get data from REST-endpoint of Cart and Product respectively by using API-Call library.
In HRV-Mart organisation, their are some libraries created which are meant to use by multiple micro-services. For example, Custom-Pageable is use to add pagination in Backend-Product, Backend-Order, Backend-Like and Backend-Cart, Cart-Response contains cart model, Product-library which contains product model, user-library is use to receive create user request from auth micro-service and order-library is use to receive order request. Both of them receive requests via Kafka. Both Cart-library and Product-library are use to calculate total cost of cart. They get data from REST-endpoint of Cart and Product respectively by using API-Call library.
In HRV-Mart organisation, their are some libraries created which are meant to use by multiple micro-services. For example, Custom-Pageable is use to add pagination in Backend-Product, Backend-Order, Backend-Like and Backend-Cart, Cart-Response contains cart model, Product-library which contains product model, user-library is use to receive create user request from auth micro-service and order-library is use to receive order request. Both of them receive requests via Kafka. Both Cart-library and Product-library are use to calculate total cost of cart. They get data from REST-endpoint of Cart and Product respectively by using API-Call library.
In protection rules, I added build workflow in Require status checks to pass before merging. This is to ensure that before merging code in master branch, build should run successfully. I also added Jacoco Code Coverage to make sure that enough unit tests are available in project and Detekt to make sure that code in project is readable. I added them in build configuration. Even if one of them gives error, build will fail. Whenever, someone push code in pull request, build action will run and check if build is running successfully or not.
In order to create a scalable back-end I use micro-service architecture. Current version of HRV-Mart back-end consist of Product-Microservice, User-Microservice, Auth-Microservice, Order-Microservice, Cart-Microservice, Like-Micorservice and API-Gateway. Above micro-services are loosely couple and communication between them happens via Apache Kafka. In order to make them more secure, I added unit tests. The master branch is protected via branch protection rules
In protection rules, I added build workflow in Require status checks to pass before merging. This is to ensure that before merging code in master branch, build should run successfully. I also added Jacoco Code Coverage to make sure that enough unit tests are available in project and Detekt to make sure that code in project is readable. I added them in build configuration. Even if one of them gives error, build will fail. Whenever, someone push code in pull request, build action will run and check if build is running successfully or not.