|
|
|
|
“Maybe containers were a mistake.”
|
|
|
Salesforce is buying Tableau and Google Cloud is adding Looker to its family. After reviewing a panoply of studies about business intelligence (BI), analytics, and data warehousing, we found it evident that both acquisitions will provide best-in-class functionality addressing the needs of both business analysts and the IT department, as well as leadership in high-growth markets that are only tangentially related to artificial intelligence and machine learning.
Twenty-eight percent of IT professionals believe that over the next five years more sophisticated data integration capabilities will be the focus in business intelligence and analytics software development, according to SharesPost’s October 2018 survey. This was a dramatic rise from only 10% that said so in the 2017 survey. Expectations also increased about the attention that will be paid to data visualization capabilities. The notable losers are machine learning integration and predictive analytics. This does not mean that ML and predictive analytics use has dropped — the same study found that the use of predictive analytics in BI tools rose from 41% to 67% over the same time period. Instead, developers may believe that the predictive power of new technologies will be less important than actually managing and visually exploring the data that is being analyzed.
|
|
|
Containers have only recently started to go mainstream as an important part of continuous integration and continuous delivery (CI/CD). This is great for developer autonomy and individual ownership, but what about security? While Docker and Kubernetes have been the main drivers of this rapid container adoption, the ease at which these two orchestrators allow anyone to deploy code can leave security in peril. Does the fact that these are open source platforms make it even more or less secure?
Most importantly, how much do users understand about container security?
This is some of what The New Stack founder Alex Williams was asking when he sat down at DockerCon with Tianon Gravi, senior vice president of operations at InfoSiftr, and Noah Abrahams, Kubernetes engineer at Ticketmaster.
|
|
Many New Stacks
This week, we are debuting our new landing pages for The New Stack website. To date, we have offered a simple home page with all the stories we have, updated as we post new stories. But despite the ongoing popularity of Dev(Sec)Ops, the TNS stories that developers want to read may be different from those security admins want to read, and different again from what the operations team may find of interest.
So we have come up with individual “landing pages,” or topic-specific home pages for all the different technologies we cover. We bucketed them into three categories: architecture, development, and operations, which you will see as a banner stretching across the home page. Under these categories, we have individual sites for all your favorite technologies, including microservices, containers, networking, data, cloud services, and monitoring.
On each page, you will find all of our stories and podcasts that under that topic, as well as a brief introduction of what the topic is pertinent to cloud native professionals. Over time, we will add additional resources to the page, such as our ebooks or third-party resources. Bookmark your favorite topic, and tell us what you think!
|
|
|
A few months ago, RackN CEO Rob Hirschfeld free-form surveyed Twitter about Kubernetes clusters. He was wondering if Kubernetes was emerging as a wholesale replacement for virtualization platforms or simply growing as an application framework. If the former, then he’d expect to see operators using the platform as a large scale, multitenant system. But if the latter, he’d see developers using the platform as a single application, life cycle management system. Of nearly 30 responses, over half suggested smaller application specific clusters were the popular choice. In general, answers reflected on the desire for the separation, isolation and control provided by small clusters. Read the results here.
|
|
|
When IBM set out to build its IBM Kubernetes Service (IKS) a couple of years back, it ended up building its own continuous delivery tool, now open sourced as Razee. It operates differently than other CD systems, in that it is pull-based, rather than push, and therefore provides self-updating Kubernetes clusters. This is done by inserting an agent into each cluster that can check back for rule updates and then update as needed using Kubectl and the Kubernetes API.
|
|
|
Currently, at release candidate 3, the Linux 5.2 kernel is coming soon and promises to offer quite a host of impressive new features and improvements. Highlights include a generic counter interface, a NULL TTY driver, and support for Intel’s new line of mobile processors, Intel Comet Lake.
|
|
|
|
Toasting Kubernetes at the K8s “Boothday” Party during KubeCon and CloudNativeCon in Barcelona (left to right) Atsuo Suzuki of NEC Solution Innovators, Ltd and Yoshiya Eto of Fujitsu.
|
|
|
Google’s Gobind Johar (left) and Bowei Du were enjoying themselves at the attendee party at KubeCon + CloudNativeCon in Barcelona.
|
|
|
|
GitLab's Sarah Voegeli was seen in this awesome T-shirt recently.
|
|
|
|
The New Stack Makers podcast is available on:
|
|
Cloud native technologies — containers, microservices and serverless functions that run in multicloud environments and are managed through automated CI/CD pipelines — are built on DevOps principles. You cannot have one without the other. However, the interdepencies between DevOps culture and practices and cloud native software architectures are not always clearly defined.
This ebook helps practitioners, architects and business managers identify these emerging patterns and implement them within an organization. It informs organizational thinking around cloud native architectures by providing original research, context and insight around the evolution of DevOps as a profession, as a culture, and as an ecosystem of supporting tools and services.
|
|
|
|
|
|
|
|
|
|
