Balancing Innovation and Integrity in Bluemix

IBM has let their actions speak for their current areas of focus, as recent steps taken in the world of cloud, analytics, and application development have evidenced. This emphasis on promoting a resource intensive atmosphere has brought us Bluemix, helping to power hybrid cloud applications and solutions for commercial purposes, IoT, and analytics. Upon the recent announcement to jointly create the Open Container Platform (OCP), a coalition promoting the interoperability of containers in hopes to foster the rapid growth of container-based solutions, we see Big Blue’s vast network come alive to support such defined initiatives of driving innovation in cloud, mobility, security, and analytics.

As points out in an interview with Mohamed Abdula, VP of Strategy & Offering Management for Cloud Foundation Services at IBM, service scalability, openness in both architecture and general conception, and the utility of hybrid all drive Bluemix, set the foundations for the Bluemix appeal to developers at all levels.

  1. Services. "Bluemix is very much a rich and leading edge platform with the highest number of services to build from — data, mobile, integration, etc."

  2. An open philosophy and architecture. "Everything that they're going to build takes advantage of that whole philosophy and architecture that we built around open"

  3. A hybrid approach. Whether customers need their applications to run on public cloud, private cloud, on-premises infrastructure or some combination thereof, Sogeti knows the applications they build will run on that deployment. "Leveraging things like containers and OpenStack mean they can do it on a public implementation or a dedicated instance or local," Abdula says.

"Our strategy around cloud is to make all of these clouds behave as one," says Angel Diaz, vice president of Cloud Architecture & Technology at IBM. "No application, no solution is an island. Everything is connected."

This interconnectedness is consciously met with precaution, however. As Diaz puts it, one of the biggest challenges with containers currently is that they can contain vulnerable code. Since the basic idea is to allow developers to use containers to build micro-services that can then be strung together to rapidly build new services, it’s vital to accurately identify if something in a container hasn't been patched or has known vulnerabilities before those containers come to serve as the foundations of broadly applicable services.

Integrating with awareness is key, in a world increasingly cyber-dependent, threats are detrimental to not only commerce, but the integrity of institutions and establishments which our activities are based around. So development, and the speed at which we are able to innovate is often maintains some dependence on the security and integrity on the foundations of this innovation.

The point at hand is that the promotion of development oriented and innovative solutions cannot be isolated. IBM sets an applaudable example in this specific case, noting that innovative ecosystems cannot be decoupled from security, even more important in an interconnected environment. How these environments will be protected, secure, and maintain their integrity.will be paramount to the legitimacy of astoundingly exciting innovation.