7 ms·

Fun to implement, sucky to maintain! Like event-sourcing.

• pyrale 7y ago
  Why would event sourcing be sucky to maintain? My last job was to build a system to replace something that used to require lots of maintenance. Event sourcing made most of this maintenance trivial, and the remaining cases were made easier to explain and handle. Event sourcing things doesn't mean you need to use a complex frp framework, a simple pg table and a state machine in your language of choice is usually enough.
  • Dude2029 7y ago
    In this case the maintainer is the builder, that is always comfortable.
    • pyrale 7y ago
      I have recently moved to another team, so we shall see. However, we also administered two crud dbs, one we inherited and another recent one. The three dbs were doing pretty much the same thing. Understanding and maintaining what happened in the crud db we built was significantly harder than understanding and maintaining the event-sourced one.
• jhayward 7y ago
  > Fun to implement, sucky to maintain! Like event-sourcing. This comment begs for a blog post or some links that illuminate what you mean.