Based on Apache OpenWhisk, IBM Cloud Functions is a Functions as a Service (FaaS) platform that makes it easy to build and deploy serverless applications. In this tutorial, you'll build a serverless application using IBM Cloud Functions that monitors the content of a Cloud Object Storage bucket and analyzes the content of images that are uploaded to the bucket by a human or an automated process. For illustrative purposes, analysis is performed by a deep learning microservice from the Model Asset eXchange and analysis results are stored as JSON files in the same bucket. You can easily adapt the outlined approach to take advantage of hosted cognitive services, such as those provided by IBM Watson, and to store results in a NoSQL datastore like Cloudant or a relational database. By completing this introductory tutorial, you learn how to monitor a Cloud Object Storage bucket for changes (new objects, updated objects, or deleted objects) using Cloud Functions and how to use deep learning microservices from the Model Asset eXchange to automatically analyze those objects in near real time.
It seems not a week goes these days by without another leak or breach of sensitive government data, from a contractor setting the wrong access permissions on a storage directory to a data center compromise to a rogue employee walking out the door with an agency's crown jewels. At the same time, concerns are being raised about the government's increasing centralization of computing services into the commercial cloud, with the US military most recently following the intelligence community to Amazon's classified cloud. Instead of creating new risks, perhaps the government's move into the commercial cloud could finally help it secure its sprawling digital empire and stop the growing flood of leaks and breaches. In today's cybersecurity landscape it is an unfortune fact of life that no matter how hard an organization works to secure its most sensitive data, some of it will inevitably walk out the door. The US Government faces an especially difficult task securing its digital secrets against the resources of the world's most sophisticated cyber adversaries.
Istio, an effort to manage micro-services across various systems in the cloud, has reached its 1.0 release courtesy of IBM, Google Cloud, Red Hat and others. You can download all of the articles in this special report in one PDF (free registration required). IBM launched Istio along with Google Cloud and Lyft a little more than a year ago. The goal of Istio is to give developers a vendor-neutral way to connect, secure and manage networks of various microservices. Managing microservices is a critical issue since enterprises are increasingly built on them.
According to a recent O'Reilly radar survey on the growth of cloud computing, one of the more interesting metrics stated that 52 percent of the 1,283 responses say they use microservices concepts, tools, or methods for software development. Of these, a large minority (more than 28 percent) have used microservices for more than three years. This was the second-largest cluster among users of microservices. The largest group, at more than 55 percent, has been using microservices between one and three years. Moreover, just 17 percent of users are new to microservices, with less than one year of adoption and use.
For all the numbers showing explosive growth of the public cloud, there remains a stubborn segment of the market where policies and regulations prohibit the moving of data into any kind of public cloud. The choices for private cloud have been one of two ends of the spectrum: build your own Open Stack implementation or opt for vendor solutions like Microsoft Azure Stack, Oracle Cloud at Customer, and IBM Cloud Private. The do it yourself side has been only for the adventurous, for the IT organizations that built their own compute grids a decade ago. Emergence of container technology, and with it, the enabling of microservices has fueled the fire. The value propositions are that containers are much lighter weight, and therefore, more nimble than VMs, and with containers, you get the construct that is tailor made for microservices.