Backend-User
User micro service for backend of HRV-Mart (by HRV-Mart)
API-Gateway
API Gateway for HRV-Mart (by HRV-Mart)
Backend-User | API-Gateway | |
---|---|---|
1 | 1 | |
1 | 0 | |
- | - | |
4.1 | 4.9 | |
10 months ago | 11 months ago | |
Kotlin | JavaScript | |
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-User
Posts with mentions or reviews of Backend-User.
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-Gateway
Posts with mentions or reviews of API-Gateway.
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
What are some alternatives?
When comparing Backend-User and API-Gateway you can also consider the following projects:
user-library
Backend-Like - Like micro-service for HRV-Mart
Backend-Cart - Cart micro-service for backend of HRV-Mart
Backend-Order - Order mirco-service for HRV-Mart application
order-library - Library for Backend-Order
detekt - Static code analysis for Kotlin
API-Call
Backend-User vs user-library
API-Gateway vs Backend-Like
Backend-User vs Backend-Cart
API-Gateway vs Backend-Order
Backend-User vs order-library
API-Gateway vs user-library
Backend-User vs Backend-Like
API-Gateway vs Backend-Cart
Backend-User vs detekt
API-Gateway vs order-library
Backend-User vs Backend-Order
API-Gateway vs API-Call