Clearly, the Google Pivotal announcement was very much aimed at that future developer, the container development, you know, I'm one of the cool kids, right, who's doing micro-services as scale-out.
There is this breaking the habit of we know what we need to do, or we think we know what we need to do, versus let me show you what we need to do because we are boldly going where other companies have gone before and it is a well-trodden path as you scale out an organization, as you grow globally and as you think about how you collaborate and communicate and things become much more complex.
Note that as you scale out though, the benefits of cloud decrease and it becomes an expensive solution.
Instead, Google is probably mostly interested in establishing Kubernetes as the standard container manager in both OpenStack and on its own platform so that businesses can move their workloads between their on-premise OpenStack clouds and use Google's public cloud to scale out as necessary.
I mean, today most business applications, most Web sites, have not been built in a way that makes them easy to scale out as needs increase, and there's a set of services that a platform, an application platform and development tools, can provide to make that much simpler.
The company claims it also means IT can scale out performance as easily as they scale their compute and memory, without any need to change applications or storage infrastructure.
Also, there is no limit on the amount of scaling that can done and one can horizontally scale out the system as much as needed.
Rapid elasticity: Resources can be quickly provisioned and released to allow consumers to scale out and in as required.
This study did not elaborate on the methodology of storage and querying of the events into the archival repository with regards to forensic purposes and how the archival repository would scale out as additional SIEMs were added to the system.
