and this has AALLLLLWAYS been my beef with the CQRS/ES community. these promises have been made for years and years and it's disingenuous.
-
-
Prikaži ovu nitHvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
Let me fix that tweet for you. “All XXX rescue projects were based on XXX that promised 1,2,3 and after doing it wrong, no surprise that it all went to shit”. Replace XXX and the list of promises to anything you want.
-
It wasn’t teams doing it wrong, FYI
- Još 11 drugih odgovora
Novi razgovor -
-
-
btw I am going to ask what should be a blatantly obvious question ... One of your "false promises" is "no lost data". How in the actual #$%^ do you "lose data" that is written into an event log without explicitly doing it?
-
The R side of CQRS/ES, if that’s durable, it’s quite easy to screw that up. Users see inconsistent data
- Još 7 drugih odgovora
Novi razgovor -
-
-
Is this satire? I work on an ES system today and I can comfortably say it meets all those goals.
-
no lol i've seen it at least a dozen times
- Još 3 druga odgovora
Novi razgovor -
-
-
Let me correct this for you. 1. Requires more scale and complexity. 2. More touch points where data loss can occur. 3. Often less transactional guarantees that confuse end users and developers. 4. Much more complicated data flow. 5. Much longer development timelines.
-
Now hey that won’t sell anything
Kraj razgovora
Novi razgovor -
-
-
This sounds like people should get better at saying no to projects. 95% of people that ask (me) get told “your system is not a for this”. But for those 5%, nothing else will do.
-
s/a/a good fit/, obviously
- Još 9 drugih odgovora
Novi razgovor -
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.