networknt / networknt/microservices-framework-benchmark
Microservices Use Cases Design
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 715
- Forks
- 120
- PR merge metrics
- No merged PRs in 30d
Description
So far we just have a use case to gauge the raw throughput and the latency of each framework under load. For real microservices, service to service calls are adding latency and it is a critical test. I am thinking about to implement several microservice patterns with database access involved. Currently, I am planning to implement two typical pattens.
Aggregator: A calls B, C, D.
Chain: A calls B, B calls C, C calls D.
All inputs are welcome and let's work together to design the use cases to cover majority business scenarios. Thanks.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the benchmark's existing throughput and latency use case, then map how the proposed Aggregator and Chain patterns could include service-to-service calls and database access. Done should be a defined set of microservice scenarios that covers representative business patterns, but the issue does not name files, tests, or implementation entry points.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend-api-design, databases, distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100