Just because some people can fuck up a good thing doesn't mean it isn't a good thing.
XML is simple. The problem was (and is) misapplication in areas it doesn't belong.
I'm sure that will happen with no-sql. No biggie.
XML is simple. The problem was (and is) misapplication in areas it doesn't belong.
I'm sure that will happen with no-sql. No biggie.
Instead, kernel-based virtualization such as BSD Jails, Linux-VServer or OpenVZ is the right approach. This type of virtualization comes without any performance penalties! And by using hard links, you can avoid wasting disk space, too.
The benefits are better hardware abstraction, i.e. easier movement to other machines, improved backup possibilities, etc. In fact, the BSD manual recommends the usage of jails for years, if not decades.
I'd say that this kind of virtualization is still underused, while inappropriate kinds of virtualization start to become overused. Maybe this is due to "successful" marketing of VMware. They promote the right techniques, but the wrong technology.
Because you can host the VMWare instance on a SAN and not lose it when the machine dies, which allows cheaper machines.
Complete machine failover is easier.
Sadly, pointy-haired bosses have started putting developers on VMs which is exactly the opposite use case: all people loading their machines at roughly the same time (e.g. I've heard people claim that in Java 1/3rd of time is spent compiling. If you have more then 3 devs....). A fail.