You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: CONTRIBUTING.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
## CONTRIBUTING
2
2
3
-
Where it makes sense, raise GitHub issues for any questions so others can benefit from the discussion, or follow the links to [the DDD-CQRS-ES #equinox Slack channel](https://ddd-cqrs-es.slack.com/messages/CF5J67H6Z) above for quick discussions.
3
+
Where it makes sense, raise GitHub issues for any questions so others can benefit from the discussion, or follow the links to [the DDD-CQRS-ES #equinox Discord channel](https://discord.com/channels/514783899440775168/1002635005429825657) above for quick discussions.
4
4
5
5
This is an Open Source project for many reasons; some central goals:
Equinox is a set of low dependency libraries that allow for event-sourced processing against stream-based stores handling:
4
4
* Snapshots
@@ -64,7 +64,7 @@ We believe the fact Equinox is a library is critical:
64
64
- It gives you the ability to pick your preferred way of supporting your event sourcing system.
65
65
- There's less coupling to worry about as your application evolves over time.
66
66
67
-
_If you're looking to learn more about and/or discuss Event Sourcing and it's myriad benefits, trade-offs and pitfalls as you apply it to your Domain, look no further than the thriving 4000+ member community on the [DDD-CQRS-ES Slack](https://github.com/ddd-cqrs-es/slack-community); you'll get patient and impartial world class advice 24x7 (there are [#equinox](https://ddd-cqrs-es.slack.com/archives/CF5J67H6Z), [#eventstore](https://ddd-cqrs-es.slack.com/archives/C0K9GBSSG) and [#sql-stream-store](https://ddd-cqrs-es.slack.com/archives/C0HM1K6DN) channels for questions or feedback)._ ([invite link](https://j.mp/ddd-es-cqrs))
67
+
_If you're looking to learn more about and/or discuss Event Sourcing and it's myriad benefits, trade-offs and pitfalls as you apply it to your Domain, look no further than the thriving 4000+ member community on the [DDD-CQRS-ES Discord](https://github.com/ddd-cqrs-es/community); you'll get patient and impartial world class advice 24x7 (there are [#equinox](https://discord.com/channels/514783899440775168/1002635005429825657), [#eventstore](https://discord.com/channels/514783899440775168/762672037113757746) and [#sql-stream-store](https://discord.com/channels/514783899440775168/762671996550774804) channels for questions or feedback)._ ([invite link](https://discord.gg/sEZGSHNNbH))
68
68
69
69
# Features
70
70
@@ -699,7 +699,7 @@ OK, I've read the README and the tagline. I still don't know what it does! Reall
699
699
700
700
### Should I use Equinox to learn event sourcing ?
701
701
702
-
You _could_. However the Equinox codebase here is not designed to be a tutorial; it's also extracted from systems with no pedagogical mission whatsoever. [FsUno.Prod](https://github.com/thinkbeforecoding/FsUno.Prod) on the other hand has this specific intention, walking though it is highly recommended. Also [EventStore](https://eventstore.org/), being a widely implemented and well-respected open source system has some excellent learning materials and documentation with a wide usage community (search for`DDD-CQRS-ES` mailing list and slack).
702
+
You _could_. However the Equinox codebase here is not designed to be a tutorial; it's also extracted from systems with no pedagogical mission whatsoever. [FsUno.Prod](https://github.com/thinkbeforecoding/FsUno.Prod) on the other hand has this specific intention, walking though it is highly recommended. Also [EventStore](https://eventstore.org/), being a widely implemented and well-respected open source system has some excellent learning materials and documentation with a wide usage community (search for`DDD-CQRS-ES` mailing list and Discord).
703
703
704
704
Having said that, we'd love to see a set of tutorials written by people looking from different angles, and over time will likely do one too ... there's no reason why the answer to this question can't become "**of course!**"
705
705
@@ -715,7 +715,7 @@ You can. Folks in Jet do; but we also have systems where we have no plans to use
715
715
716
716
You'll learn a lot from building your own equivalent wrapping layer. Given the array of concerns Equinox is trying to address, there's no doubt that a simpler solution is always possible if you constrain the requirements to specifics of your context with regard to a) scale b) complexity of domain c) degree to which you use or are likely to use >1 data store. You can and should feel free to grab slabs of Equinox's implementation and whack it into an `Infrastructure.fs` in your project too (note you should adhere to the rules of the [Apache 2 license](LICENSE)). If you find there's a particular piece you'd really like isolated or callable as a component and it's causing you pain as [you're using it over and over in ~ >= 3 projects](https://en.wikipedia.org/wiki/Rule_of_three_(computer_programming)), please raise an Issue though !
717
717
718
-
Having said that, getting good logging, some integration tests and getting lots of off-by-one errors off your plate is nice; the point of [DDD-CQRS-ES](https://github.com/ddd-cqrs-es/slack-community) is to get beyond toy examples to the good stuff - Domain Modelling on your actual domain.
718
+
Having said that, getting good logging, some integration tests and getting lots of off-by-one errors off your plate is nice; the point of [DDD-CQRS-ES](https://github.com/ddd-cqrs-es/community) is to get beyond toy examples to the good stuff - Domain Modelling on your actual domain.
0 commit comments