Xceedium Xsuite® controls access, monitors, and records the activities of privileged users across the hybrid cloud. You can easily define, apply, and enforce security policies to sensitive systems across traditional data centers, virtualized infrastructure, and public and private clouds. Xsuite manages passwords and protects servers regardless of where they’re located, helping to reduce risk, ensure…
The arms race to make it easy for one cloud vendor to onboard workloads from another vendor has been started by GoGrid and Racemi. This will likely lead to a world where it is easy to move workloads around between private clouds and public clouds of various types. If this happens then we are headed towards a world where execution environments for applications will compete on a limited set of dimensions like application response time, required throughput, cost, and required security level. If and when this occurs, then in fact IT will have become “a service”.
One sure way to improve performance is to cache the non-dynamic data of any application. We did this to improve the overall performance of The Virtualization Practice website. However, there are many places within the stack to improve overall performance by caching, and this got me to thinking of all the different types. At the last Austin VMUG, there were at least three vendors selling caching solutions that were designed to improve overall performance by as little as 2x to upwards of 50x improvements. That is quite a lot of improvement in application performance. Where do all these caching products fit into the stack?
• • 3 Comments
The next evolution of virtualization is the Software Defined Data Center or SDDC and it is quickly becoming the next logical step in the continued evolution of cloud technology that will give you the ability to run legacy enterprise applications as well as the other cloud services. In my opinion you could also define Software Defined Data Center as a converged datacenter so to speak. My friend and colleague, Edward Haletky wrote a great post on SDDC and data protection, which raised this question. How the heck to we recover SDDC?
One aspect of SDDC that does not get a lot of attention is Data Protection, instead we are concentrating on SDN and automation. Yet, this leads me to Data Protection. There is a clear marriage between Data Protection and SDDC that needs to be added to any architecture. As with all things, we start with the architecture. Our SDDC architecture should also include data protection, but what data are we really protecting? Within SDDC there are three forms of data: tenant, configuration, and automation. Without one or the other, we may not be able to reload our SDDC during a disaster. What is required to get these three types of data, what really are these types of data? and how can we add data protection into SDDC cleanly?