A community for Domain Driven Design (DDD), Command Query Responsibility Seperation (CQRS) and Event Sourcing Enthusiasts. Language and platform agnostic. Technical and non-technical welcome.
Popular Channels
4732
#announcements
We've moved to Discord! <[URL]>
Code of conduct: <[URL]>
This channel is for team-wide communication and announcements. All team members are in this channel.
4508
#off-topic
Non-work banter, water cooler conversation and developer group therapy. Friends of <@U0HCLMWGP> get in free.
Messages are lost to us. But Slack has them
A place for non-work-related flimflam, faffing, hodge-podge or jibber-jabber you'd prefer to keep out of more focused work-related channels.
4048
#general
On-topic discussions & rubber-ducking on DDD-CQRS-ES. To join: <[URL]>
General banter and generally on topic. Be nice :slightly_smiling_face:
Basic Concepts Found here: <[URL]>
3509
#eventsourcing
I should know better than to try
*using hypotheticals by now.
*build my own store for prod
*making a good channel topic
Don't
*Name Your Event as The FQDN of the Class to ease serialization
* Share Your streams with strangers.
* use Kafka as store
1193
#eventstore
<[URL]> This isn't an official support channel, more of a user group / fans-of.
<[URL]>
For discussions related to [URL]
1187
#event-storming
<[URL]> is not for big-picture -event-storming, it used to be called RealTimeBoard BTW
<[URL]>
<[URL]>
what it says
812
#dotnet
All IoC jokes must be abstract. Cynics welcome
Topics per day
Mo. : STJ
Tu: DI, dotnet drama
Th: F#
await if
A) you need the return value now
B) inside a try-catch
C) in a using block
D) at the top of the call stack
Consensus: Records are not VO
.NET related topics. Should be try to be on topic with this Slack team.
634
#event-modeling
Background info: <[URL]>
Subjects around "single-flow event storming" that Adam Dymitruk practices
585
#jobs
Topics regarding job and work opportunities only. Use threads to discuss specific job items. Discussions should be held in appropriate channel.
We're hiring
509
#dddeu
June 2022, Amsterdam
Domain Driven Design Europe <[URL]>
Timezones
Number of members by timezones in UTC. DST applied.
