The New Stack Makers is all about the developers, software engineers and operations people who build at-scale architectures that change the way we develop and deploy software.For The New Stack Analysts podcast, please see https://soundcloud.com/thenewstackanalystsFor The New Stack @ Scale podcast, please see https://soundcloud.com/thenewstackatscaleFor The New Stack Context podcast, please see https://soundcloud.com/thenewstackcontextSubcribe to TNS on YouTube at: https://www.youtube.com/c/TheNewStack
One of the bright points to emerge in Kubernetes management is how the core capabilities of the Istio service mesh can help make engineering teams more efficient in running multicluster applications. In this edition of The New Stack Makers podcast, we spoke with Dan Berg, distinguished engineer, IBM Cloud Kubernetes Services and Istio, and Neeraj Poddar, co-founder and chief architect, Aspen Mesh, F5 Networks. They discussed Istio’s wide reach for Kubernetes management and what we can look out for in the future. Alex Williams, founder and publisher of The New Stack, hosted this episode.
In this The New Stack Makers podcast, technology thought leaders from Dell EMC and VMware discuss the dynamics of data protection and other DevOps-related themes for today’s highly complex cloud native environments.
It sounds pretty basic, but getting your infrastructure ready for modern apps, and centrally managing your clouds and cluster requires a modernized app platform.
And that’s exactly what we explored with Dell Technologies in our series of five recordings scheduled to start tomorrow. Dell Technologies and VMware are making continued investment in the cloud native market. It’s perhaps most apparent with the acquisition of companies such as Heptio, Wavefront, Bitnami, and most recently Pivotal. It’s now transformed into initiatives using Dell Technologies’ and VMware’s Tanzu solution portfolio. VMware Tanzu is built upon the company’s infrastructure products and technologies that Pivotal, Heptio, Bitnami, Wavefront, and other VMware teams bring to this new portfolio of products and services.
In this The New Stack Makers podcast, we discuss the infrastructure requirements for organizations making the shift to modern-day application development, deployment and management — and how Dell Technologies’ expertise can help to make that possible. Our guests are Bob Ganley, cloud senior consultant, product marketing for Dell Technologies and Dormain Drewitz, director, product marketing and content strategy, at VMware.
Before tasking DevOps with technology adoption to take advantage of the immense opportunities application development can offer with the right mix of tools, platforms and usually cloud environments, it is essential to both determine what users really want. Once that is established, making sure that the infrastructure can support the adoption of the technologies to deliver is also essential.
In this edition of The New Stack Makers podcast hosted by Alex Williams, founder and publisher of The New Stack, Wang spoke about these and other third-party security trends. The podcast was recorded in anticipation of the The State of Cloud Native Security virtual summit to take place on June 24.
Major exploits such as the Target and Equifax hacks made headlines a few years ago. But these infamous attacks have not necessarily served as a wakeup call for many, if not most, organizations. They lack the security tools, processes and culture required to properly protect their data, Chenxi Wang, Ph.D., managing general partner, Rain Capital, said.
“Everybody read about those headlines but translating that into the work [organizations] do day to day, I think there’s still a gap,” Wang said. “As security industry professionals — myself included — we need to reach out more to the adjacent community and especially with Dev these days. I mean software is eating the world and Dev is the one driving software, so we need to work with dev to make it happen.”
In this episode of The New Stack Makers, our Publisher Alex Williams sits down with Raj Dutt, CEO and co-founder Grafana Labs, provider of the open source observability platform Grafana. They’re talking about creating a more seamless transition among observability, tracing, metrics and logs, across different data types and open source projects.
Observability and distributed tracing are intrinsically linked to reliability of increasingly distributed systems. Observability-driven development uses data and tooling to observe the state and behavior of a system to learn more about its patterns for weaknesses. Distributed tracing provides the metrics and logs that allow for diving into individual requests and to get closer to the problem. In this powerful pairing, observability happens at the event level, which drives your questions, and tracing happens at the request level, which helps answer them.
In this edition of The New Stack Makers podcast hosted by Alex Williams, founder, and editor-in-chief of The New Stack, Keith Mokris, head of product marketing, Prisma Cloud, Palo Alto Networks, and Mark Rauchwarter, cloud and infrastructure security for Accenture Security, discuss the key talking points of the Prisma Cloud Native Security Summit and what the results of the survey mean for the DevOps community.
Join Prisma Cloud by Palo Alto Networks June 24 at 9:00 AM PDT at The State of Cloud Native Security virtual summit for a full discussion of the “The State of Cloud Native Security” report and other topics relevant to your organization’s digital journey. The summit will feature a panel session hosted by The New Stack’s Founder and Editor-in-Chief Alex Williams, with security thought leaders from AWS, Accenture, and Prisma Cloud by Palo Alto Networks.
Bloomberg’s involvement as a financial information leader with the OpenAPI Initiative and the open source community is built on wider aspirations than it is about choosing the right tools to grow its business. The stakes are especially high in these turbulent times as the ravages of COVID-19 continue to take its toll, already wiping out large swaths of the economy .
In this The New Stack Makers podcast, we speak with two open source leaders from Bloomberg:
Richard Norton, head of the data license engineering group.
Kevin Fleming, head of open source community engagement and member of Bloomber’s CTO office.
Bloomberg’s collaboration and backing of OpenAPI as well, its involvement with open source and what this means for the financial sector are discussed.
From the outset, APIs are seen as a core underpinning of what Bloomberg offers with, of course, its famous Bloomberg terminals. The data and analytics Bloomberg provides its financial institution and other customers — which might include data feeds for futures or commodities — allows for key decisions to be made, often affecting world capital markets.
There’s no doubt we are in weird times. There are a lot of stressors, but the majority of the tech community has more opportunities than ever to do what we do working from home. Just last week Google and Twitter announced that employees can work from home for the rest of the year or even indefinitely. For The New Stack Publisher Alex Williams, there’s one resounding reason why — the internet is awesome. And what’s driving much of that awesomeness right now is no doubt Kubernetes and its highly distributed community.
In this episode of The New Stack Makers, Williams sits down, over Zoom, with two grounded frequent fliers — Diane Mueller, director of community development at Red Hat and co-chair of OKD, Red Hat’s distribution of Kubernetes, and Paris Pittman, developer relations program manager at Google and a leader in CNCF’s Kubernetes contributor strategy. They spoke fresh off of running a particularly successful, inclusive — and very big — Red Hat Summit.
“Now, because it’s virtual, there’s no reason for them not to participate. And so we saw like this phenomenal exponential growth of people coming and participating at Red Hat,” Mueller said.
The hype around Kubernetes has created many repercussions in the IT industry — while not all of the effects have been net positive for many organizations and DevOps teams. Infrastructure management is a prime example. Missing too often are security management tools for Kubernetes deployments and infrastructure management. Ultimately, these tools should have the capacity to replace security and IT skills gaps and talent shortages by automating vulnerability detections and fixes, for example.
“Kubernetes is something powerful and impactful, but has too many components and moving pieces,” Moe Abdula, vice president of engineering, SaltStack, said. “How do you ensure that you can build an architecture and a system around something like a Kubernetes that is easy to maintain, easy to support, easy to extend?”
In this The New Stack Makers podcast, we speak with Abdula and Gareth Greenaway, vice president of engineering, SaltStack, about how and why the infrastructure- and security-management aspects of Kubernetes, as well as infrastructure, have been neglected, what the risks are and what can be done to fix it.
Rare is the DevOps team that has the bandwidth to manually parse through and prioritize what needs to be fixed among what can number millions of application-error alerts. This includes distinguishing between minor glitches and those errors that can bring to a screeching halt an organization’s capacity to meet its customers’ needs and expectations.
A viable error-monitoring system should, ideally, automate the communication of error data in a way that indicates what must be done to make a fix.
A system might be able to signal every single error, perhaps totaling millions of alerts.
The error alerts users receive must be “actionable,” Ben Vinegar, vice president of engineering, for Sentry, said. “That’s a really hard problem,” Vinegar said.
Twenty years ago, Dries Buytaert founded Drupal right at the dot-com bust. Then in 2008, at the start of the so-called Great Recession, he started Acquia, a digital experience platform for Drupal sites. Some would say those are unlucky times to start businesses. Not Buytaert. He’s convinced well-loved free and open source software or FOSS is recession-proof. And that’s what this episode of The New Stack Makers dives into.
What is remote-first? In normal times, it’s an organization that is built in such a way that anyone can go remote if necessary.
“Whether or not you want to allow your employees to go remote, you should have the processes in place to be able to just-in-case because you see transportation problems loom all over the world, weather problems all over the world, sick children at home. There were all kinds of reasons why a business should be putting remote processes into place,” said Lisette Sutherland on this episode of The New Stack Makers.
For Sutherland, founder of Collaboration Superpowers remote team workshops, longtime remote work podcast host, and author of A Handbook on Working Remotely — Successfully — for Individuals, Teams, and Managers, we’ve been technologically ready for a remote-first world for about five years now. And she says there’s always been logic in factoring a remote-first mindset into your business continuity planning. Plus, giving the option of remote work often makes for a much more inclusive workplace that in turn empowers a business to hire the best candidate no matter where they live.
With remote work, “people can hire people who love what they do, rather than people who are just doing their job,” Sutherland said.
How do we promote diversity and inclusion from the comfort of our homes? How do we recreate those important hallway moments within a virtual environment? How do we continue to consider the consequences of what we’re building? We begin to answer these questions and more in this episode of The New Stack Makers, where we interview Emily Webber, independent agile delivery and digital transformation consultant, coach and trainer, and author of the book Building Successful Communities of Practice.
Webber, like everyone The New Stack is interviewing as of late, was calling in via Zoom from her home office. Usually, she’d be working between her clients’ offices in London and in India. Even for someone who has built part of her brand on remote meet-ups, nothing about this is business as usual.
Webber is based in London, where, in normal times, it’s completely common to see people eating lunch at their desks or even while walking back to work from the takeaway shop. But at her client in India, they all take breaks and share meals together in the canteen. There she’s not only experienced a huge leveling up in terms of cuisine, but she’s witnessed the innovation that comes from those chance encounters around the hallway, cafeteria, and water cooler.
Webber has borrowed Etsy’s John Goulah’s term “assisted serendipity” and applied it to our temporarily remote-first world. This can be using a Slack app like Donut or Shuffl to facilitate random coffee pairings. Or host remote coffees or happy hours. It may be assisted, but it is an efficient way of crossing cross-departmental silos, as well as to fight isolation during these trying times.
In this The New Stack Makers podcast, we speak with Glitch’s CEO Anil Dash and James Turnbull, vice president of engineering, about how Glitch could help developers remove much of the pain associated with installing and accessing application code and how it serves as an extension of GitHub.
Glitch, which was originally called Gomix created under the Fog Creek Software umbrella — along with Stack Overflow and Trello — has served as the platform for over five million apps, according to Dash.
Glitch can potentially take some of the pain out of application development since developers can begin working directly on abstraction layers while “taking away the the kind of boring, repeatable part of being a developer,” Dash said, who estimates about 80% of all code written is identical elsewhere. “Glitch provides people with a platform they can build on top of it without having to worry about installing this dependency or worrying about how this thing works,” Dash said. “That’s the way that a lot of the world has been moving and how the abstraction layer is moving further up the stack.”
For those seeking just to study how certain code and apps work, Glitch can “make it really easy for folks who are like journalists to go: ‘okay, I don’t really understand how this AWS thing works, but I’ve got an example of someone using this Python app to to map all this data together,’” Turnbull said. “I can create a visualization from that. And I think that’s an example of a strong use case framework-wise.”
Ultimately, for the developer, the creative — or for many — the fun part of development work could potentially be more accessible. Applications are “built on top of the scaffold,” Dash said. “I think what we’re seeing here is that we can provide that abstraction layer and we can take away the the kind of boring, repeatable part of being a developer,” Dash said. “We can provide people with a platform that they can take and build on top of it without having to worry about things like ‘I need to install this dependency or I need to worry about how this thing works, or I need to set up this framework or, or this template.'”
Today, we speak with Cheryl Razzell, director of platform and Live Ops, at Polystream who has a particularly interesting narrative to share in what remains nevertheless a renaissance era in computing. Indeed, the assumption we can make is open source tools, platforms and, especially, talent will underpin how data is processed and managed as we win this war against the pandemic.
As the ravages of COVID-19 continue to take their toll in London, where she is based, and worldwide, Razzell speaks of women in tech, and her career path from tech support to working at Apple, Microsoft, HBSC, DevOps and continuing her high-level IT career tech at Polystream, a 3D content platform provider.
As mentioned above, regardless of whatever happens during the next few weeks and months, open-source development and tools will continue to serve as the foundation for what is yet to come. And during what will be a recovery eventually, organizations that thrive in the future will only do so by continuing to operate as software companies. But, this is just the context — lest we forget — that can often obscure how open source development and tools are only as good as the talents of the people constituting the DevOps teams that make the magic happen.
In this, The New Stack Makers podcast, Bill Mulligan, who plays a key role in helping customers to automate their IT operations with Kubernetes and operators for Loodse, discusses his background — taking him from the University of Wisconsin-Madison via the University of Oxford to his life in Berlin today — and the key role Cloud Native plays in supporting telcos and other Loodse customers.
Linus Torvalds first released his Git version control software 15 years ago, on April 7, 2005, in an effort to foster a more creative spirit in Linux kernel development. Since then, Git's role in software development has emerged well beyond its roots as a version control system and a software repository. It's become a cornerstone in how software is developed today by distributed teams and open source developers around the world.
In this The New Stack Makers podcast, we spoke with three Git thought leaders who about Git’s roots, its present context and its future. We learned that despite its present-day success, Git's future is not certain.
Guests on this episode are:
Jason Warner, CTO, GitHub.
Cornelia Davis, CTO, Weaveworks.
Sid Sijbrandij, Co-founder and CEO, GitLab.
For many, the possibilities that Git offers are exciting, both on an individual and macro level when many parties must collaborate on a project, particularly for CI/CD. You can use Git to upload personal pet projects, such whether you want to share a simple code sample or just documentation for something not necessarily related to software. For a large enterprise, developer teams can collaborate on application development concurrently whether they are scattered around the world or separated by only cubicle walls.
In this episode of The New Stack Makers, we talk to Nóva, chief open source advocate at Sysdig, about the progression of the open source world and her perspective examining it through the lens of San Francisco’s COVID-19 lockdown. She calls the book she wrote with Justin Garrison a kind of thesis that looks to predict the infrastructural patterns that could solve a lot of the challenges cloud-native infrastructure teams face.
Listen to more episodes here: https://thenewstack.io/podcasts/
In this episode of The New Stack Makers podcast, Daniel Spoonhower, CTO of Lightstep, discussed and described what the “three pillars” concept means for DevOps, how monitoring is different, Lightstep’s evolution in developing observability solutions and a number of other related themes.
Spoonhower — whose experience in developing observability tools traces back to work as a software engineer at Google — makes it clear that a “three pillar” observability solution consisting of metrics, logs, and distributed tracing represents, in fact, separate capabilities.
“I think the thing that we’ve kind of seen is that thinking of those as three different tools that you can just kind of squish together is not really a great solution. I mean, the way that I think about observability is I like to get away from the what the specific tools are, and just say that observability is the thing that helps you connect the effects that you’re seeing — whether that’s performance or user experience, or whatever, connecting those effects back to the causes,” Spoonhower said. “And the thing that happened with deep systems is that it’s not like there are five or 10 potential causes to those problems, but there are thousands or tens of thousands of those things. And so you need a tool to help you find those.”
Listen to more episodes here: https://thenewstack.io/podcasts/
This episode of The New Stack Makers focuses on more the community and less on the tech side of the tech community — which we think matters now more than ever. Williams has dedicated her career to teaching, mentoring and helping others find the right roles in tech. In fact, she’s written a step-by-step guide on how to get your first job in this industry. This episode dives into how to build the right network
Software Engineer and Developer Advocate Cassidy Williams started this decade looking forward to a year of global travel for React training, workshops, and public speaking gigs. She spent January in Boston, DC, and Austria. February saw her speaking in France and Ireland. Then, suddenly, the small consultancy she worked at went from having overbooked their March to an empty schedule. And the full-time staff was let go.
Listen to All New Stack Podcasts here: https://thenewstack.io/tag/podcast
Kubernetes has emerged as the de-facto option for managing containers, while microservices serve as the underlying distributed architecture of Kubernetes clusters. The continued rise of multi-cloud infrastructures is also seen as a conduit for the continued adoption of microservices for Kubernetes deployments for such widely distributed infrastructures. The need to create applications and manage such diverse infrastructures in this rapidly expanding multi-cloud universe.
But, suddenly, the coronavirus worldwide pandemic has turned the world on its head in ways we have yet to fully realize,
In this, The New Stack Makers podcast, Ankur Singla, founder and CEO at software as a service (SaaS) provider Volterra, discusses the profound influences Kubernetes, microservices, multi-cloud environments, and open source have had on computing and IT today — and what their impacts may be in a Covid-19 world.
"Covid-19 throws a big wrench" into everything, Singla said. "The first thing we realized with lots of our large enterprise customers is that corporate networks are becoming a big bottleneck," Singla said. "And in order to reduce the load, many of the enterprises are already looking at how can they quickly migrate their apps from private data centers to the cloud, because the network to the cloud is a lot better than a network to private networks."
The migration to the cloud also involves a "move to SaaS services," Singla said. "SAS services obviously require scale, and more and more of them are going microservices," Singla said.
It is safe to assume that a particular technology or architecture has become mainstream, after surviving an initial hype cycle and becoming uniformly accepted and reliable. A technology associated with cost savings and demonstrably improved efficiencies is also another criterion used to determine whether a particular technology has acquired mainstream status. One can thus arguably assume microservices are on their to achieving mainstream status. "More and more enterprises are migrating to SaaS services, and SaaS is all about scale — and scaling is a lot easier with microservices," Singla said.
Singla began to see the potential of microservices about five years ago when large enterprises largely had adopted microservices. "But it was becoming very clear to me that that would be an architecture paradigm, and increasingly so with serverless — so, then, the paradigm shift was starting to happen. And we thought that was a great opportunity to start a new company that helped solve many of the problems of going mainstream to multiple cloud providers and being able to build highly distributed edge locations...with the convergence of distributed applications and data," Singla said. "And we said, 'it's a great time to start a company to solve the problem of distributed application data. So, that's the background on Volterra."
Feature image by from Pixabay.
Listen to All TNS podcast here: https://thenewstack.io/podcasts
In this episode of The New Stack Makers podcast, we spoke with IBM’s Lin Sun, whose official title is a senior technical staff member and “master inventor” for a comprehensive overview on what service meshes are for those not completely familiar with the topic, may have some familiarity and want to know more or want to also know more about emerging use cases.
Sun’s expertise in service meshes largely draws upon her role as an Istio project maintainer and is also on the Istio Steering Committee and Technical Oversight Committee.
Sun’s IBM title as “master inventor” may sound unusual or even arguably pretentious for some, or even “really cool,” as Sun describes it. But at IBM, the status as “master inventor” represents specific merits those who hold the title must first attain.
“‘Master inventor’ is a title for someone who demonstrates the mastery of the IBM inventor process and is able to mentor other people to be successful in the invention process, and to be able to be productive yourself,” Sun said. Among the other requirements, a “master inventor” must also first file about a dozen patents and to have at least one issued patent, Sun said. You must also have worked with a ‘review board to reveal any incoming patent disclosures on behalf of IBM
Listen to all of our podcasts here: https://thenewstack.io/podcasts/
There’s a common misconception that the individual consumer’s actions will dramatically affect climate change. That we should recycle more and avoid plastic straws and bottles. These are nice-to-haves, but they don’t make an impact on the systemic contamination of industries like agriculture, travel, and, yes, tech. On the other hand, when scandal strikes tech, we point blame at the top, and we don’t drill down into the individual responsibility. What we found with the Volkswagen emissions scandal is that even the person who writes the code can be culpable.
If we each bear some individual responsibility in the code we release, is there power in the green developer? In this episode of The New Stack Makers, we sit down with Microsoft Green Cloud Advocacy Lead Asim Hussain to talk about what a green developer is. And we try to uncover what does that actually look like for a web developer, a machine learning engineer, a DevOps person, or a department with a huge fleet of Internet of Things fleet devices.
Hussain says to start it’s not about a lack of motivation.
“They care, they want to do something. And one of the questions I get asked a lot is from developers and all kinds of developers working on all different aspects of applications are, What can I do now?”
Hussain said that then they end up only focusing on their own role when they should be looking at things end to end.
He continued that “I used to think full stack meant like a website to a database. And now I understand full stack means like, from user behavior to how electricity is bought and sold on a grid.”
In fact, Hussain predicts a whole new role emerges: sustainable software engineer. Or even better a multi-department team that looks to piece together the full software development lifecycle, from sourcing hardware materials to powering data centers to the deprecation of the tools and devices.
This can start with just ardent, cross-functional green-conscious volunteers who make themselves know in an organization and who try to piece together this lifecycle. That’s how it started with Microsoft, growing into a 2,000-person green team.
Where do you get started? Hussain says to start by examining the carbon efficiency and the carbon intensity of your application. Hussain points to little moves that have a big impact like choosing when to run your workloads, which “depending upon the renewable mix and the energy grid, you can, just by changing when you run a workload, you can reduce the carbon emissions by 48 percent per application.”
And don’t just assume this is for the most modern microservices, he says this can even be more impactful when you are running certain jobs on legacy applications.
Hussain continues to talk about the creation of a green public agreement. He also offers Microsoft’s sustainability calculator which allows you to start to measure because, as we’ve learned with the agile movement, you can’t improve what you can’t measure.
Last week we wrote about how a true DevOps transformation doesn’t just focus on developers and operations but looks to unclog cross-organizational bottlenecks. One of those areas often overlooked — the one with so much of that coveted rapid feedback — is support. In this episode of The New Stack Makers, we talk to Michael Shelton, VP of global customer support at NinjaRMM, about closing the cultural distance to reach support teams to drive the post-customer experience.
When Shelton joined NinjaRMM five years ago, it was still a tiny team working on the then new remote monitoring and management platform. They didn’t have a support team yet — everyone was support. He admitted that back in the day they had a lot of bugs, but they used that to broach stronger customer relationships.
Shelton said they built an ethos that continues today, talking to customers like partners and, sometimes even therapists:
“You’re not wrong. Sounds like you’re having a really tough time. And sounds like we’re part of the cause of that. Let’s work together to figure out what the solution is.”
The NinjaRMM team realized they could use the close relationship between support and the customer to drive the product. What do the customers love? What are they super frustrated about? What are their use cases?
To hear more podcasts listen here: https://thenewstack.io/podcasts/
Prisma, from Palo Alto Networks, sponsored this podcast, following its Cloud Native Security Live, 2020 Virtual Summit held Feb. 11, 2020.
The adoption of “immutable infrastructure” has emerged as a viable way to improve DevOps processes and culture. By introducing more of a standardization in application deployment and management, immutable infrastructure helps, among other things, to foster a better collaborative environment among developers, operations, security team and other stakeholders.
“Immutable infrastructure gives you the ability to have a consistent environment, across your entire fleet of systems, which gives you a simpler and more predictable deployment,” Mike Liedike, manager, Deloitte Consulting’s Innovations and Platforms team, said. “It allows you to do the testing more consistently and promote your environments from development to test to prod.”
In other words, the adoption of immutable infrastructure is often a hallmark of a highly functional DevOps.
In this edition of The New Stack Makers podcast recorded live at Palo Alto Networks’ studio in Santa Clara, CA, Liedike offers further insight and analysis of what the adoption of an immutable infrastructure can mean for your organization.
A good starting point to describe how immutable infrastructure works is by first detailing how it does not work — or more specifically, what “mutable” infrastructure is and how it differs compared to immutable infrastructure. Using the example of Apache servers, Liedike noted how admins might upgrade the servers by installing the latest version of the Web server software with configuration-management tools. The problem, Liedike said, is that “across 1,000 instances, you have a lot of room for error and inconsistency.” “With immutable infrastructure, instead of doing those changes in place, you would actually build a new server, with all the upgrades already in place, and then deploy your systems and decommission the old ones,” Liedike said.
For the full video go here: https://youtu.be/honVx93d9aM
As Nicole Hubbard, a developer advocate for HashiCorp observed, customers constantly face difficulties when trying to secure the communication between their services running inside of a Kubernetes cluster. The dilemma often involves trying to figure out how to lock down communications between the applications inside and outside clusters or with apps between clusters, Hubbard said.
In this edition of The New Stack Makers video recorded live at Palo Alto Networks’ studio in Santa Clara, CA, Hubbard shows how Consul Connect with Envoy can help to securely maintain data communication between different Kubernetes and microservices environments.
Hubbard describes, among other things, Consul Connects features and functions as a “one-on-one level intro to Consul.” The end result is that Consul Connect with Envoy secures communications between Kubernetes clusters, as well as different data sources.
“If you look at the different ways you can run applications, you can run them everywhere between mainframes, your own hardware in your own data centers, virtual machines or even as far as containers and functions that are serverless. But the one thing that’s common between all of these is the network. You have to secure the communication between all the different services, no matter where they’re running,” Hubbard said. “But as you grow and you start to break these out into microservices, you run into the problem of how does ‘a’ talk to ‘b’ and how do I find where ‘b’ is.”
Hubbard described how some bank partners can have as many as 4,000 services “that won’t scale with VLANs or firewall rules, without an extremely high operational overhead.” Hubbard described how within a service mesh, there is a control plane and the data plane, while “the control plane for us is Consul.” “And what Consul is responsible for is defining the roles, defining and tracking what services are available as well as provisioning that information to the data plane so that the data plane knows how to move traffic around,” Hubbard said. “The data plane is basically a pluggable proxy that receives this information from the control plane and uses it to route data correctly to the correct place.”
For more insight from security thought leaders, Cloud Native Security Live, 2020 Virtual Summit is your opportunity to learn from the experience and expertise of developers, DevOps pros and IT leaders who all have so much at stake in container technologies and DevSecOps. Hosted by Prisma, from Palo Alto Networks, in partnership with The New Stack, you can still virtually attend this event held Feb. 11, 2020, for a full day of discussions about cloud native security — brought to you online wherever you may be.
Listen to more Podcasts from The New Stack here : https://thenewstack.io/
Prisma, from Palo Alto Networks, sponsored this podcast, following its Cloud Native Security Live, 2020 Virtual Summit held Feb. 11, 2020.
The concept of DevSecOps is getting a lot of play these days — and for good reason. As organizations’ DevOps seek to boost their rates of deployments and updates at cadences unheard of just a few years ago, the risk of vulnerabilities can often increase at the same rate in theory. While it doesn’t have to be this way, of course, some organizations struggle with remediating vulnerabilities long after the software has been deployed, not only causing major potential headaches when breaches occur (think Equifax), but causing additional pain when developers must reconfigure code again, and in extreme cases, reinvent the wheel.
The solution, of course, is for security teams to become vested in code development at the very beginning of the production cycle. This is what agile DevOps teams are supposed to do anyway, but many organizations have not implemented the necessary culture, tools and processes to do this. After years of existing as a concept, DevSecOps formalizes the often missing security links in development processes today.
In this edition of The New Stack Makers podcast, DevSecOps evolution and why it is so vital today were discussed.
The guests were selected for there first-hand experience and experience with DevSecOps were:
Rohit Gupta, global segment leader, security, for Amazon Web Services (AWS).
Cindy Blake, security advocate, for GitLab.
Shaan Mulchandani, AWS security practice, for Accenture.
The New Stack Publisher Alex Williams hosted this episode.
Read more https://thenewstack.io/
In this episode of The New Stack Makers, we talk to Kris Beevers about the importance of the traffic manager role and so much more as we look ahead to this year in enterprise tech. Seven years ago, Beevers co-founded NS1, the networking automation company or, as he calls it, “the system of record for many, many of the key domains and the applications on the Internet today.”
He says that each of us interacts with NS1 dozens of times a day, like when we are connecting on LinkedIn or sharing files on DropBox.
NS1 sits at the base of this new traffic management stack, steering that traffic across our increasingly complex and distributed systems. This stack also includes content networking delivery networks (CDN), load-balancing tooling, edge networking footprints, Service Mesh, service discovery, and egress optimization. This new role isn’t just about measuring if traffic is working correctly, but really understanding both your users and systems to know how traffic is reaching the application, if you’re using the right networking providers and venders, and if you’re choosing data centers, clouds and CDNs effectively.
This new traffic management role sits at the heart of greater site reliability engineering trends like chaos engineering and progressive delivery. It’s about using your tooling stack to understand how your whole tooling reacts to prepare for the worst.
Read more stories like this here! https://thenewstack.io/
Prisma, from Palo Alto Networks, sponsored this podcast, following its Cloud Native Security Live, 2020 Virtual Summit held Feb. 11, 2020.
Agile development teams may able to meet software release and update cadences at faster and faster rates — but ultimately, their deployments are only as good as the underlying code. Applications that lack robustness or have vulnerabilities that are discovered until only after its too late can defeat the whole purpose of Agile DevOps. The hard truth is that policies and practices must involve testing and monitoring from the outset of code development while extending throughout the entire CI/CD lifecycle.
The main theme of this edition of The New Stack Makers podcast recorded live at Palo Alto Networks’ studio in Santa Clara, CA, is how to protect software throughout the entire supply chain. The guests were:
Dr. Chenxi Wang, a managing general partner for Rain Capital, a keynote speaker and a “Forbes” contributor.
Rochelle Mattern, a Google Cloud customer engineer at Google.
Gareth Rushgrove, a director of product management at Snyk
The New Stack Publisher Alex Williams hosted this episode.
Time series data management continues to underpin huge swaths of application deployments today across on premises, and increasingly, cloud native environments. Whether it’s video streaming, real-time financial security data management, energy utility management or any application that requires time stamps for often very complex datasets at massive scales, time series data will play an integral role. Today’s time series data platforms can typically be used for data analysis and forecasting by processing millions of data points per second.
Pricing has also become affordable for a growing number of enterprises seeking high-powered data analysis as a way to distinguish themselves from the competition. These organizations also do not necessarily have the financial backing that the world’s largest financial institutions or Fortune 100 companies have at their disposal.
In this The New Stack Makers podcast, Chris Churilo, responsible for technical product marketing at InfluxData, offer some background and perspective on why organizations increasingly rely on time series databases to “make products or services better.” Churilo also discussed why organizations are shifting their databases and management to cloud environments and why InfluxData recently extended to its InfluxDB Cloud 2.0 serverless time-series Platform as a Service (PaaS) to include Google Cloud Platform (GCP) as well as Amazon Web Services (AWS) cloud environments.
“Time series data is useful for monitoring anything that you want to make improvements on,” Churilo said. “So, of course, your cloud infrastructure is one thing that you definitely want to always be monitoring to make sure that you can provide the best service, especially if you have applications sitting on top of it that are customer-facing or even internally-facing — no one can tolerate having a slow application.”
Prisma, from Palo Alto Networks, sponsored this podcast, following its Cloud Native Security Live, 2020 Virtual Summit held Feb. 11, 2020.
The traditional role of the IT security professionals in the past largely involved drafting and implementing policies and best practices, as well as managing security-vulnerability detection and remediation. Interaction with developers was usually relegated to the post-deployment stages of software development.
But in this new age of DevOps, security practices have evolved, especially for cloud native security. Many of the differences can be attributed to how software development underpins DevOps processes. Consequently, security team members have become more development-focused and should play a role throughout the entire production pipeline (think of it as part of a shift to the left in CI/CD).
In this edition of The New Stack Makers podcast recorded live at Palo Alto Networks’ studio in Santa Clara, CA, how security practices have evolved and changed are discussed. The guests were:
Ben Bernstein, senior vice president of product and engineering at Palo Alto Networks.
Matt Chiodi, chief security officer of Public Cloud at Palo Alto Networks.
Xiaobo Long, senior vice president of cloud security at Citibank.
In many ways, the evolution of the role of the security professional for cloud native environments is part of the change. In that respect, security, as well as DevOps, is about culture, and thus, people.
“The DevOps movement enabled not just a digital transformation on the business side,” but digital transformation also “transformed the processes and the things that people do to deploy software and to build software. New programming languages that were previously dictated by the company are now available to everyone,” Bernstein said. “So, it’s all about the people and giving them the ability to choose the best tools for themselves and security has traditionally not been that way. And what you can see is that for us as a security company, it’s very important to empower the people to not only make the right security decision but also give them a set of a wide range of capabilities to pick and choose what they think is most important.”
No matter what you call this role — developer community manager, developer evangelist, developer advocate, developer relations, or, cheekily, developer avocado — it's got two things in common. It's one of the most expensive, travel-heavy roles in a tech org and it's one of the hardest to measure. That combination means metrics often make or break your job.
But first, what is this role? Good question to which there are many, many answers. In this episode of The New Stack Makers, Camunda's Director of Developer Relations Mary Thengvall talked about her definition. And she should know, she wrote the book on the business case for developer relations.
To her, the DevRel arena is "anyone who is responsible for enabling developer audiences and making them successful.
In this The New Stack Makers podcast, The New Stack Founder and Publisher Alex Williams spoke with Ayesha Mazumdar, senior UX designer at Optimizely, during Node+JS Interactive in Montreal about what needs to be done — and why human-centered designs are becoming not only nice-to-have features but technical requirements.
Oftentimes, when developers and engineers think about human-centered design, there is a “very prominent tendency to go around designing for humans like us,” Mazumdar said. “This is subconsciously something I think we all fall victim to, but I think [human-centered design] is becoming this technical requirement,” Mazumdar said. “We’re realizing certain users aren’t able to interact with the application we’ve built in certain ways, because we never accounted for that use case in the first place.”
The main issue is that a design might be accessible for some people, but not necessarily for the end user, Mazumdar said. “Accessibility has to be continued down the line, and show up in the developers workflow so that we can ensure the final product is actually usable by absolutely everyone in all aspects,” Mazumdar said “And so I think, making it a technical requirement involves making it part of your development process,” including making it part of GitHub and Q&A processes, for example. “Inserting accessibility checks along the way ensures that we don’t lose it at any point during the development cycle,” Mazumdar said.
Prisma, by Palo Alto Networks, sponsored this podcast, in advance of its Cloud Native Security Live, 2020 Virtual Summit Feb. 11, 2020.
For many organizations, becoming a software company hinges on making a successful shift to cloud native platforms. This makes sense as a rapidly growing number of organizations, both in the private and public sectors, can achieve very tangible benefits by making the transition. The ultimate goal is typically being able to vastly improve the digital experience for the end-use customer.
In this, The New Stack Makers podcast, Morello and Aqsa Taylor, a product manager for Prisma Cloud Compute, discuss what organizations should know about security before making the cloud native native shift. The themes covered include, among other things, what a cloud native security platform should offer and the evolution of security in the cloud native era.”
In this The New Stack Makers podcast, Guillermo Rauch, founder of Zeit, and co-creator of Next.js, said much of his work today involves network synchronization. More specifically, he described his work with state and how it’s synchronized over networks and how that has affected his creation of policy structuries for applications. He also described his ambitions to help improve the groundwork for coherent and consistent systems for data consistency models.
The theme of interconnectivity is also “a great segue into how our deeper thinking has gone into building a resilient systems from both a service architecture perspective but also within the context of front-end applications,” Rauch said.
In this latest, The New Stack Makers podcast recorded live at IFX2019 in Downtown Las Vegas, Matt Taylor, senior vice president, worldwide sales and business development, Ampere Computing, a semiconductor technology provider, discussed how the options for server components, especially processors, are widening and the underlying business needs for why that is the case. “Those options are starting to become much more real, across the entire landscape and more accessible,” Taylor said. “They are more accessible for developers and end users, and I think it is becoming a lot more common.”
If there’s a sign something in IT has moved past the hype, it’s not that digital organizations continue to adopt it, it’s that they continue to see better and better results. Both the most traditional and the most forward-thinking, DevOps organizations are seeing continually improved outcomes.
This is especially true for so-called DevSecOps orgs. You know, the ones that bake security right into their people, processes, pipelines and code.
In this episode of The New Stack Makers, publisher Alex Williams sits down with Alanna Brown, director of product marketing at Puppet, and Charles Betz, an analyst with Forrester, to talk about the current state of security in DevOps. Brown is the co-author of 2019 State of DevOps Report — and of the previous six reports — while Betz is co-author of Top 10 Trends That Will Shape Modern Infrastructure And Operations In 2020.
During this episode of The New Stack Makers, we talk to Daly about how you can go beyond the buzzword of open source toward true public collaboration, reaping all the benefits to your business that can come with it.
First, while open source is a decidedly nice PR move, why would a company want to risk their trade secrets going public? And if it’s open source, couldn’t people use it in ways you don’t want them to?
Daly argues that open source is an excellent asymmetrical strategy that (starts to) even the playing field between behemoth software corps and the little startups that could go global.
She also says open sourcing software leads to easier patent and legal review. And that having a good patent will shield you from ne’er-do-wells. During this interview, Daly breaks down the two kinds of open source software patents, which differently allow people and organizations to read and use your open-sourced code:
Container security has always been a concern — especially now in the wake of recent highly publicized vulnerabilities and breaches. But while containers benefit from running in isolated environments and have other advantages compared to traditional application structures, the peculiarities of Kubernetes as an orchestration platform represents additional security concerns. As Kubernetes continues on its rapid path of adoption, the need for a reliable framework for vulnerability detection and management becomes that much more important.
The vacuum for a definitive audit of the state of Kubernetes security set the stage for publication of the Kubernetes Security Audit Working Group. On hand to discuss the audit during KubeCon + CloudNativeCon were Jay Beale, CTO of InGuardians, and Aaron Small, a product manager for Google, who are also both co-leads of the Kubernetes third-party assessment project. They discussed this and how Kubernetes, compared to Docker containers, represents a new, and ultimately, risky world of dependencies during a live recording in San Diego for this edition of The New Stack Makers podcast.
In this next episode of The New Stack Makers, Editor in Chief Alex Williams sits down with Buddy Brewer to talk about the user experience that New Relic’s customers are working to deliver to their customers. And about how monitoring inside mobile and web apps for end users — including perceived performance and distributed tracing — helps everyone understand just what that experience is.
In this The New Stack Makers podcast, CloudBees CEO Sacha Labourey discussed the resulting complexities of CD and software delivery management in 2020, as well as the role Jenkins X and CloudBees are expected to play in what should be an especially exciting year for at-scale development.
For many organizations, 2019 was a pivotal year due to the snowball effect of Kubernetes adoption, as both opportunities — and complexities — emerged.
In this, The New Stack Makers podcast episode, Paul Dix, co-founder and CTO of InfluxData, discusses what is in store for 2020 for databases, both on an industry scale and how InfluxData’s development teams hope to rise to today’s challenges. Distributed tracing, serverless “pay as you go” business models, InfluxData’s Flux programming languages for databases and the outlook for stateful database applications in Kubernetes were also under discussion as Dix spoke freely and candidly about the different topics.
In this episode of The New Stack Makers, we talk about all this and more with Susanna Kass, who, after 30 years designing, building and operating data centers, is now the data center advisor for the United Nations Sustainable Development Goals Program.
For data centers, it all comes down to stopping what Kass refers to as the “dirty cloud,” which sees most data centers depleting energy, land, and water. Data centers need to make a pledge to achieve carbon neutrality for every kilowatt hour that is consumed, be accountable for the phase out of coal, and transition to a carbon-neutral infrastructure by using and generating renewable energy per KW hour consumed by site.
Kass describes this as using “nature-based technological solutions to protect our earth, resources and the environment.
In this The New Stack Makers podcast, Andrew Tunall, general manager, serverless and emerging cloud services; and Erica Windisch, principal engineer, from New Relic discuss how Lamba and serverless have changed and evolved and how some organizations have benefited.
When the concept of serverless was introduced, Windisch said much time and effort were spent just explaining “to people what serverless was.”
Today, organizations are introducing levels of complexity through their deployments on Lambda and serverless. Examples include distributed applications, Windisch said. “More people are running into these harder things: These sort of use cases with more complex architectures,” Windisch said. “It’s not because serverless is hard — it’s because people are at the maturity level that they can build, so they’re building complex applications in serverless rather than in containers.”
Maxine, the fictional character in Gene Kim’s latest book “The Unicorn Project,” likely shares your plight. In this edition of The New Stack Makers podcast, Kim, who is also the author of the seminal and now classic “The Phoenix Project,” discusses Maxine’s daily struggles — and without disclosing spoilers — successes.
Maxine shares the developer’s modern-day angst in this paradoxically open source and DevOps Renaissance. While her plight is fictional, Maxine shows how developers, with management’s backing, can transform an enterprise’s DevOps with its from-the-front-lines fictionalized case study with human drama to spare.
And, of course, it is never easy, whether you are trying to convince management to back you or your team to implement DevOps — or if you are Maxine in “The Unicorn Project.” In the the first third of the book, Maxine is stranded on an island” and “everything requires a ticket — not one ticket but like 30 tickets,” Kim said. “She’s having to pester people to get even license keys or environments,” Kim said.
In this episode of The New Stack Makers, Williams talks to Pivotal’s Cornelia Davis and Dell Technologies’ William Geller about this journey to bring this majority on-board with Kubernetes, and how to use managed architecture to overcome the often overwhelming complexity of Kubernetes orchestration.
Davis, VP of technology at Pivotal, pointed to MiniKube as one of the major ways to bring those people on board.
“With a simple download and a couple of commands, you’re on your way. You’re going to be pushing apps into Kubernetes. And you’re doing that on your own laptop or maybe they’re doing it with one of the cloud service providers.”
She continued that “And it’s all so easy. It just works.”
The New Stack Founder and Publisher Alex Williams sat down at the IFX infrastructure conference with one of the companies looking to apply the speed, delivery, and, most importantly, the resilience built into software teams to the infrastructure side. After over a decade at Microsoft followed by more than a year at AWS, Luke Hoban, CTO of Pulumi, was ready to build something that helps developers work with the cloud. The way to bridge the chasm and bring the application development and infrastructure on either side closer together.
The New Stack Editor in Chief Alex Williams sat down with Steven Wong and Dejan Bosanac at KubeCon to talk about just this. Wong is a software engineer on the Cloud-native business unit at VMWare and Bosanac is a senior software engineer at RedHat. Both are also on the Kubernetes working group that looks to address the limitations of Kubernetes on the edge.
Wong started by offering the example of modern luxury car models, which — from entertainment systems to antilock breaks to traction controls to even power windows and doors — may have as many as 37 computers riding around inside them. Each of these connected objects are sources of data that often need configuration and updates.
He looks at Kubernetes orchestration as being uniquely suited to solving this problem — eventually.
Special Guest - Eliot Horowitz MongoDB. In this latest The New Stack Makers podcast recorded live at IFX2019 in Downtown Las Vegas, Horowitz puts the complexities of today’s databases-development challenges into context and describes MongoDB’s evolution to keep up with the paces of change as applications become increasingly more cloud native-centric and stateless.
Brian Dawson, director of product marketing for CloudBees, certainly knows a lot about silos, and especially, how to remove them in support of a healthy DevOps culture and a well-oiled CI/CD pipeline. During the past 30 years of his career, for example, he's seen the adoption of many tools and languages. But unfortunately, new and powerful tools have also traditionally created more barriers to constant and intense collaboration for CI/CD. The problem has certainly been compounded by the explosion in choice of open source tools, especially for cloud native deployments.
Special guests Parasar Kodati and Audrius Stripeikis of Dell EMC speak with us about how the intrinsic battle in modern digital organizations lies between speed and security. As software development velocity seems to endlessly increase, IT organizations are looking at what tools are available to them to provide guardrails and governance —without slowing things down.
Infrastructure-as-code is arising as the solution and the common language between the two sides. As cloud-like consumption is being demanded by developers and automation continues to be the secret to successful DevOps organizations, tooling and specification arises as the welcome solution.
This is what one can say with a reasonably high degree of certainty: organizations are deploying applications in hybrid environments consisting of legacy datacenters and often different cloud services, while the open source business models allowing them to do that are changing. In this context, for database management and use, the choice of NoSQL remains a safe bet for today’s deployments, especially for multi-cloud environments, Alvin Richards, chief product officer, Redis Labs said in this latest edition of The New Stack Makers podcast
At AWS re:Invent this December, The New Stack Founder and Publisher Alex Williams sat down with Liran Tancman and Corey Scobie. Scobie is the CTO of 10-year-old open source automation platform Chef. Tancman is the CEO of cybersecurity newcomer Rezilion, which allows cloud environments to self-protect and revert to the previous intended state automatically when an attack occurs. This week Rezilion announced $8 million in seed funding.
Williams spoke with Tancman and Scobie about a new partnership between Rezilion and Chef to extend the automation and reliability of DevOps to include the necessary resiliency of security automation.
Data streaming is needed more than ever. It's a consideration as data becomes as much a requirement to achieve agility and composability with events-based principles to build business state as they come from multiple feeds and sources.
In this The New Stack Makers podcast recorded live at IFX2019 in Downtown Las Vegas, Zachary Smith, CEO and co-founder of Packet, and Ivo Rook, senior vice president at Sprint, discussed how bare metal fits into the IoT story. The December 4-5 event was Packet’s second annual vendor-neutral infrastructure conference and is organized at the same time as AW Re:Invent.
For the first 12 years of Gwen Shapira’s career, she worked on relational databases, where she learned all about both their power and limitations. In her The New Stack Makers interview, Shapira, a system architect at Confluent, excitedly shares how event-driven architecture literally breaks down those limitations and redefines the boundaries of service responsibilities.
Event-driven architecture is part of the broader industry trend of separating components and streamlining processes so that releases are faster and organized around user activity. It's all about pulling apart applications into components — usually microservices — that you then chain together to better service business needs through the publishing of, listening to, and reacting to those events.
In this edition of The New Stack Makers podcast recorded live at KubeCon + CloudNativeCon North America 2019, Dell EMC's Nelson Hsu, director, solutions marketing for data protection, and Alexander Almeida, consultant, product marketing, describe the intersection of data protection and cloud native deployments and DevOps' roll in securing mission-critical workloads. Sponsored by Dell.
This is the classic security problem Gareth Rushgrove, director of product management at Snyk, pointed to during his conversation with The New Stack founder and publisher Alex Williams at KubeCon's Cloud Native Security Day. Snyk is a Software-as-a-Service dedicated to helping organizations flag and fix vulnerabilities in their open source, third-party dependencies.
The New Stack Editor in Chief Alex Williams sat down at last month’s Kubecon to talk about telco’s cloud-native future with Heather Kirksey, VP of community and ecosystems at OPNFV, and Taylor Carpenter, partner and founder of Vulk Coop design and development cooperative. The different collaborative, telecom-focused Linux Foundation and CNCF working groups that Kirksey and Carpenter are a part of have witnessed — and sometimes driven — telco’s move over the last five years from monolithic hardware appliances toward what’s now known as the cloud.
Deploying and managing Kubernetes infrastructure may be the most challenging aspect of developing and delivering cloud-native applications. We will discuss leveraging a purpose-built appliance that provides a production-ready Kubernetes platform that also supports existing VMware virtualized applications in hybrid (private and public cloud) deployments. This approach provides rapid results to quickly stand up the environment as well as automated Lifecycle Management of the entire stack to enable organizations to securely and non-disruptively stay up-to-date and secure with their Kubernetes and vSphere clusters. We will discuss what is available today from Dell Technologies Cloud with PKS on VCF on VxRail as well as the roadmap forward for next year and beyond with Project Pacific and Tanzu Mission control.
Janikiram MSV is one of the few analysts and writers who is also a certified member of the Kubernetes community. He is able to bring into his writing an analysis that details the issues that an everyday users and developers face. He is also a regular contributor to The New Stack, on Kubernetes and other technologies.
In this edition of The New Stack Makers podcast recorded live at KubeCon + CloudNativeCon North America 2019, Janikiram discusses why developer happiness is such a challenge, the new role of the configurator and the issues that are coming as Kubernetes matures and isolation becomes a larger issue. He also discusses multi-tenancy and challenges to come as users adopt services and face security risks with less defined cluster isolation.
This podcast is sponsored by InfluxData. In this week’s The New Stack Makers podcast interview in advance of AWS re:Invent, The New Stack Founder and Publisher Alex Williams caught up with InfluxData Vice President of Product Tim Hall to discuss why time-series databases are gaining in popularity with developers and how they differ from other databases.
Service meshes, Istio and the underling architectures — fine topics to discuss over a short stack with The New Stack. At Kubecon + Cloud NativeCon in San Diego, We explore the scaling of application architectures and how business objectives fit with approaches, team development and workflows that come with service mesh technologies.
Guests: Carlisia Campos, Tom Spoonemore, and Efri Nattel-Shay
Velero is an open source project that provides backup, restore and migrating capabilities for Kubernetes. Originally developed by Heptio and known as Ark, Velero is supported by Dell's PowerProtect, allowing users to back up their Kubernetes clusters. In an interview at KubeCon, The New Stack discussed Velero with VMware's Carlisia Campos, a maintainer for Velero and member of the VMware technical staff; Tom Spoonemore, VMware's cloud native apps director and Dell's Efri Nattel-Shay, director of product management.
The idea is to empower all DevOps' stakeholders with better access to continuous integration (CI)/continuous delivery (CD) pipelines. Your organization also very likely relies on Jenkins as the backbone for the production pipeline with a reliance on Git to share and collaborate.
However, the problem has long been that Jenkins is notoriously hard to implement and use for many organizations. The added complexities of shifting to cloud native and Kubernetes platforms have further compounded the difficulties — but this new age of Jenkins and cloud native deployments have also set the stage for the creation of CloudBees' open source Jenkins X. CloudBees created Jenkins X mainly to help facilitate and automate CD pipelines to Kubernetes and cloud native environments. The idea is also to allow Jenkins X to make it easier to develop and deploy cloud native applications to Kubernetes without having to learn the intricacies of the orchestrator. Jenkins X is also one of four projects of the Continuous Delivery Foundation (CDF), which also includes Jenkins, Spinnaker and Tekton.
CloudBees says it is also continuing to try and improve Jenkins X, by simplify how developers and all DevOps stakeholders work with the tool. To that end, the company has developed its first-ever graphical interface.
In this The New Stack Makers podcast recorded during KubeCon + CloudNativeCon in San Diego last week, CloudBees' Moritz Plassnig, vice president, cloud and Peter Muir, lead architect, spoke with Alex Williams, founder and editor-in-chief of The New Stack about how CloudBees continues to try to make Jenkins X both more accessible and easier to use.
Guests: Sugu Sougoumarane & Quinton Hoole
Google and other tech giants can be hard examples to follow. As organizations rush to scale their infrastructure on a mix of on-premises and cloud environments, especially on Kubernetes, they often struggle when trying to store and analyze data from stateless sources. A lot of the traditional storage databases have not worked at the scale needed, while the early cloud services, such as AWS and Google, developed their own storage environments internally.
“Kubernetes was very much focused initially on the stateless workloads and didn't do a very good job, to be perfectly honest, of providing any kind of support for storage, other than to the extent that you could connect to an existing public cloud provider,” Quinton Hoole, technical vice president of Huawei’s Futurewei Technologies, said. “I think that's evolved a lot over the last several years, as there are many different cloud native database [options]. People are starting to do serious stateful workloads in the cloud and in Kubernetes, in particular.”
In this edition of The New Stack Makers podcast recorded live at KubeCon + CloudNativeCon North America 2019, Sugu Sougoumarane, co-founder and Chief Technology Officer at PlanetScale, as well as Hoole, discuss what tools and approaches organizations can take to store and manage data from Kubernetes and containers.
They also cover how storage and database-management tools are catching up to organizations’ often complex infrastructure needs. However, finding the right tool mix is not easy.
KubeCon + CloudNativeCon sponsored this podcast.
Lauren Maffeo studies the emerging threats of artificial intelligence in her work as an analyst for GetApp, a software reviews site under Gartner Research that uses proprietary data to help match software buyers with the best tools for their businesses.
In these two episodes of The New Stack Makers, Maffeo provides her perspective on artificial intelligence, its power and the threats it poses when unchecked.
The top performing companies in the financial markets are using technologies based upon artificial intelligence. These technologies are powerful but can at times prove to pose indirect biases. That can lead to a bank loan getting denied, a passport not issued, a payment getting stopped and a black person getting a longer prison sentence due to the color of their skin.
The threads and threats that come with computer intelligence were apparent to Pamela McCorduck in 1960 as a graduate student in English Literature. Those same threads and threats are apparent today in the biases that can come with black box algorithms and indirect biases that Lauren Maffeo studies in her work as an analyst for GetApp, a software reviews site under Gartner Research that uses proprietary data to help match software buyers with the best tools for their businesses.
In these two episodes of The New Stack Makers, McCorduck and Maffeo each provide their perspectives on artificial intelligence, its power and the threats it poses when unchecked.
Docker. You know it. You use it. You might well be confused by it. Is it Docker? Or is it docker? And why has Docker (or docker) taken a back seat to Kubernetes? There are so many questions regarding this technology. But one question that has been on the hearts and minds of many a container administrator is security.
You might think that, given the isolated nature of containers, they’d be harmless. On certain levels that is the case. If a container is deployed correctly, it cannot access the deploying ecosystem. In theory. But, as we’ve all discovered in the realm of technology, where there’s a will there’s a way.
Although you might fully understand how to deploy a containerized application and scale it out to meet the needs of your company, are you taking the necessary steps to ensure that application, and the hosting environment, is as secure as possible?
What can you do?
Listen as Jack Wallen discusses these topics with Scott McCarty, principal product manager for containers at Red Hat.
First came agile. Then came DevOps. Except they only came to a few departments, mainly the traditionally IT ones. What's keeping them from reaching the most extreme realms of tech? According to Luke Marsden, CEO and founder of Dotscience, enterprise-grade artificial intelligence (AI) and machine learning is being held back, in part, because the mathematicians and statisticians behind it are stuck in the days of Waterfall — still emailing code back and forth to each other.
Basically most enterprise AI and machine learning initiatives are stuck at the gate. On this episode of The New Stack Makers, we talk to Marsden about why.
VMware has certainly seen some changes in its corporate structure during the past few years — but today, VMware’s business moves have been especially relevant for developers. Following its agreement to purchase Pivotal in August, for example, VMware continues to try to adapt its open source contributions and services for the ever-evolving needs of the community, with a greater emphasis on Kubernetes. This means VMware is increasingly engaged in offering and creating the tools and platforms developers need for Kubernetes, as well as for other open source projects.
In this edition of The New Stack Makers podcast: Kubernetes, open source, the developer experience and new technologies. VMware’s role during the upcoming KubeCon + CloudNativeCon conference was also discussed. The guests from VMware on hand to discuss these topics were:
Bryan Liles, senior staff engineer.
Tim Pepper, senior staff engineer.
Tasha Drew, product line manager.
All three guests are actively engaged in the open source community, and particularly, in improving the Kubernetes experience for DevOps engineers.
Executives from Pivotal joined this latest episode of The New Stack Makers podcast recorded at the SpringOne Platform conference to discuss what the developer experience is like around the world. They were particularly well-suited to offer input about what developers face as customers worldwide since each executive is based in the U.S., Europe and Asia, respectively. The common-thread experiences they described also covered what it's like to deploy software on Kubernetes and CI/CD best practices and tools.
The podcast guests from Pivotal were Lionel Lim, vice president and managing director, Asia Pacific and Japan; Chad Sakac, Americas Sales; Bas Lemmens, vice president and general manager, EMEA.
At least in the tech industry, the word “community” is teetering somewhere between adage and advantage. As developer experience becomes more of a necessity, does building a community have to be part of your business strategy?
In this episode of The New Stack Makers, we sit down with Jono Bacon, community and collaboration strategy consultant, speaker and author. Our conversation unsurprisingly begins with talking about the emerging role of developer relations, developer advocate or developer evangelist. It is often an external-facing role, and yet acts as the liaison among infrastructure, product and marketing. It’s a role that is still rather a fish out of water, often immeasurable and flopped around from department to department.
Stateful data management and storage are set to remain ever-present in IT infrastructures for the foreseeable future. But as containers and Kubernetes take hold, storage management for stateless and multiplatform environments is set to change. This holds true whether your organization employs hundreds of developers spread around the world who regularly spin up stateless containers or if your organization has data spread among multicloud and on-premises legacy environments. In any case, all of this data must be stored somewhere in a stateful form.
At the end of day, all that “state” really means is that “data outlasts containers,” Murli Thirumale, CEO and co-founder of Portworx, said. However, in this era of stateless data, a new kind of storage has emerged.
In this edition of The New Stack Makers podcast, recorded during TC Sessions: Enterprise in September in San Francisco, Thirumale described this new era of storage management and Portworx's role in this context as a provider of stateful storage for containers and multiplatform environments.
How does your product change when it scales up in the open source world? How does that change your drive to create a better developer experience? In this episode of The New Stack Makers recorded at the SpringOne Platform conference, The New Stack founder and editor-in-chief Alex Williams sits down with Olga Kundzich, senior product manager for the Spinnaker continuous delivery platform at Pivotal. They discuss the best practices that help drive Pivotal's open source community, and how that informs Spinnaker's roadmap.
It wasn't that long ago when data fabrics were mainly relegated to various strategies organizations had in place for data management. The concept was largely limited to making sure data was where it should be and stored in the right places. Flash forward to today, and data fabrics are very much tied to often mission-critical analysis, often across a mix of multicloud and on-premises environments. DevOps teams, of course, increasingly rely on data fabrics to help support DevOps operations and culture.
In this edition of The New Stack Makers podcast, Neil Stanley, product manager, data fabric at NetApp Cloud Data Services, and Jason Blosil, senior product marketing manager, cloud solutions, for NetApp, spoke about what data fabric means today, and how NetApp has adapted its architectural approach for modern DevOps challenges.
Data engineering is 10 years behind the software engineering world and, in many ways, remains mired in "spreadsheet land," Danielle Morrill, general manager for the GitLab startup Meltano, said. As a way to make up for the lack of viable data engineering processes, Meltano can meet the needs of organizations without the in-house expertise of software developers who can invent a tailored solution from scratch. "A lot of people are great with spreadsheets and can't write code or think they can't write code, but conceptually, they already are," Morrill said. "So, I think the roadmap [for Meltano] is very much about bringing them along."
In this episode of The New Stack Makers podcast recording during the GitLab Commit conference in Brooklyn, New York in September, Morrill described how Meltano casts an as wide net as an open source alternative for data modeling, analysis and management.
It wasn’t that long ago when Dell Digital’s software product teams were typically bogged down in very silo'ed development cycles. One of the more troubling effects was how long it took to complete projects, often measured in months. In some cases, software releases could even take a year before deployment. And all to often these very long development cycles did not result in something that met Dell Digital’s business goals — as in, creating something the customer wanted or needed.
Besides the requisite culture for agile development, missing in Dell’s digital-transformation strategy was a single underlying platform that Pivotal Labs eventually provided, said Greg Bowen, chief technology officer and senior vice president, Dell Digital (the IT organization that supports Dell).
With the help of Pivotal Labs' platform and the adoption of a more agile DevOps culture, Dell Digital's teams are now "extremely hyper-focused on the outcome with the business partner right there in the development process,” Bowen said. “And so, that's allowed us to take the scale of an enterprise company, and become almost startup in nature.”
In this latest episode of The New Stack Makers podcast recorded at the SpringOne Platform conference, Bowen discussed how Dell Digital's transformation was dependent as much on culture and processes as it was on selecting the right technologies and tools including, as mentioned above, Pivotal Labs' platform.
There are many opinions out there about what your organization must do — or buy — to make sure container environments are secure. But taking a step back, containers stand on the shoulders of open source, and the security and compliance processes that teams have learned during the past decades remain applicable in many instances.
At the same time, container security has its own set of rules and best practices that are often less than apparent. Worse still, much of the confusion around open source security remains, further compounding the challenges.
“If I look at the container environment, we’re kind of back in the bad old days where the container Docker file may have a license, but almost always it is not the license for all of the software that is included in the container, which usually contains many components,” Dirk Hohndel, vice president and chief open source officer at VMware, said. The quintessential question, Hohndel says, is how do you find secure containers and “ensure that the one that you have is actually secure?”
In this latest episode of The New Stack Makers podcast, host Alex Williams discusses the status of compliance and security now that containers are becoming such a core part of open infrastructure. He is joined by VMware’s Hohndel and Andrew Wilson, a long-time chief open source compliance officer at Intel.
The technology industry is undergoing a data revolution in which the unlimited storage and compute power of the cloud is changing how data is stored, processed and managed.
Alluxio is a platform for data orchestration that aims to simplify and standardize how data is managed across different types of infrastructure by creating a layer of abstraction between the storage and application layers.
The Alluxio orchestrator virtualizes data and allows applications to access it in a way that’s compute, storage and cloud agnostic. It’s a platform designed to eliminate data silos and make data readily available and performant for developers.
Haoyuan (H.Y.) Li, CTO and founder of Alluxio, is a co-creator of the Apache Spark streaming library and built Alluxio as an open source virtual distributed file system for a computer science PhD project at Berkeley. Li is now building a startup, which currently boasts 40 employees and several large enterprise customers. The company offers enterprise features and support on top of its open source project.
Porsche has always been about technology since Ferdinand Porsche founded the iconic brand in 1931. This is manifest in today’s new models, whether it’s how engineers have shaved milliseconds from the turbo rotations for an even more responsive takeoff blast in the new 2020 Porsche 911 Carrera 4 or the battery-powered motor for a zero-to-60 mph acceleration in the Taycan Turbo S in a slam-you-back-in-your-seat 2.6 seconds. But Porsche is radically changing, the company asserts. This means the Porsche experience — for those lucky enough to have driven one of the fabled models — is no longer brought to you by a sports car manufacture...but by Porsche as a “mobility provider.”
And this Porsche metamorphosis as a mobility provider hinges on software development, company executives say.
In this latest The New Stack Makers podcast recorded at Cloud Foundry Summit EU, hosted by Alex Williams, founder and editor in chief of The New Stack, Porsche’s Matthias Hub, Porsche IT project manager and prototyper, and Thorsten Türk-Steppe, Porsche product owner, described how Porsche is reinventing itself as a company through its DevOps’ software emphasis as a mobility provider.
Watch on YouTube: https://youtu.be/9zReDsl41ac
When The New Stack Editor-in-Chief Alex Williams sat down with Pivotal’s VP of Technology Cornelia Davis at SpringOne Platform in Austin Texas, they had a lot to talk about. Almost 40 years. Davis’s tech career began in aeronautics which could go give years from code written to rocket launched. She has journeyed right alongside as we went from SOA and SOAP to REST to the distributed systems we have today. During her talk and in this conversation, she reflects on the patterns that drove APIs from a RESTful layer toward toward true autonomy, where everything is as loosely coupled as possible, with bounded context.
A chat with Davis feels one third practical computing, one third theoretical mathematical foundations, and a third grammar. To give context to the chat, let’s give some background.
The traditional object-oriented or imperative programming is focused on using statements to change a program’s state. On the other hand,
declarative or functional programming focuses on what the program should accomplish and isn’t worried about how that result is achieved, This is why the first is referred to as stateful programming, while the latter is stateless.
In this conversation, Davis describes functional programming as a statement of relationship between the first part of a problem and the rest of the problem. You trust that the second half of that problem is correct, so all that is important is how you combine these things.
Watch on YouTube: https://youtu.be/ZCbWNBw_fHg
One of the main components of the mantra “all companies are software companies” is organizations’ DevOps must deploy and update applications rapidly and at scale. The supporting infrastructure hosting the production pipelines and deployments must also be both safe and sound, regardless of whether it is on the cloud, on premises or — more likely — a mix of both
The main theme of this episode The New Stack Makers podcast, hosted by Alex Williams, founder and editor in chief of The New Stack, was how NetApp offers a foundation for DevOps deployments and data management across cloud native and on premises infrastructures. NetApp’s Diane Patton, hybrid cloud services (NetApp Cloud Services on HCI) and Robert Esker, product management and strategy, discussed, among other things, how NetApp’s HCI can serve as the underlying foundation for a number infrastructures.
"We provide this common set of tools, so no matter where the developer wants to deploy their application, they can use that exact same toolset and deploy it either on-prem or deploy in any of the major cloud providers as well.," Patton said.
Building enterprise level software takes a lot of skill and creativity. When developers want to come together to discuss, create, and inspire one another, the place they flock to is the SpringOne Platform conference, which took place this year in Austin, Texas. Pivotal Senior Vice President of Product James Watters said it best at the keynote for the event, which he later recapped alongside VMware Principal Engineer Joe Beda in an interview with TNS founder and editor-in-chief Alex Williams.
"It's because it's the one place for people who are really passionate about building modern applications in enterprises all hang out. There's some places where that's considered like, 'Oh that won't happen,' or 'We're not doing that yet,' or, 'We're straddled with so much heritage,' but you know, this is the conference where on stage you can see Netflix saying, 'We're all in on SpringBoot, it's how we build all our applications,' and then the next customer gets up from Home Depot or TDA and says, 'We do it the same way,' and to me that's kind of inspiring because it's I think kind of a lifeblood for enterprises to come to a place where they have a peer group that's doing the same difficult thing which is modernizing their applications," said Watters.
One of the themes of the Cloud Foundry Summit series has always been to help reinforce the strong sense of community among those who take part in the open source movement. In this way, the recently held Cloud Foundry Summit EU in September lived up to its mission. Among those on hand at the conference whose jobs are to initiate and educate organizations, about open source and the Cloud Foundry, as well as to include more individuals in the movement, were Ivana Scott, business operations manager, EngineerBetter and Sara Lenz, sales and account Manager, anynines. They were the guests on The New Stack Makers podcast recorded at Cloud Foundry Summit EU, hosted by Alex Williams, founder and editor in chief of The New Stack. Both Lenz and Scott are particularly well-positioned to offer a fresh perspective on how to grow the community through education.
Scott first became involved in the open source community in in 2007 when she joined training provider in London. There, she was part of the events team, and was involved in organizing events, training courses, conference and meetups, while devoting a “huge amount” of effort to support open source communities. She then became directly involved in the Cloud Foundry community after joining EngineerBetter in 2018.
Watch on YouTube: https://youtu.be/CZ45-j2e_eY
A question that may come to mind for those managing enterprise workloads is: What is Trident? This is the main question that George Tehrani, Director of Product Management, Open Ecosystem answered on this episode of The New Stack Makers, hosted by TNS founder and Editor-in-Chief Alex Williams.
"By and large, any workload of importance to the enterprise needs some sort of persistence. So what Trident is, is an open source storage orchestrator that NetApp developed and continues to maintain. It greatly simplifies the creation, management, and consumption of persistent storage for enterprise workloads in Kubernetes, as well as the other major distributions of Kubernetes such as OpenShift."
Three years ago, Lukas Lehmann, head of cloud services, Swisscom described how his organization at that time was largely client-server dependant. In order to achieve its goals as both Switzerland’s largest telecom and as an IT provider, it became apparent that the Swiss firm had to find ways to scale across its entire operations in a way that remained consistent and robust.
In this podcast from Cloud Foundry Summit EU hosted by Hosted by Alex Williams, The New Stack founder and editor-in-chief, Lukas Lehmann, head of cloud services, Swisscom discussed his organization was able to scale to achieve its shift to at-scale application development goals across cloud environments thanks largely to partnership with Cloud Foundry. Stefan Voegele, expert middleware engineer, for insurance provider Swiss Re, was also on hand to discuss how his firm uses Swisscom’s platform as a service (PaaS) in its shift to a cloud environment.
“Helping our customers and ourselves make a digital transformation is key to us,” Lehmann said. “That is why such a platform [as Cloud Foundry’s] and being involved in such an ecosystem is very important for us.”
Watch on YouTube: https://youtu.be/42mNdpu_6wc
Alex Delgado, a security engineer at the Gremlin chaos testing service, points to the disconnect many enterprises have. It’s not that the developers aren’t building with the newest technologies like Kubernetes and microservices. It’s just that security and compliance haven’t even heard of these things. And it's increasing risk.
“You can’t secure something that you don’t know how it works,” he said, on this episode of The New Stack Makers, where Delgado reflects on his past at a security and defense enterprise and his present at scale-up Gremlin. He began his career in customer support and then remediation of customer concerns. That put him in an interesting but often frustrating position as he moved into security, which had him throwing code over the wall that was released maybe three months down the line.
Automating security is now more of an issue as attack surfaces become more expansive and change. We sat down at GitLab Commit Brooklyn with Shamiq Islam, Head of Application, Blockchain, and Infrastructure Security at Coinbase and Philippe Lafoucrière, Distinguished Engineer at GitLab to discuss all things security automation and why today’s enterprises should look into automating their security and closing the software development life cycle loop.
Watch on YouTube: https://youtu.be/JfZ-SoBRFkU
All things continuous integration, continuous delivery, the GitLab experience in new environments, and even mainframes were the topics of discussion taking place at GitLab Commit during an interview TNS founder & Editor-in-Chief Alex Williams had with Eddie Zaneski, Developer Relations Manager at DigitalOcean, Kyle Persohn, Senior Engineer at Northwestern Mutual, and Sean Corkum, Senior Software Engineer at Northwestern Mutual.
Launching the discussion was the topic of CI/CD in an organization. Specifically, how organizations can get their teams involved with and building out CI/CD.
"It has to be ingrained in the culture of the team to really take full advantage of everything that you can get from that. Making sure you're building fast, failing fast, and everyone understands and is totally on board like, 'Yeah, this is the right way that we should go,'" said Corkum.
It is certainly never easy to port existing software production pipelines and operations to a cloud native or, more typically, to a mix and match of cloud, bare metal and on-premises server environments. This assumption certainly held true for the situation T-Mobile was in during its digital journey . But while T-Mobile’s operations are on a gargantuan scale of magnitude compared to most organizations, T-Mobile succeeded by applying many of the same practices any organization needs to rely on, whether for a 10-person shop or if the company is Google. This includes an increasing reliance on GitOps for version control (VC) and repository functions but also as a way to combine all data access and functions into a single source to help manage the enormous complexity of multi-cloud and server environments, including, of course, Kubernetes deployments.
One of T-Mobile’s main goals was moving “a lot of those pieces out of the traditional location where they might be in a database of inside of a certain system of record, and a service registry and more into a repository. So, we're able to recreate things on the go to manage our user base in a more dynamic fashion,” Philip Marc Schwartz, principle engineer, software, T-Mobile, said. “It's been an eye-opening experience to be able to work through the problems that you see with those systems as you're trying to get them working. And it's very interesting to see those problems solved where you can really work on them in a finite level.”
Watch on YouTube: https://youtu.be/yT5zogF_NT0
"Cloud Foundry is a project that predates Kubernetes, and as container orchestration has evolved, we have started seeing more microservice components built into Cloud Foundry that were used as a way to containerize to some extent. This speaks to the history of project Eirini and project Quarks," said TNS founder and Editor-in-Chief Alex Williams during a live interview recorded at Cloud Foundry Summit Europe, where he was joined by Jennifer Spinney, Staff Software Engineer at Pivotal, and Vlad Iovanov, Technical Lead at Cloud Foundry SUSE.
Spinney went on to explain, "So, Cloud Foundry traditionally has this component called Diego, which is actually a rewrite of the old way that containers used to be run in Cloud Foundry via these DEAs, we replaced that with Diego when we did that we introduced this hard boundary between the API of CF and the back end that schedules containers and schedules your actual app workloads. So then when Kubernetes started picking up steam, because we have this hard boundary now between the Cloud Foundry API and the back end that's actually scheduling jobs, we could look at swapping out Diego with just Kubernetes because it's kind of doing the same thing. Back when we started Diego, Kubernetes wasn't fully there yet, there was still a lot of maturing to do. Now I think we're seeing Kubernetes becoming way more mature, and it's much more possible to just drop in Kubernetes instead of Diego."
At GitLab Commit, GitLab's first user conference that took place last week in Brooklyn, GitLab announced that it has received 268M in funding, valuing the company at 2.75B dollars. TNS Founder Alex Williams dove into this announcement and many more with GitLab CEO & co-founder Sid Sijbrandij, asking candidly what the next steps are for GitLab after it received that kind of funding.
"We're going to continue what we were doing. This money will enable us to keep hiring people, and keep hiring people to make GitLab more mature in every single aspect. GitLab is incredibly broad, started with version control and CI, but now we go all the way from planning what you want to do to monitoring the results of that. We want to make sure every part of GitLab becomes as good as the best parts," said Sijbrandij.
Once largely reserved for the finance industry, times series databases are increasingly emerging as must-haves for many organizations. A classic SQL database, for example, is not designed to process thousands or — in many cases — millions of data points per second that a time series database can monitor, track, analyze and assimilate for forecasting applications for real-time analytics and business intelligence. These applications often include application, server, network monitoring, for industrial or IoT data.
However, many organizations are faced with the conundrum of not being able to afford investing in the required hardware infrastructure for time series data analysis or most of their operations are cloud-based and they have faced a dearth of viable alternatives. As a solution, InfluxData, a leading data has launched InfluxDB Cloud 2.0, the first serverless time series platform as a service (PaaS).
In this The New Stack Makers podcast, Paul Dix, co-founder and CTO, InfluxData, discussed InfluxDB Cloud 2.0, and how the evolution of time series databases have evolved to create a need for a cloud-based alternative.
A question we’re asking a lot is: What is a developer advocate? Often followed by: Which department do you report to? How do you measure your role?
It’s a somewhat old role in the fact that people have been marketing to devs since software started getting sold. It’s a somewhat new role under its name. When Rob Zazueta mentioned he was hired at WeWork to build a developer relations team focused on internal developers first, it surprised me to realize that companies — even ones with massive API programs — aren’t really advocating to their internal developers. This is a shame. This would promote reusable code, shared learnings, and brand advocates that can go out and talk for you.
On this episode of The New Stack Makers, we sit down with Brian Douglas, developer advocate at Github. This is something he does for both external and internal developers.
When applying for an open award for people that did activism in the Portland tech community, Netlify's Head of Community Perry Eising found himself having to identify outside of his gender identity as a result of the form not having an option for nonbinary people to be recipients of the award. After realising he was getting mixed signals, he decided to ask the company about it directly, "That moment of bravery was just, I didn't know how they were going to respond. I didn't know how clued in they were to having people who were nonbinary as part of their organization, whether they knew what that was, whether they were going to treat me well, whether they were going to laugh at me. Us as underrepresented people in tech, I think there's always that nervousness if we're going to bring up a concern to people who were organizing something, whether they're going to have the knowledge to take that in, or whether they're going to reject us, or whether they're going to laugh at us," Eising said.
Eising's experience addressing the issue of exclusion with the event organizer in question turned out positive, as they didn't realize their form had been excluding those that were nonbinary. This interaction began a collaboration between Eising and the organization where he volunteered and collaborated with them to make their events more inclusive.
"It's not always like that, you don't always have those experiences where you're welcome when you bring something forward and so I decided that I wanted to respond to this personal event of mine by creating a guide that kind of laid out that experience, of this sort of mismatch of signals you can experience, and give opportunities for people to understand why that was the case but also provide really hands-on solutions for people that are planning, promoting organizing, orchestrating events to be more gender inclusive."
Thus, the Gender Inclusive Events Guide was created.
The user journey evolves at many levels, says Pivotal Software Senior Director of Product Marketing Dormain Drewitz. "There's a couple of different user journeys that are really happening. You've got user journeys at the developer level, you have user journeys at more of the platform, engineering level, and the teams that are operating and building the platforms, and you have user journeys kind of at the business level and what does that mean for lines of business and their whole relationship to software?"
During a podcast with TNS Founder & EiC Alex Williams at Cloud Foundry Summit Europe, Drewitz discussed not only the user journey, but the evolution of the developer persona itself. In particular, how developers can learn from those that came before them.
Watch on YouTube: https://youtu.be/HeZd6J4TsKc
Part of the transition to DevOps that comes with cloud native application development, has been a shift in responsibility for storage, away from dedicated specialists towards developers who are increasingly responsible for provisioning the storage for the applications they build.
“People do not want storage to be a complicated task,” said Chris Merz, principal technologist at NetApp. “It is a piece of infrastructure. It should be simple, it should be scalable, it should be self healing. They should follow the same patterns as the systems that DevOps practitioners and cloud native architects are building every day.”
Before Kubernetes, building and operating container-based applications was onerous—it involved manually handling tasks like DNS management, load balancing, scaling and resource monitoring. Now the Kubernetes ecosystem handles all of that—but there needs to be a way to get the same level of automation for storage, Merz said.