The idea behind this video is that it could have been a conversation at the water cooler between developers. But we might look into more coding in the future.
The idea behind this video is that it could have been a conversation at the water cooler between developers. But we might look into more coding in the future.
I think thinking about a strategy on how to deal with wrong data in the events themselves before choosing the ES route is mandatory otherwise is a no go for me as a beginner, I don't want to wake up facing a problem like that hehe
It would be good to see an code examples during the discussion
The idea behind this video is that it could have been a conversation at the water cooler between developers. But we might look into more coding in the future.
Nice one. In fact, I'm in a very similar project right now. It was good to hear that we are not doing everything wrong here. ;)
great but in the future i hope to see practical example with live code
The idea behind this video is that it could have been a conversation at the water cooler between developers. But we might look into more coding in the future.
@@phpannotated thanks for great efforts 🌹
great discussion, I actually purchased the course but haven't tried it in a real project yet.
great talk
could you please mention which package to handle multi-tenancy system according Seb's said ?
Good talk
❤🌱
I think thinking about a strategy on how to deal with wrong data in the events themselves before choosing the ES route is mandatory otherwise is a no go for me as a beginner, I don't want to wake up facing a problem like that hehe
In big picture, event sourcing is heavily business based decision.
Definitely!