Skip to content

docs: even more clarity about per-endpoint and groups of endpoints scaling #22

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
bougyman merged 1 commit into from
Aug 4, 2025
+3 −1
Merged

docs: even more clarity about per-endpoint and groups of endpoints scaling #22

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion doc/service-api-vs-rest.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,9 @@
Leopard’s NATS ServiceApi wrapper delivers full-featured service-to-service communication, comparable with REST/GRPC.
With NATS, you get discovery, health checks, and observability, all at the protocol layer.

All Leopard does is add an Easy Button to serve these endpoints with concurrency to utilize multiple CPU cores.
All Leopard does is add an Easy Button to serve these endpoints with concurrency to scale NATS connections
horizontally, and to allow for per-endpoint (or groups of endpoints) scaling.

This abstraction preserves the simplicity of REST requests with the resilience of asynchronous messaging
under the hood.

Expand Down