Our public virtual server offering now comes in four distinct virtual server families: balanced, balanced local storage, compute, and memory. With this enhancement, IBM continues its effort to provide you with a first-class public cloud experience by taking the guesswork out of provisioning the right instance flavor for your workload needs.
We’re making it that much easier for you to provision a public virtual server by bundling core and RAM (and storage in the case of Balanced Local Storage) together into predefined flavors. You can choose the flavor that best addresses your specific needs while also realizing new cost savings through reduced pricing.
In addition to these four families, we have several more public virtual server families on the horizon that will meet your requirements as they change.
What does this mean for you?
Our ordering experience has gotten that much easier
You will realize new cost savings when ordering a public virtual server
You can better match your specific need to one of our public virtual server flavors
For clients seeking a specific configuration not found in our flavor selections, try dedicated virtual servers (they allow custom configurations)
Although our public virtual servers have changed, everything else you’ve come to know and love about IBM Cloud will remain the same—and will continue to be available in our vast global footprint.
Working in conjunction with SAP, IBM Cloud is proud to announce the global availability of new 4-socket and 8-socket bare metal servers that are fully SAP S/4HANA and NetWeaver certified and powered by the latest Intel® Xeon® E7-8890 V4 processors.
We're excited to announce three new compute capabilities available in Bluemix that work together to give IBM Cloud clients faster virtual server provisioning, greater virtual server placement control, and greater ease-of-use.
Control and cloud have not necessarily been considered mutually exclusive – this has been a fundamental pain in building applications with granular control according to our clients
"I want full control over workload placement like I have on-premises but I also want the scale of cloud."
Conversations like workload co-location and anti-colocation come into play, where workloads require placement on the same or different underlying physical hardware.
Think about an analytics solution that is being developed. There is not just one instance of the analytics application, there are two or three. Each of which require being developed on different physical hardware requiring fine grain placement control, so in the case of one failure, the other two applications remain unaffected.