Having a canvas that brings people together is a major accomplishment of
#EventModeling
. Using it to guide your organization, it's important to distinguish the "What" from the "How".
Event Modeling for the regular systems:
When you have a regular architecture and approach in your development, use
#EventModeling
to plan your solution and get your cost curve flattened as well.
Part 1 of 4 of
#wardleymaps
with Chris Daniel (
@wardleymaps
) - specifically how they complement
#EventModeling
and vice versa! Chris is a Wardley Maps expert. He takes us through solidifying our business strategy for the time tracking application.
What's the difference between
@eventmodeling
and things like
@eventstorming
?
@Rafal_Maciag
starts to dig into the subject so that you can navigate the waters of systems automation.
The new blog post can be found here:
Designing systems using diagrams that allow branching/looping leaves you open for many oversights under the illusion of the opposite. A temporal view is critical for understanding. The
#eventsourcing
mindset unlocks that secret - even if events are not used in the implementation.
There are hundreds of benefits for describing your system with adherence to
UI -> Command -> Event -> State View
as the simplest rule to decompose complexity into visible artifacts that you can plan properly against.
How do business concerns get reflected in your solutions? Probably a far cry from what you imagined..
(special thanks on
@adymitruk
's son for helping out with this!)
The front page has been updated, menus simplified and an excellent new video is in the resources page! Hope this will help you with your
#EventModeling
journey!
Next addition will be comparison chart to user story mapping, UML diagrams,
#EventStorming
and many others.
Here's today's excellent virtual meetup focusing on
#golang
#oauth
#CQRS
/ES and many other excellent examples of going from concept to implementation using
#eventmodeling
!
How can
#EventModeling
help you with
#LegacyCode
? It'll be like night and day. It wouldn't make sense to try it without it. No one talks about option 3: the side-car.
The author of
#CRDTs
Martin Kleppmann (Google docs uses something similar),
@adymitruk
and Bobby Calderwood will show these ledger approaches are the next chapter in how we explain information systems with tools like oNote. 1 hour from now!
Thank you to everyone that participated in today's session. We got the start in .net and the beginning of
#golang
and
#php
as well. We showed how we can make polyglot solutions - especially with
#eventsourcing
. The recording will be edited to a smaller format before being posted.
As opposed to UML which favours OOP, DDD which favors aggregates, etc. Event modeling gives you the freedom needed to automate with whatever architecture you like to use. Thanks to
@enordfjord
and the rest of the community for helping so many. Join us in the slack group!
How to do
#eventmodeling
for traditional systems: An important skill for bringing the rest of the world up to speed in accountability for the correctness of state in information systems. Blog post coming later.
Recently
@shanselman
published a very good video on "being overwhelmed"
There is a lot that
#eventmodeling
can do to help people just starting out in programming. We look at how we can plan a project and start in small pieces so we don't get overwhelmed!
We completed the
#wardleymap
today! Special guest
@wardleymaps
joined us to guide the finishing touches on our time tracking system. It's the best complement to
#eventmodeling
that's built for executives.
Recording will be published soon.
It's been 2 years since
#eventmodeling
was penned at the
#eventstorming
summit in Bologna, Italy. Remember this original graphic ? Now entire communities have adopted it as their standard notation. We're going to relaunch with a new intro to it tomorrow!
#EventSourcing
is not only a technical concept. It existed for thousands of years in information systems around the world. Hence, the discussion shouldn't be limited to a technical audience. You can discuss it & related topics on the
#EventModeling
forum:
The resources page has been updated and the latest article has linkable titles now. More recordings coming! In particular, please check out the series that
@k_owsiany
has put together!
Building event-based
@apachekafka
apps in record time? Event Modeling can simplify & accelerate your design and development process.
Check out this course for a comprehensive guide, plus how to design and build a ride-sharing app with
@bobbycalderwood
➡️
A shared vision for your system can't be really shared if it exists in 10 different documents. It needs to be a single blueprint. Sharing 1 thing is much easier than sharing 10 things.
Divide and conquer with
#EventModeling
by specializing in one of 4 disciplines: command populators and their potential UIs/APIs, command handlers that isolate state changes, event handlers that build views and page/report constructors that show views.
From the meetup on Friday. How we move past just "compare and swap" for event number in
#eventsourcing
. This allows arbitrary invariants across streams. This tightens the loop for eventual consistency and stores the invariant function itself as part of the event.
No matter what your technical or business tooling is (patterns, methodologies, etc), information flow is the ultimate test that you have a working system.
If your methodologies don't use real data to show what the system has and how it shows it to the users, you're flying blind.
Another
#EventModeling
workshop in the bag! Incredible transformation of so many great companies into even more effectiveness. Happy to have
@gregyoung
involved in these.
Learn about
#eventmodeling
from
@bobbycalderwood
at the
#kafkasummit
on Monday at 3pm PST (August 24th)! This is highly recommended. Registration is free. This is one you should NOT miss out on.
💡 If you are working with
#EventModeling
, don't forget to join the slack channel where other participants are sharing their experiences! You can join for free on using the link on the resources page on the main site.
The remaining sections of the virtual
#eventdriven
meetup recordings are landing on the YouTube channel over the next days. The aim is to have 2 sections a day published.
Design makes software much better. It affects planning, execution, maintenance, etc. Find ways to do design collaboratively to add transparency and reduce communication overhead such as meetings and documentation up-keep. Make the design document the communication medium.
Today,
@adymitruk
finished v1.0 of the laptop stickers that you can get very soon. Let us know what you think and if you have ideas on improving the design, hop into our slack group!
Working from an
#eventmodeling
blueprint, your software development will be predictable, uniform and give you cadance like no other method has before. It's like watching this machine do its thing:
Please join us tomorrow for Episode 4 on the Event Driven Podcast -
@VaughnVernon
the author of the red
#DDDesign
book! You'll learn a lot about
#eventsourcing
and
#cqrs
among many other subjects!
#EventSourcing
is everywhere.
Do you know the addresses you lived at in your life? You don't just forget the old address when you move. Yet we write systems like this.
If an address is in a different country, a projection called 'immigrant' is 'true'
Design by
#EventModeling
.
This is one of the best interview introductions on how to use
#eventmodeling
to collaborate between many separate teams in large distributed systems. Happy that
@bobbycalderwood
is part of the large workshop coming up.
Don't miss this large webinar tomorrow!
🚀 some people for organizations involving space travel will be there too!
Well over 1000 attendees will be there.
What
#UserStories
miss is making it clear how they all overlap.
#EventModeling
gives you a clear view of what is shared among the many functionalities of your system.
How to effectively translate business needs into features within a complex and constrained environment?
Discover how
@AXA
uses Event Modeling (introduced by
@adymitruk
) to create more cohesion between the technical and product teams in the design process
Senior developers can get 2 - 3 workflow steps implemented per week, consistently. Are you providing your teams with the
#eventmodeling
blueprint to deliver in a predictable manner so you can remove the risk of developing software in-house?
Make your blueprints the vehicle to communicate progress and examples of how the system is used. This way, you will know how to maintain the system even if you haven't touched it for years or new people are working on it.
The first episode of The Event Driven Podcast starts recording in less than 30 minutes! If you like the
#eventdriven
approaches to thinking about systems and want to be part of it, join us here:
Who should be invited to collaborate using
@EventModeling
?
Answer this question:
Who would be upset if the system is implemented badly?
Invite these people. Don't invite those that don't care.
We didn't know that workshops would be so popular in the middle of summer! It's nice to see so much interest in Event Modeling and Event Sourcing. Don't miss out and reserve your spot in August! Bonus: includes project management and source control impact.
Need an excuse to visit Vancouver? We're extending our 2 day
#EventModeling
and
#EventSourcing
virtual workshop on August 18/19 to include those who want to attend in person! Looking forward to lunch and casual chatter after if you have time.