News for hackers. Stuff that matters.
Re:Event Sourcing (2017) by m45t3r on Thursday January 02, 2020 @08:12AM (#21935061)
For this specific case, nothing, however let's say you need to know when the user got a specific scope and from who. You probably can answer this question in SQL if you prepared your database to do it (i.e: a changeset table), however in an event sourcing architecture you would gain this information for free.

However, just because you're using event sourcing doesn't mean you don't have a database with the current state of your entities.

Re:Event Sourcing (2017) by dgregd on Thursday January 02, 2020 @11:15AM (#21936598)
In Ruby on Rails one can add just one line of code to achieve the same result.

  class User < ActiveRecord::Base
    has_paper_trail
  end
That solution is good enough for most use cases and doesn't require highly skilled architects and developers to implement Event Sourcing properly.