Difference between revisions of "NATS"
Jump to navigation
Jump to search
(Created page with "https://docs.nats.io/") |
|||
| Line 1: | Line 1: | ||
https://docs.nats.io/ |
https://docs.nats.io/ |
||
| + | |||
| + | ==What is NATS?== |
||
| + | |||
| + | NATS is a connective technology that powers modern distributed systems. A connective technology is responsible for addressing, discovery and exchanging of messages that drive the common patterns in distributed systems; asking and answering questions, aka services/microservices, and making and processing statements, or stream processing. |
||
| + | |||
| + | |||
| + | ==Use Cases== |
||
| + | NATS can run anywhere, from large servers and cloud instances, through edge gateways and even IoT devices. Use cases for NATS include: |
||
| + | * Cloud Messaging |
||
| + | ** Services (microservices, service mesh) |
||
| + | ** Event/Data Streaming (observability, analytics, ML/AI) |
||
| + | * Command and Control |
||
| + | ** IoT and Edge |
||
| + | ** Telemetry / Sensor Data / Command and Control |
||
| + | * Augmenting or Replacing Legacy Messaging Systems |
||
| + | |||
| + | ==Docker== |
||
| + | |||
| + | https://hub.docker.com/_/nats |
||
Latest revision as of 14:25, 9 September 2022
What is NATS?
NATS is a connective technology that powers modern distributed systems. A connective technology is responsible for addressing, discovery and exchanging of messages that drive the common patterns in distributed systems; asking and answering questions, aka services/microservices, and making and processing statements, or stream processing.
Use Cases
NATS can run anywhere, from large servers and cloud instances, through edge gateways and even IoT devices. Use cases for NATS include:
- Cloud Messaging
- Services (microservices, service mesh)
- Event/Data Streaming (observability, analytics, ML/AI)
- Command and Control
- IoT and Edge
- Telemetry / Sensor Data / Command and Control
- Augmenting or Replacing Legacy Messaging Systems