eventhorizon
nats-by-example
| eventhorizon | nats-by-example | |
|---|---|---|
| 5 | 2 | |
| 1,549 | 140 | |
| 0.5% | 9.3% | |
| 3.8 | 8.0 | |
| 3 months ago | 5 days ago | |
| Go | Go | |
| Apache License 2.0 | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
eventhorizon
-
Help to migrate a simple app from Elm to React, Angular or VanillaJS.
The todo app
-
Sync Changes to External Data Systems using Ent Hooks | ent
https://github.com/looplab/eventhorizon just got a proper outbox pattern.
-
DDD in Go -- my take on it
There is a package called EventHorizon that solves some of the issues in Go.
- Event-driven architecture resources
-
Ask HN: Are you using Go for web development?
Consultant using Go in a few client projects. Both use build-in-Docker for stability and less CI surprises. One uses GRPC with Profobuf, another is using an event sourcing toolkit I have authored [0]. Personally I use VSCode with gopls which has been working great for quiet some time now. Ordinary male files for combined documentation and usage of common operations.
[0] https://github.com/looplab/eventhorizon
nats-by-example
- NATS by Example - Examples of how to use NATS and JetStream in various languages
-
Stream Compression in NATS
> You're in your own little bubble and expect people to be mind readers.
Out of curiosity, have you asked questions in Slack or Github? If so, and you had a bad experience with the interaction, I get the sentiment and would offer help. But this comment is not constructive without context.
> I'm guessing that the documentation is bad so one has to pay for support.
The NATS project has been open source for around 12 years, and part of the CNCF since 2018. This is an incorrect statement and very poor assumption to make because the documentation doesn't make sense for you.
I 100% agree it can be improved and we are working on a new docs site, but it is not quite ready.
In case its helpful, there is an increasing collection of examples on https://natsbyexample.com with new JetStream client examples among others. If you have specific requests, feel free to open issues in the corresponding repo: https://github.com/ConnectEverything/nats-by-example
What are some alternatives?
watermill - Building event-driven applications the easy way in Go.
goes - goes is an event-sourcing framework for Go.
go-starter - An opinionated production-ready SQL-/Swagger-first RESTful JSON API written in Go, highly integrated with VSCode DevContainers by allaboutapps.
sealer - Build, Share and Run Both Your Kubernetes Cluster and Distributed Applications (Project under CNCF)
ent - An entity framework for Go
steward - Command And Control system for async management of servers, containers, workstations...basically anything that runs an operating system.
eventsourcing - A library for event sourcing in Python.
keptn - Cloud-native application life-cycle orchestration. Keptn automates your SLO-driven multi-stage delivery and operations & remediation of your applications.
pulse - ☁EventBus on Portable Pub/Sub Components☄
asyncjobs - Asynchronous Job Processor
mongodb-nats-connector - A connector that uses MongoDB's change streams to capture data changes and publishes those changes to NATS JetStream.
Juju - Orchestration engine that enables the deployment, integration and lifecycle management of applications at any scale, on any infrastructure (Kubernetes or otherwise).