GundersenM

10 ms·

1. 1.▲
   by GundersenM 10y ago

   Yup, agree, this is the problem of having a legacy monolith RDBMS that needs to be rewritten and split apart. It's tempting to throw every new fancy technology at the problem when that is suddenly an option, but it's better to foc
2. 2.▲
   by GundersenM 10y ago

   Sorry, replied too quickly. My point is that if things are so bad that they warrant a major rewrite, then they are probably so bad that there is no simple way to map the existing data into events or starting conditions. It might be true if
3. 3.▲
   by GundersenM 10y ago

   Sure, if the existing DB is simple, that is straight forward, but remember that likely this is a monolith that is so bad that even management have agreed that it needs to be rewritten. Likely there are lots of DB tables with foreign keys an
4. 4.▲
   by GundersenM 10y ago

   Having been part of a project to rewrite a monolith e-commerce site into an event-sourced, domain driven, CQRS system, let me tell you in which situation that is not possible: when you already have data. Remember that in a DDD, ES, CQRS sy
5. 5.▲
   by GundersenM 10y ago

   I wrote about using a bloom filter and HTTP2 push for loading modules (instead of bundling them), and implemented a PoC using service workers: https://mariusgundersen.net/module-pusher/
6. 6.▲
   by GundersenM 10y ago

   I recently wrote about this, and how it can be solved using HTTP/2 and Service Workers: https://mariusgundersen.net/module-pusher/
7. 7.▲
   by GundersenM 11y ago

   No support for a 24 hour clock?