Many companies are adopting a ‘virtualization first’ policy due to all the benefits associated with virtualization. But, there is still legitimate concern about virtualizing everything, especially with security and performance for high I/O driven applications. The hyperadvisor, Antone Heyward addresses these concerns and best practices for virtualizing these applications.
As you probably saw by now, JetBrains just announced that they are working on a brand new statically typed JVM language called Kotlin. I am planning to write a post to evaluate how Kotlin compares to the other existing languages, but first, I’d like to take a slightly different angle and try to answer a question I have already seen asked several times: what’s the point?
We already have quite a few JVM languages, do we need any more?
Here are a few reasons that come to mind.
I've had some interesting discussions with other developers about writing code recently. I often have the impression that some developers put too much emphasis on clean code. Don't get me wrong, i strive for clean code as well, and have written about its importance quite a lot in the past couple of years. But when i'm coding, clean code is my secondary goal and it could never take the place of my primary goal: making it work. And preferably, i want to make it work great.
The past few months have been a jam-packed with a few developments in terms of C++. Not only did C++0x get the almost unanimous nod of the industry to be good enough to be called C++11 but there’s also a few stories that have come out that need some attention too. With a new version coming up I’d say this decade is the one where C++ is more relevant than ever.
Git has become the programming world's most popular version control system--at least that's what surveys conducted by Microsoft Corp. suggest. While there are abundant write-ups already available for new users and administrators, from tutorials to descriptions of clever merge workflows, I still often encounter a few missteps in basic version control naming and layout.
Java is known for security purpose widely.As Java 7 has come so it is obvious that some security features will be there.Ya its right.Java community add lots of major and better security algorithms in Java 7.They added Elliptic Curve Cryptography that is so much secure other side they deprecated MD2 digest algorithm.Here i am listing some security features those are implemented in java 7.
LMAX, a trading company in the UK, recently open sourced one of their core components: the Disruptor. This component allows reduces execution overhead by removing the necessity for locks, while still keeping processing order guarantees. A pretty ingenious piece of engineering, if you ask me. I tried to apply the disruptor to the Axon Command Bus, just to see what it potential is. The results are pretty astonishing.