Skip to content

Microservices Use Cases Design #15

Description

@stevehu

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.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions