Backend-Like
Like micro-service for HRV-Mart (by HRV-Mart)
API-Call
By HRV-Mart
Backend-Like | API-Call | |
---|---|---|
1 | 1 | |
1 | 1 | |
- | - | |
6.6 | 6.1 | |
5 months ago | 5 months ago | |
Kotlin | Kotlin | |
Apache License 2.0 | Apache License 2.0 |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Backend-Like
Posts with mentions or reviews of Backend-Like.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-08.
-
HRV-Mart
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
API-Call
Posts with mentions or reviews of API-Call.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2023-05-08.
-
HRV-Mart
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.
What are some alternatives?
When comparing Backend-Like and API-Call you can also consider the following projects:
API-Gateway - API Gateway for HRV-Mart
Backend-Product - Product microservice for backend of HRV-Mart
Backend-Cart - Cart micro-service for backend of HRV-Mart
product - Product libray
order-library - Library for Backend-Order
Backend-Auth - Auth micro service for backend of HRV-Mart
detekt - Static code analysis for Kotlin
user-library
Backend-User - User micro service for backend of HRV-Mart
Backend-Order - Order mirco-service for HRV-Mart application
Backend-Like vs API-Gateway
API-Call vs Backend-Product
Backend-Like vs Backend-Cart
API-Call vs Backend-Cart
Backend-Like vs product
API-Call vs order-library
Backend-Like vs Backend-Auth
API-Call vs Backend-Auth
Backend-Like vs detekt
API-Call vs user-library
Backend-Like vs Backend-User
API-Call vs Backend-Order