The European edition of Cloud Foundry Summit is just around the corner.
Next week, an ITQ delegation will visit Basel Switzerland for the conference about the fastest-growing cloud native platform.
At VMworld US a couple of guys in suits and Sam Ramji VMware, Pivotal, and Google introduced Pivotal Container Service. Exciting stuff! But what does it mean?
As a consultant on the Cloud Foundry platform I regularly get asked if CF can host .NET applications. The answer is yes. However, it depends on the application how much we as platform engineering have to do to make it possible.
Netflix is a pioneer in microservices land, and had to develop tools to run microservices efficiently as none existed at the time. They were largely open-sourced as Netflix OSS tools, and include components such as:
These days I’m working at a client creating workflows for their state of the art private cloud platform. It’s really quite nice: internal clients can use a webportal to request machines, which are then customized with Puppet runs and workflows to install additional software and perform custom tasks like registering the machine in a CMDB.
What do you base your selection on when buying some piece of technology? Is it the core functionality, or the added features?
As Kit Colbert aptly stated in his VMworld DevOps program Keynote, customers at this point implicitly assume the core functionality of almost any given product will be alright, and base their choices on the extras:
