Profile cover photo
Profile photo
Thomas JASKULA
70 followers
70 followers
About
Posts

EventStorming for data migration:

Here is the context, I'm working for a big insurance company in France. One of the topics is the data migration from the old legacy sytem to the new plateform. It inludes stuff like policies, claims, personal data, etc.
EventStorming on the first sight is not a right tool to explore what has to be done, or how it has to be done. One just take a sort of ETL, transforme some data from one system to another and you're done (in a simplistic way).
However I see an opportunity on how eventstorming might help here, but I'm not sure wheter it's a good idea or not. So some feedback would be welcomed :)

What I'm thinking about, is that data migration can be thought of as an accelerated lifecycle (in my case a policy), so different events can be triggered while the data is migrated like:
- TariffRecalculated (may be of interest of different contexts; Accounting, Policy managment, Communication, User access)
- InsurancePackChanged
- ClaimReported
- etc. etc.

I'm just experimenting but would be nice to have some feedback from the community.

Post has attachment
Add a comment...

Post has attachment
Add a comment...

Post has attachment

I'll be speaking at @LambdaDays in Kraków about functional programming with F# http://www.lambdadays.org
Add a comment...

Post has shared content
Nice insight from master of events :)
Explicitly separating discovery phase from design phase

During the last #evenstorming  we struggled a little when modelling more in detail. The real problem was the old one: not enough space.

We decide to move to the other side of the room and start a new roll. Instead of introducing aggregates and thus breaking consequentiality on the original roll, we started over with a new paradigm. And a new colour-based pattern matching implicit rule.

I think it worked fine, and provided some smoothness in the exploration. However, not all the discoveries of the zoomed-in model ended up quickly on the original model. So... still debatable.

However I'll guess I'll keep it working that way: explore till commands (I still love to pester domain experts around mechanics of key user decisions) and move to a different surface when it's time to pronounce the word "aggregate". 
Add a comment...

Post has attachment

Post has attachment
Add a comment...

Post has attachment
My move from C# to F#
Add a comment...

Post has attachment
Add a comment...
Wait while more posts are being loaded