Photo by LindaInpijn
Several years ago I worked on a WebDAV project. At the time we complained about the format (did you there are multiple date formats in use) and thought we could have done better. But, WebDAV works on Windows, Mac, Linux, iOS, and Android, just to name a few. It's widely supported and works across different ecosystems. Standards like WebDAV seem like a thing of the past and that may not be a good thing.
Helm 2.0.0, the package manager for Kubernetes, was just released. This is definitely a major milestone release.
A couple months ago we held a survey of Go package management needs, likes, dislikes, and so forth. From this survey we collected lots of great information with some confirmations and some surprises.
Since the survey closed data and roll-ups from the survey have been sent to the package management committee which has now released a draft spec for a new tool.
The results of the survey were promised to be publicly shared. You can read the results in Google Docs.
In the Kubernetes documentation for accessing a cluster there is a step to install kubectl, the CLI for working with clusters. This step assumes you've download a pre-compiled release of Kubernetes and then points you at a subdirectory to find kubectl for your operating system and architecture.
But, do you really want to download 1 GB and all of Kubernetes just to get the CLI for accessing a cluster?
For those with lots of data, and I'm talking about petabytes, the location of data is a major factor cloud location decisions. This is when data gravity become an issue.
Data Gravity, explained on technopedia:
Data is something that continues to accumulate over time, and could be considered to become more dense, or have a greater mass. As density or mass accumulates, the data's gravitational pull increases. Services and applications have their own mass and; therefore, have their own gravity. But data is much bigger and denser than the two. So, as data continues to build mass, services and applications are more likely to be drawn to the data, rather than vice versa. This much like an apple falling to earth, which if often provided as a typical example of gravity. Because the earth has more mass, the apple falls to the earth, rather than the other way around.
Paying to host petabytes of data in a cloud provider can be expensive. There's a point where it's more cost effective to host it on premise using something like Ceph.
Moving data out of cloud providers is also expensive and time consuming when dealing with petabytes of it.
This can create a form of lock-in to a platform.
Dealing with enterprises, some of whom have large amounts of data to go along with the amount of compute capacity they need, has made me consider where private clouds can potentially be useful.
Whether a startup or an enterprise it's useful to be aware of the impact of data gravity.
