I’d say a solution will be highly dependent of what exactly you need to do. A solution to write thousands of records per second might be very different from incrementing a counter in the example you provided. More so, there could be no tables at all to handle such load. Consistency/availability requirements are also missing … Read more
To answer your specific question I will speak more generally about your architecture. The architecture you’ve devised for your project is subtly different from a typical architecture used with DDD. While the way you’ve partitioned responsibilities is typical, in DDD, domain classes aren’t responsible for their own persistence. In fact a mantra of DDD is … Read more
This is a very interesting question. I also would like to know how other developers do this. Up until now I use these possibilities in no particular order: Read the source code, it has the advantage that it is always up to date. It is also the most difficult task, but it is possible. Read … Read more
You make some points. But I nevertheless use a Dao layer, here’s why: Database accesses are calls to a remote system. In all such cases (also web-service, ajax etc…), the granularity of interaction need to be big enough. Many tiny calls would kill performance. This performance necessity requires often a different view of the system, … Read more
each microservice need its own database A separate DB per microservice is not a prerequisite (nor a requirement, really). You can have as many microservices as you want working on top of the same database, but use different schemas for example. The bounded context of a microservice should be the boundary. Lets say we have … Read more
The first point is to decide what “breaking change” means in English*. In some places it would be merely something which stops the code from compiling / running. From your list so far, I suppose you mean a change that will require other people to make a corresponding change. In that case, since each module … Read more
As programmers, we like to believe we are smart people, so it’s hard to admit that something is too big and complex to even think about all at once. But for a large-scale software project it’s true, and the sooner you acknowledge your finite brain capacity and start coming up with ways to simplify the … Read more
I have worked with both ZeroMQ and Redis with python. I would say ZeroMQ is more robust, it offers real simple load balancing and also more than pub-sub, like request reply among others. But if you are only after pub-sub, redis is much simpler. In case the redis server crashes or stops working, all the … Read more
Rules. You create events in the system, and use rules within an event stream processor. Specifically, say you have a badge “made 10 posts”. You don’t run “select count(*) from posts where user = :user” for every post. Rather, you have a simple rule that watches each post come by, and “count them”, storing the … Read more
I didn’t read the article, so I can only speculate what he can mean exactly, but as he gives ESB as an example against microservices and ZeroMQ as an example for micro services I hope my speculation will be pretty exact: One of the ideas of Unix (and Linux) is to build small independent applications … Read more