My workspace

One of my few blog posts i have mentioned how to use and the use cases of using Oracle DataBase changed notification. When you have to need context search or count facts over your datas, you certainly need any modern Lucene based search engine. Elastic search is one of that search engine that can provide those above functionalities. However, from the previous versions of ES, elastic search river is deprecated to ingesting data to ES. Here you can get the whole history about deprecating river in ES. Any way, for now we have two option to ingest or import data from any sources to ES: 1) Implements or modify your DAO services, that can update data in ES and DataBase same time. 2) Polling, implements such a job, which will polling data in some period of time to update data in ES. First approach is the very best option to implements, however if you have any legacy DAO services or 3rd party application that you couldn't make any changes is not for you. Polling to data base frequentl...

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...

Last couple of months, most of the conferences and seminar discussing and debuting about the new architecture design named microservice. From the first glance micro service means, developing independent small service which will be high cohesive in functionality and could be changed rapidly. Some of the IT evangelist already starts debating, why micro service is a buzzword. From my point of view word microservice misleading itself. Design model under this concept is as follows: 1. Service should be loosely coupled. 2. High cohesion in functionality. 3. Service should be change with minimal effect on other services. 4. Automated in deployments. 5. Scaling out easily. 6. Can be use polyglot programming language and polyglot persistence store. Most of these requirements are nothing new at all. Developers or IT Architect who already familiar with SOA already know all these above concept very well. From my point of view, we have to clear following three things to giving start coding o...

Yesterday i visited Saint Petersburg university after a long period of time as a speaker. Conference held already a weeks and students came here from all over the country and out side of Russia. Audiences was very nice and ask a lot of technical question mostly about Cassandra and we are utilising it in our projects. Community was very curious about NoSQL and wanted find all the answer of their questions about the new trend. Here is the presentation from slide share net. NoSQL - World IT Planet, Saint Petersburg 2015 from Shamim bhuiyan

UP1: If you are interested in in-memory computing for getting High Performance from your system, we recommended you the book " High performance in-memory computing with Apache Ignite ". Today i have provide new presentation for tuning and optimising high load j2EE web application based on developing sberbank portal. Presentation is available here in slide share. Tuning HighLoad J2EE web application from Shamim bhuiyan