Copy
This month, AWS released an open source distribution of the Elastic search software, a move that raised a lot of eyebrows in the communityView in browser »
The New Stack Update

ISSUE 159: Don’t Call It a Fork

Talk Talk Talk

“There are two kinds of open source projects: ones that are growing and ones that are dying. There is nothing in between.”

___
Evan Kaplan, InfluxData CEO, InfluxDays NYC.
Add It Up
How centralized is you enterprize's decision-making?
IT departments continue their endless quest to gain control over enterprise technology decision making. IT spending decisions are extremely centralized at 56 percent of organizations, especially as it pertains to infrastructure and operations. In contrast, only 9 percent of respondents say application development is extremely centralized, according to a survey of 202 IT leaders I conducted with the Argyle Executive Forum. Although technology decisions appear to be devolving towards business units, IT executives’ plans are to actually bring more capabilities within their organization.
What's Happening

“We are coming to all those communities and basically pitching them to move, right? We tell them, ‘look, monolithic is very complicated — let’s move to microservices,’ so, they are working very, very hard to move but then they discover that the tooling is not that mature,” Idit Levine, founder and CEO of Solo.io, said. “And actually, there are many gaps in the tooling that they had or used it before and now they’re losing this functionality. For instance, like logging or like debugging microservices is a big problem and so on.”

Levine, whose company offers service mesh solutions, also described how service meshes were designed to “solve exactly this problem,” during a podcast episode of The New Stack Analyst hosted by Alex Williams, founder and editor-in-chief of The New Stack, with Janakiram MSV, a TNS Correspondent and principal of Janakiram & Associates.

How Service Meshes Are a Missing Link for Microservices

Don’t Call It a Fork

Earlier this month, Amazon Web Services released an open source distribution of the (mostly) open source Elastic search software, a move that raised a lot of eyebrows in the open source community. The moved was necessary, AWS’ Adrian Cockcroft argued in a blog post, in that Elastic has intermingled proprietary code with the open source code that makes up the core of Elastic. He writes that with Elastic:

Neither release notes nor documentation make it clear what is open source and what is proprietary. Enterprise developers may inadvertently apply a fix or enhancement to the proprietary source code. This is hard to track and govern, could lead to breach of license, and could lead to immediate termination of rights (for both proprietary free and paid). Individual code commits also increasingly contain both open source and proprietary code, making it very difficult for developers who want to only work on open source to contribute and participate.

In particular, AWS releases open source components of Elastic providing functionalities that were previously only handled by Elastic’s proprietary code, namely security, event monitoring and alerting.

AWS made a similar move last year with the Java OpenJDK, releasing its own version called Correto, that offered long-term support beyond Oracle’s own. Nonetheless, many people took issue with this approach, charging that AWS might put Elastic out of business, unintentionally or otherwise. Developer advocate Sharone Zitzman argued in The New Stack that AWS, by starting its own Elastic distro, was engaging in “cynical and hostile corporate behavior,” namely that of hijacking an open source project and community for its own benefit, leaving little to the maintainers of the project. 

Zitzman argued that unlike other tech giants — IBM, Google, Microsoft — that have shown a commitment to devoting engineering hours to help maintain open source projects they are using, AWS has shown less regard for the well-being of the open source technologies that it has hijacked for its own commercial offerings (MongoDB also comes to mind here).

What do you think — was AWS acting unfair, or is Elastic moving too slow to anticipate the emerging cloud marketplace of ideas?  

5 Questions Database Admins Should Ask About Compliance Regulations

In this contributed piece from IT management software giant Quest, John Pocknell, senior solutions product marketing manager, says that database administrators need to think about how to have their data meet compliance requirements such as HIPAA, PCI or the dreaded GDPR. In other words, to ensure the data they are responsible for is properly managed, secure, and not sensitive to threat vectors, in light of evolving compliance requirements. Techniques include identifying where the sensitive data is, and establishing someone in charge of making sure data is compliant.

Grafana Now Offers Flux as a Native Query Language

As part of a sweeping set of upgrades for version 6.0, the open source Grafana analytics visualization software now supports the Flux query language for time-series data, initially as a plugin, but soon as the default query language for the InfluxDB time-series database.

Develop a Forward-Thinking Interface to Streamline the User Experience

In this contributed piece, Toby Coleridge, vice president of product at HiveIO, discusses how to build a usable user interface for data center administrators and ops folks. The company is drawing lessons from its recently updated hyperconverged software package (HiveIO 7.2) which included a fresh user interface with more visualizations, and the usual rows of menus being replaced with a more intuitive reactive approach.

Party On

Seen at last week's OSLS in Half Moon Bay: The Red Hat team of Jen Krieger (left) and Leslie Hawthorne on combatting the fatigue that comes with change. Who can’t relate to that, right?

InfluxData CEO Evan Kaplan believes instrumentation (and monitoring) are growing more and more important as complex systems evolve towards self-autonomy.

Influxdata’s Tim Hall, seen here at InfluxDays NYC, is excited for the upcoming release of time-series database service InfluxCloud 2.0.

Grafana’s Jacob Lisi waxed poetic about the expanded query capabilities that the Flux language provides at InfluxDays NYC.

On The Road
Cloud Foundry Summit North America // APRIL 04, 2019 // PHILADELPHIA, PA @ PENNSYLVANIA CONVENTION CENTER

APRIL 04 // PHILADELPHIA, PA @ PENNSYLVANIA CONVENTION CENTER

Cloud Foundry Summit North America
Come join The New Stack for a short stack in historic Philadelphia! Digital transformation is not about adopting a single new technology — it’s about adapting to a world that’s now ordered around technology. To build for the future, your organization must develop new systems for constant learning and the ability to turn on a dime. A huge part of this is designing an interoperable IT strategy in which your chosen technologies work in tandem as part of a multi-platform strategy. Your organization’s success will be measured by the ability to master this new state of change — now and in the future. Thank you Cloud Foundry and Pivotal for making this breakfast possible. Add it to your schedule now! 
The New Stack Makers podcast is available on:
SoundCloudFireside.fm — Pocket CastsStitcher — Apple PodcastsOvercastSpotifyTuneIn

Technologists building and managing new stack architectures join us for short conversations at conferences out on the tech conference circuit. These are the people defining how applications are developed and managed at scale.
Free Guide to Cloud Native DevOps Ebook

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. 

Download The Ebook
We are grateful for the support of our ebook sponsors:





Copyright © 2019 The New Stack, All rights reserved.


Want to change how you receive these emails?
You can update your preferences or unsubscribe from this list