From d8a5a511c3be329505d46541a2f472ac748c3337 Mon Sep 17 00:00:00 2001 From: "Tj (bougyman) Vanderpoel" Date: Sun, 3 Aug 2025 22:14:57 -0500 Subject: [PATCH] docs: even more clarity about per-endpoint and groups of endpoints scaling --- doc/service-api-vs-rest.adoc | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/doc/service-api-vs-rest.adoc b/doc/service-api-vs-rest.adoc index 4edc5e7..8c6bd99 100644 --- a/doc/service-api-vs-rest.adoc +++ b/doc/service-api-vs-rest.adoc @@ -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.