home.social

#event-sourcing — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #event-sourcing, aggregated by home.social.

fetched live
  1. Which user groups/meetups should I speak at in November that are near/in Berlin/Potsdam? (About #Java and #EventSourcing and #DomainDrivenDesign)

    Would be before or after Agile Testing Days. Check jittertravel.com/calendar for where I’ll be and when.

  2. Which user groups/meetups should I speak at in November that are near/in Berlin/Potsdam? (About #Java and #EventSourcing and #DomainDrivenDesign)

    Would be before or after Agile Testing Days. Check jittertravel.com/calendar for where I’ll be and when.

  3. Which user groups/meetups should I speak at in November that are near/in Berlin/Potsdam? (About #Java and #EventSourcing and #DomainDrivenDesign)

    Would be before or after Agile Testing Days. Check jittertravel.com/calendar for where I’ll be and when.

  4. Which user groups/meetups should I speak at in November that are near/in Berlin/Potsdam? (About #Java and #EventSourcing and #DomainDrivenDesign)

    Would be before or after Agile Testing Days. Check jittertravel.com/calendar for where I’ll be and when.

  5. Which user groups/meetups should I speak at in November that are near/in Berlin/Potsdam? (About #Java and #EventSourcing and #DomainDrivenDesign)

    Would be before or after Agile Testing Days. Check jittertravel.com/calendar for where I’ll be and when.

  6. Reminder that tonight I'll be talking at EuregJUG in Aachen (Germany) about #EventSourcing in #Java. Come join us!

    Details: euregjug.dev/#events

  7. Reminder that tonight I'll be talking at EuregJUG in Aachen (Germany) about #EventSourcing in #Java. Come join us!

    Details: euregjug.dev/#events

  8. Reminder that tonight I'll be talking at EuregJUG in Aachen (Germany) about #EventSourcing in #Java. Come join us!

    Details: euregjug.dev/#events

  9. Reminder that tonight I'll be talking at EuregJUG in Aachen (Germany) about #EventSourcing in #Java. Come join us!

    Details: euregjug.dev/#events

  10. Reminder that tonight I'll be talking at EuregJUG in Aachen (Germany) about #EventSourcing in #Java. Come join us!

    Details: euregjug.dev/#events

  11. Reminder that tonight I'm speaking in Hamburg (at the Microservices Meetup) about #EventSourcing! I know it's short-notice, but if you're around, come on by and let me share with you my passion on the topic! meetup.com/microservices-meetu

  12. Reminder that tonight I'm speaking in Hamburg (at the Microservices Meetup) about #EventSourcing! I know it's short-notice, but if you're around, come on by and let me share with you my passion on the topic! meetup.com/microservices-meetu

  13. Reminder that tonight I'm speaking in Hamburg (at the Microservices Meetup) about #EventSourcing! I know it's short-notice, but if you're around, come on by and let me share with you my passion on the topic! meetup.com/microservices-meetu

  14. Reminder that tonight I'm speaking in Hamburg (at the Microservices Meetup) about #EventSourcing! I know it's short-notice, but if you're around, come on by and let me share with you my passion on the topic! meetup.com/microservices-meetu

  15. Reminder that tonight I'm speaking in Hamburg (at the Microservices Meetup) about #EventSourcing! I know it's short-notice, but if you're around, come on by and let me share with you my passion on the topic! meetup.com/microservices-meetu

  16. Me and #EventSourcing a year ago

    [edit: added that this turned into an obsession for me about a year ago]

  17. Me and #EventSourcing a year ago

    [edit: added that this turned into an obsession for me about a year ago]

  18. Me and #EventSourcing a year ago

    [edit: added that this turned into an obsession for me about a year ago]

  19. Me and #EventSourcing a year ago

    [edit: added that this turned into an obsession for me about a year ago]

  20. Me and #EventSourcing a year ago

    [edit: added that this turned into an obsession for me about a year ago]

  21. Hey folks, guess what? I'm speaking on Thursday (3 Sept) in Hamburg (at the Microservices Meetup) about #EventSourcing! I know it's short-notice, but if you're around, come on by and let me share with you my passion on the topic. meetup.com/microservices-meetu

  22. Hey folks, guess what? I'm speaking on Thursday (3 Sept) in Hamburg (at the Microservices Meetup) about #EventSourcing! I know it's short-notice, but if you're around, come on by and let me share with you my passion on the topic. meetup.com/microservices-meetu

  23. Hey folks, guess what? I'm speaking on Thursday (3 Sept) in Hamburg (at the Microservices Meetup) about #EventSourcing! I know it's short-notice, but if you're around, come on by and let me share with you my passion on the topic. meetup.com/microservices-meetu

  24. Hey folks, guess what? I'm speaking on Thursday (3 Sept) in Hamburg (at the Microservices Meetup) about #EventSourcing! I know it's short-notice, but if you're around, come on by and let me share with you my passion on the topic. meetup.com/microservices-meetu

  25. Hey folks, guess what? I'm speaking on Thursday (3 Sept) in Hamburg (at the Microservices Meetup) about #EventSourcing! I know it's short-notice, but if you're around, come on by and let me share with you my passion on the topic. meetup.com/microservices-meetu

  26. Tested an idea I had for teaching aspects of #EventSourcing by having folks role-play as different components (read model, processor) and I think it worked! Thanks to my SoCraTes Germany guinea pigs for participating, I hope it helped you understand things better.

  27. Tested an idea I had for teaching aspects of #EventSourcing by having folks role-play as different components (read model, processor) and I think it worked! Thanks to my SoCraTes Germany guinea pigs for participating, I hope it helped you understand things better.

  28. Tested an idea I had for teaching aspects of #EventSourcing by having folks role-play as different components (read model, processor) and I think it worked! Thanks to my SoCraTes Germany guinea pigs for participating, I hope it helped you understand things better.

  29. Tested an idea I had for teaching aspects of #EventSourcing by having folks role-play as different components (read model, processor) and I think it worked! Thanks to my SoCraTes Germany guinea pigs for participating, I hope it helped you understand things better.

  30. Tested an idea I had for teaching aspects of #EventSourcing by having folks role-play as different components (read model, processor) and I think it worked! Thanks to my SoCraTes Germany guinea pigs for participating, I hope it helped you understand things better.

  31. My book club is reading Designing Data-Intensive Applications (by Chris Riccomini and @martin) and today we went over the bulk of Chapter 13 and all I can say is WOW!

    Dataflow-oriented systems, of which #eventsourcing is very much in line with those ideas, give up a bit in "timeliness" (aka consistency lag, aka eventual consistency), but give you solid integrity and can help sidestep coordination, making distributed systems easier to reason about and perform better than overcomplicated transactions and consensus systems.

    I can't wait to add some of the insights from this chapter into my Ted Talk on Event Sourcing.

  32. My book club is reading Designing Data-Intensive Applications (by Chris Riccomini and @martin) and today we went over the bulk of Chapter 13 and all I can say is WOW!

    Dataflow-oriented systems, of which #eventsourcing is very much in line with those ideas, give up a bit in "timeliness" (aka consistency lag, aka eventual consistency), but give you solid integrity and can help sidestep coordination, making distributed systems easier to reason about and perform better than overcomplicated transactions and consensus systems.

    I can't wait to add some of the insights from this chapter into my Ted Talk on Event Sourcing.

  33. My book club is reading Designing Data-Intensive Applications (by Chris Riccomini and @martin) and today we went over the bulk of Chapter 13 and all I can say is WOW!

    Dataflow-oriented systems, of which #eventsourcing is very much in line with those ideas, give up a bit in "timeliness" (aka consistency lag, aka eventual consistency), but give you solid integrity and can help sidestep coordination, making distributed systems easier to reason about and perform better than overcomplicated transactions and consensus systems.

    I can't wait to add some of the insights from this chapter into my Ted Talk on Event Sourcing.

  34. My book club is reading Designing Data-Intensive Applications (by Chris Riccomini and @martin) and today we went over the bulk of Chapter 13 and all I can say is WOW!

    Dataflow-oriented systems, of which #eventsourcing is very much in line with those ideas, give up a bit in "timeliness" (aka consistency lag, aka eventual consistency), but give you solid integrity and can help sidestep coordination, making distributed systems easier to reason about and perform better than overcomplicated transactions and consensus systems.

    I can't wait to add some of the insights from this chapter into my Ted Talk on Event Sourcing.

  35. My book club is reading Designing Data-Intensive Applications (by Chris Riccomini and @martin) and today we went over the bulk of Chapter 13 and all I can say is WOW!

    Dataflow-oriented systems, of which #eventsourcing is very much in line with those ideas, give up a bit in "timeliness" (aka consistency lag, aka eventual consistency), but give you solid integrity and can help sidestep coordination, making distributed systems easier to reason about and perform better than overcomplicated transactions and consensus systems.

    I can't wait to add some of the insights from this chapter into my Ted Talk on Event Sourcing.

  36. I wrote a small blog post about the new release of patchlevel/event-sourcing-phpstan-extension, 1.3.0 adds three new rules.

    They report aggregate properties that no event ever fills, state that nothing ever reads, and state that changes outside an apply method.

    Also, every rule can be turned off individually.

    Feel free to check it out!

    patchlevel.dev/blog/what-is-ne

    #TechBlog #PHP #DDD #EventSourcing #PHPStan #StaticAnalysis

  37. I wrote a small blog post about the new release of patchlevel/event-sourcing-phpstan-extension, 1.3.0 adds three new rules.

    They report aggregate properties that no event ever fills, state that nothing ever reads, and state that changes outside an apply method.

    Also, every rule can be turned off individually.

    Feel free to check it out!

    patchlevel.dev/blog/what-is-ne

    #TechBlog #PHP #DDD #EventSourcing #PHPStan #StaticAnalysis

  38. I wrote a small blog post about the new release of patchlevel/event-sourcing-phpstan-extension, 1.3.0 adds three new rules.

    They report aggregate properties that no event ever fills, state that nothing ever reads, and state that changes outside an apply method.

    Also, every rule can be turned off individually.

    Feel free to check it out!

    patchlevel.dev/blog/what-is-ne

    #TechBlog #PHP #DDD #EventSourcing #PHPStan #StaticAnalysis

  39. In this #InfoQ podcast, Johannes Schickling explains why he moved beyond the traditional three-tier web stack to a local-first architecture while building Overtone.

    Learn how client-side event sourcing with SQLite compares to CRDTs, and the trade-offs architects should consider.

    🎧 Listen now (transcript included) 👉 bit.ly/4pIHM6N

    #LocalFirst #SQLite #EventSourcing #SoftwareArchitecture

  40. In this #InfoQ podcast, Johannes Schickling explains why he moved beyond the traditional three-tier web stack to a local-first architecture while building Overtone.

    Learn how client-side event sourcing with SQLite compares to CRDTs, and the trade-offs architects should consider.

    🎧 Listen now (transcript included) 👉 bit.ly/4pIHM6N

    #LocalFirst #SQLite #EventSourcing #SoftwareArchitecture

  41. In this #InfoQ podcast, Johannes Schickling explains why he moved beyond the traditional three-tier web stack to a local-first architecture while building Overtone.

    Learn how client-side event sourcing with SQLite compares to CRDTs, and the trade-offs architects should consider.

    🎧 Listen now (transcript included) 👉 bit.ly/4pIHM6N

    #LocalFirst #SQLite #EventSourcing #SoftwareArchitecture

  42. In this #InfoQ podcast, Johannes Schickling explains why he moved beyond the traditional three-tier web stack to a local-first architecture while building Overtone.

    Learn how client-side event sourcing with SQLite compares to CRDTs, and the trade-offs architects should consider.

    🎧 Listen now (transcript included) 👉 bit.ly/4pIHM6N

    #LocalFirst #SQLite #EventSourcing #SoftwareArchitecture

  43. In this podcast, Johannes Schickling explains why he moved beyond the traditional three-tier web stack to a local-first architecture while building Overtone.

    Learn how client-side event sourcing with SQLite compares to CRDTs, and the trade-offs architects should consider.

    🎧 Listen now (transcript included) 👉 bit.ly/4pIHM6N

  44. CQRS, async with retries and dead-lettering, event sourcing, projections, workflows. That feature list usually means a platform team.

    I built it as an e-commerce shop on Tempest + Ecotone. The entire messaging layer: about a dozen small classes of business logic. No worker command, no repository, no queue wiring.

    The Order aggregate IS the Tempest database model. One class, both frameworks.

    github.com/ecotoneframework/te

    #PHP #CQRS #EventSourcing

  45. CQRS, async with retries and dead-lettering, event sourcing, projections, workflows. That feature list usually means a platform team.

    I built it as an e-commerce shop on Tempest + Ecotone. The entire messaging layer: about a dozen small classes of business logic. No worker command, no repository, no queue wiring.

    The Order aggregate IS the Tempest database model. One class, both frameworks.

    github.com/ecotoneframework/te

    #PHP #CQRS #EventSourcing

  46. CQRS, async with retries and dead-lettering, event sourcing, projections, workflows. That feature list usually means a platform team.

    I built it as an e-commerce shop on Tempest + Ecotone. The entire messaging layer: about a dozen small classes of business logic. No worker command, no repository, no queue wiring.

    The Order aggregate IS the Tempest database model. One class, both frameworks.

    github.com/ecotoneframework/te

    #PHP #CQRS #EventSourcing

  47. CQRS, async with retries and dead-lettering, event sourcing, projections, workflows. That feature list usually means a platform team.

    I built it as an e-commerce shop on Tempest + Ecotone. The entire messaging layer: about a dozen small classes of business logic. No worker command, no repository, no queue wiring.

    The Order aggregate IS the Tempest database model. One class, both frameworks.

    github.com/ecotoneframework/te

    #PHP #CQRS #EventSourcing

  48. CQRS, async with retries and dead-lettering, event sourcing, projections, workflows. That feature list usually means a platform team.

    I built it as an e-commerce shop on Tempest + Ecotone. The entire messaging layer: about a dozen small classes of business logic. No worker command, no repository, no queue wiring.

    The Order aggregate IS the Tempest database model. One class, both frameworks.

    github.com/ecotoneframework/te

    #PHP #CQRS #EventSourcing

  49. Requirements change, but your events are immutable and your history lives forever. So how do you evolve them without breaking anything?

    I just published the second and final part of my two-part series on event design: "Evolving Your Events Over Time." It walks through the whole toolbox of event evolution, from a free rename to rebuilding the whole store.

    Feel free to check it out!

    patchlevel.dev/blog/evolving-y

    #TechBlog #PHP #DDD #EventSourcing #EventDesign

  50. Requirements change, but your events are immutable and your history lives forever. So how do you evolve them without breaking anything?

    I just published the second and final part of my two-part series on event design: "Evolving Your Events Over Time." It walks through the whole toolbox of event evolution, from a free rename to rebuilding the whole store.

    Feel free to check it out!

    patchlevel.dev/blog/evolving-y

    #TechBlog #PHP #DDD #EventSourcing #EventDesign

  51. Requirements change, but your events are immutable and your history lives forever. So how do you evolve them without breaking anything?

    I just published the second and final part of my two-part series on event design: "Evolving Your Events Over Time." It walks through the whole toolbox of event evolution, from a free rename to rebuilding the whole store.

    Feel free to check it out!

    patchlevel.dev/blog/evolving-y

    #TechBlog #PHP #DDD #EventSourcing #EventDesign

  52. Requirements change, but your events are immutable and your history lives forever. So how do you evolve them without breaking anything?

    I just published the second and final part of my two-part series on event design: "Evolving Your Events Over Time." It walks through the whole toolbox of event evolution, from a free rename to rebuilding the whole store.

    Feel free to check it out!

    patchlevel.dev/blog/evolving-y

    #TechBlog #PHP #DDD #EventSourcing #EventDesign

  53. Requirements change, but your events are immutable and your history lives forever. So how do you evolve them without breaking anything?

    I just published the second and final part of my two-part series on event design: "Evolving Your Events Over Time." It walks through the whole toolbox of event evolution, from a free rename to rebuilding the whole store.

    Feel free to check it out!

    patchlevel.dev/blog/evolving-y

    #TechBlog #PHP #DDD #EventSourcing #EventDesign