My workspace

A few years ago in one of my blog post , i described how to use Oracle database changed notification to update HazelCast cache in application server layer. For now this is one of the finest use case of using Oracle database changed notification, but you can also use this possibilities for solving others problem such as event processing in legacy table. For instance, you are developing dispute system for any Banking system. For banking core system, dispute is as a another banking transaction, when any dispute comes from any client, operator of bank should react on this transaction. Most of the time disputes keeps in same storage (tables) along with another transactions. Such type of tables can keeps billions of rows, and when you would like to get notified when a few of the rows changes, you have a few options in your hand: 1) Poll periodically, schedular which will poll the whole table periodically to get changed data. 2) Using oracle trigger to send some notification (stored procedu

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

UP1: If you are planning to migrate to Microservice, we recommend you to read the book "High performance in-memory computing with Apache Ignite". One of the challenging thing in Microservices world is not the implementation of the services, rather it's monitoring and the management. In the time of writing the blog, we have a few frameworks and tools to implements microservices such as Dropwizard , Spring boot and vertx . Complexity grows when you have a lot of independent micro services deployed and running over cloud infrastructure. It really a pain full task to monitor and manage all the services through 24*7. However Ansible, puppet, docker and logstash tools can help you to build such a management platform for micro services but they are not always sufficient. To solve the above described problem Jboss project release such a management tool for micro services named fabric8 . Fabric8 provides following possibilities such as management, continuous delivery and simple