My workspace

UP1: If you are planning to use Reactive programming, we recommend you to read the book "High performance in-memory computing with Apache Ignite". Nowadays, term Reactive programming and Reactive manifesto is became trend. Blog post, articles and presentations are all over. Why peoples getting crazy with it? or what's the problem it could solve? The easiest way to answer the above questions is to think about the requirements we have building application these days. We have to: 1) Modular - Module can help to maintain the application, it can be go offline and getting back to online without breaking all the system down; 2) Scalable - this way we can scale vertically or horizontally to handle a large amount of data or transactions; 3) Resilient - system can be getting back online and be fault tolerant; 4) Responsive - this means fast and available. Here is the paradigm of reactive manifesto: For most of the part, we already have a few framework such as Akka, Vert.x...