Backend-Like VS Backend-Product

Compare Backend-Like vs Backend-Product and see what are their differences.

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.
www.influxdata.com
featured
SaaSHub - Software Alternatives and Reviews
SaaSHub helps you find the best software and product alternatives
www.saashub.com
featured
Backend-Like Backend-Product
1 1
1 2
- -
6.6 5.9
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.

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
    16 projects | dev.to | 8 May 2023
    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

Backend-Product

Posts with mentions or reviews of Backend-Product. 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
    16 projects | dev.to | 8 May 2023
    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-Like and Backend-Product you can also consider the following projects:

API-Gateway - API Gateway for HRV-Mart

Backend-Auth - Auth micro service for backend of HRV-Mart

Backend-Cart - Cart micro-service for backend of HRV-Mart

API-Call

product - Product libray

order-library - Library for Backend-Order

detekt - Static code analysis for Kotlin

Backend-Order - Order mirco-service for HRV-Mart application