There are a number of articles on whether synchronized or Locks are faster. There appear to be opinions in favour of either option. In this article I attempt to show how you can achieve different views depending on how you benchmark the two approaches.
This article explores deserialisation with and without recycling objects. How it not only is slower to create objects, but it slows down the rest of your program by pushing data out of your CPU caches.
I always had the idea of having some kind of organized store, some kind of very simple knowledge base where I could memorize interesting stuff around software development which I encounter i my day-to-day business.
In our own project we have used JMS not to communicate between two disparate systems but to get the asynchronous capability integrated to our application. What we do is push the message into a queue and get along with the rest of the business process. But it seems that this is not the correct way of achieving this.
It’s neither particularly newsworthy nor insightful to suggest that ‘Big Data’ gets everywhere these days, but two recent items reminded me of the gulf between credible execution of a big data play and the more questionable tacking of the big data meme onto an otherwise useful product.