-
Notifications
You must be signed in to change notification settings - Fork 0
Implement JetStream and NATS in K8s #20
Copy link
Copy link
Closed
Labels
enhancementNew feature or requestNew feature or requestinfrastructureCI/CD, Deployment, K8s, Docker, and Server configurationCI/CD, Deployment, K8s, Docker, and Server configuration
Description
Two Tasks:
JetStream
- Learn about NATS JetStream
- Implement it in codebase for certain events
K8s configuration
- Implement a
nats.ymlservice and stateful set
Here is what I found why JetStream is necessary:
- Perfect for certain events that needs to be stored in case services crashed. Regular NATS Pub/Sub is "fire" and "forget", which means it doesn't actually store the event in case of emergencies.
- Can easily be implemented with current architecture and build (need some more configurations though)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or requestinfrastructureCI/CD, Deployment, K8s, Docker, and Server configurationCI/CD, Deployment, K8s, Docker, and Server configuration