2 ms·
Not sure some of these precepts are possible: > A.2 Everything should be CQRS. Some things require strong consistency, even at the UI level. Eventual consiste
by naasking 7y ago
Not sure some of these precepts are possible:
> A.2 Everything should be CQRS.
Some things require strong consistency, even at the UI level. Eventual consistency is probably the right default though. Unfortunately, we still don't have good abstractions at the language level to manage this.
> A.4 A subscriber shouldn't affect a publisher.
Literally impossible. Either a subscriber is polling the publisher, or the subscriber registers with the publisher to receive updates. Either way, the subscriber is inducing state transitions in the publisher. What other possible meaning can be assigned to "affect" in order to make this precept valid?
> D.1 Academia has many genuinely smart and interesting ideas, but always remember that pursuing them whole-heartedly will never result in a useful product.
Yeah, not at all sure that's correct. Lots of academic research is funded by commercial interests. In fact, currently one of the biggest corporations in the world at this time (Google) started as academic research.
> D.2 Those people (academics) wasted a lot of time finding the right answer, but now that they've done it, you must exploit it.
Spent a lot of time. "Wasted" implies there was a better way.
> D.5 Practice tells you that things are good or bad; theory tells you why. Never use theory to design a good system from scratch; only practice can tell whether the system is good.
I don't think this is coherent. If theory tells you why a system is bad, then that immediately entails what a good system should look like.
What I think typically happens, is that a system designed by theory is so good at solving the problems it was designed for, that it's then applied to similar-but-not-quite-the-same-problems, and thus it becomes inadequate again.
- AnimalMuppet 7y agoA.4: I think you're a bit too literal here. A subscriber shouldn't affect the publisher other than by subscribing, and by the tiny bit of time it takes to be called. Why those two exceptions? Because those two exceptions are mandatory in the publish/subscribe model. You can't escape them and do publish/subscribe. But the claim is, a subscriber shouldn't do anything beyond that, and that is actually a useful and important claim. A subscriber shouldn't send data back to the publisher via the return value of a subscribed message, still less via reference parameters. A subscriber shouldn't affect the publisher's performance by taking too long to handle one of the messages. There may be other ways as well. D.5: There's a difference between theory and practice. If the system is good in theory but bad in practice, then theory will not tell you so. Only practice can tell you. You can, based on that practice, create an improved theory. That theory will tell you what a good system should look like... in theory. In practice, such a system may still be bad, just in a different way from the previous system. Again, you need practice to tell you this, not theory.