|
|
|
|
To comply with GDPR rules, we need your explicit consent.
Please take a moment to
select the TNS Update newsletter & re-confirm your subscription.
Thank you!
Of course, if you prefer to stop receiving the newsletter, you can easily do so via the unsubscribe link at the bottom of this email.
|
|
|
“Traditional infrastructure providers, such as Cisco, VMware, HPE, Dell and Nutanix, have always sold infrastructure solutions to IT departments. They never dealt with the application layer and lack the intellectual property and experience.”
|
|
|
|
Self interest and guilt are the main reasons companies invest in open source. Without a clear connection to self-interest, an ongoing challenge is justifying investments of time and money to open source projects. A recent survey by DigitalOcean found that only a quarter of respondents’ companies donated more than a thousand dollars a year to open source, and just 18 percent are members of an open source software foundation. Even members of an open source software foundation are not in it as an act of charity. Almost half of this group said one reason their company participates is to better promote their solutions to the community’s developers. Another survey by The Linux Foundation found that almost half of hiring managers involved with open source say their company’s investment was made to support recruitment efforts.
If you dig into the actual money being spent, a lot is going to conferences and training as opposed to paying developers a wage to work on non-company related projects. Instead of looking for a budget line item for “open source,” a better metric is how much time is spent is spent on open source development. Fifty-five percent of developers are contributing to open source, according to the aforementioned DigitalOcean survey, but only 34 percent say their company gives them time to contribute to projects not related to work. Of this privileged group, 53 percent are allowed 1-5 hours a week on non-work open source software developments.
|
|
|
Shannon Williams described Rancher’s course of action on the recent Kubernetes vulnerability — and how with the help of the community, Rancher plugged the Kubernetes security holes — during a podcast hosted by Alex Williams, founder and editor-in-chief of The New Stack, at KubeCon + CloudNativeCon North America 2018.
|
|
Kubernetes 4Eva
One of the ongoing issues of multiple companies collaborating on some open source software is the danger that one or multiple software vendors will hijack the code at some crucial juncture that would force the user to keep using their particular implementation. Competing vendor implementations bedeviled the ease of use for Fibre Channel two decades ago, and, more recently, OpenStack. Now Kubernetes developers Lucas Käldström and Luc Perkins are working to ensure this doesn’t happen with K8s.
This pair of programmers has standardized the way that Kubernetes deploys the clusters it will use to run its workloads, called kubeadm. If an administrator were to do this by hand, the work would involve a lot of permission-setting and creation of certificates. There are a number of packages, such as Cops or Rancher, that ease such roll-outs. Kubeadm doesn’t compete with such an offering. In the best Unix style, kubeadm was scoped very narrowly to do one thing and one thing only: cluster deployments and upgrades. The admin will still have to do external tasks, such as setting up the overlay network. But kubeadm could be used by the maintainers of Kops to ease their own stack management.
Käldström also hoped the work would thwart any possible fragmentation across Kubernetes distributors, who would otherwise work up their own deployment schemes, which could be incompatible with each other. "We don't want this situation in 10 years where you have three different camps, and you can't switch between them," he said. "We are really trying to making things generic as possible at this layer, and keep it open for everyone."
|
|
|
We’ve used SQL for database querying for decades, but streaming data needs a new language. This is why InfluxData released a new declarative query language just for streaming data. Called Flux, the language allows you to do much more complicated analytics, data modification, and ETL tasks in addition to standard querying.
|
|
|
Developed and open sourced by Lyft, Envoy is a service mesh substrate that provides common utilities such as service discovery, load balancing, circuit breaking, logging and tracing to heterogeneous application architectures. It can be used as a service proxy to route requests between services or as an edge proxy to handle external traffic. It’s the third project to graduate from the Cloud Native Computing Foundation incubator after Kubernetes and Prometheus.
|
|
|
Behavior-driven design (BDD) uses simple syntax — Given, When, Then — to explain processes to both IT and business, which then becomes testable specifications. Find out here how BDD can help in your software development.
|
|
Experts and visionaries in distributed systems believe serverless technologies are the next evolution of application infrastructure beyond microservices. Leading edge companies have already embraced serverless and have dramatically reduced operational overhead and streamlined the DevOps cycle, while increasing scalability and resiliency. Still, there are many challenges to serverless adoption, such as operational control, complexity and monitoring.
The New Stack’s Guide to Serverless Technologies will help practitioners and business managers place these pros and cons into perspective by providing original research, context and insight around this quickly evolving technology.
|
|
|
We are grateful for the support of our ebook sponsors:
 |
|
|
|
|
|
|
|
|
