Python for our modeling allows and try to put on modeling is goes even further because you have a third time axe which is the decision axis. It's very difficult to make those queries over three time axes if you can explain a little bit on this decision time so maybe extending from the same example of the child is born what would be an example of the decision time for tri modelingYeah the decision time is set as well by the clerk so the fact that the child was born on the three of April that would be the valid time but in that case the decision time I know from the business point of view I don't think it has any meaning here it probably would be set to the day
“Time is important for business. We have to model it explicitly. Temporal modeling means that we use time-based artifacts as first modeling citizens."
Tomasz Jaskula is the CTO and co-founder of Luteceo and an experienced software developer and architect. In this episode, we started off discussing how Domain-Driven Design (DDD) influenced Tomasz’s view on software development approach and its relation with functional programming. Tomasz then explained in depth about the time concept in business applications and temporal modeling, in particular, bi-temporal modeling. He mentioned the different concepts of time in temporal modeling, explaining them using an example for easier illustration. We then extended our discussion further to Event Sourcing, understanding the key concept, its relation to temporal modeling, when we should decide to use Event Sourcing in our application, and some available tools that can help us implement Event Sourcing.
Listen out for:
- Career Journey - [00:04:58]
- DDD and Bounded Context - [00:08:56]
- DDD and Functional Programming - [00:13:24]
- Temporal Modeling - [00:14:47]
- 3 Different Types of Time - [00:21:13]
- Event Sourcing - [00:25:42]
- When to Use Event Sourcing - [00:28:13]
- Event Sourcing Tools - [00:34:02]
- 3 Tech Lead Wisdom - [00:36:10]
_____
Tomasz’s Bio
Tomasz Jaskuła is CTO and co-founder of Luteceo, a software consulting company in Paris. Tomasz has more than 20 years of professional experience as a developer and software architect, and worked for many companies in the e-commerce, industry, insurance, and financial fields. He has mainly focused on creating software that delivers true business value, aligns with strategic business initiatives, and provides solutions with clearly identifiable competitive advantages. Tomasz is also a main contributor to the OSS project XOOM for the .NET platform. In his free time, Tomasz perfects his guitar playing and spends time with his family. He recently wrote a book with Vaughn Vernon titled “Strategic Monoliths and Microservices” published by Addison-Wesley.
Follow Tomasz:
Our Sponsor
Are you looking for a new cool swag?
Tech Lead Journal now offers you some swags that you can purchase online.
These swags are printed on-demand based on your preference, and will be delivered safely to you all over the world where shipping is available.
Check out all the cool swags by visiting https://techleadjournal.dev/shop.
Like this episode?
Subscribe on your favorite podcast app and submit your feedback.
Follow @techleadjournal on LinkedIn, Twitter, and Instagram.
Pledge your support by becoming a patron.
For more info about the episode (including quotes and transcript), visit techleadjournal.dev/episodes/66.
