Skip to content

docs: more intro clarification #21

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
Merged

docs: more intro clarification #21

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
6 changes: 4 additions & 2 deletions doc/service-api-vs-rest.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,8 +4,10 @@

== Abstract
Leopard’s NATS ServiceApi wrapper delivers full-featured service-to-service communication, comparable with REST/GRPC.
With NATS, you get complete with discovery, health checks, per-endpoint scaling, and observability.
This abstraction preserves the simplicity of REST request with the resilience of asynchronous messaging
With NATS, you get discovery, health checks, and observability, all at the protocol layer.
Copy link

Copilot AI Aug 4, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

[nitpick] The sentence structure could be improved. Consider rephrasing to: 'With NATS, you get discovery, health checks, and observability all at the protocol layer.' (removing the comma before 'all').

Suggested change
With NATS, you get discovery, health checks, and observability, all at the protocol layer.
With NATS, you get discovery, health checks, and observability all at the protocol layer.

Copilot uses AI. Check for mistakes.

All Leopard does is add an Easy Button to serve these endpoints with concurrency to utilize multiple CPU cores.
This abstraction preserves the simplicity of REST requests with the resilience of asynchronous messaging
under the hood.

This paper contrasts the NATS ServiceApi model with traditional REST, outlines its key benefits and trade-offs,
Expand Down