Author: Alan Shimel

  • DevOps Chat: Cloud-Native Security with Twistlock CEO Ben Bernstein

    DevOps Chat: Cloud-Native Security with Twistlock CEO Ben Bernstein

    The rise of containers and microservices has given rise to a need for a different type of security. Ben Bernstein, CEO of Twistlock, believes cloud-native security is the answer. Fresh off another round of VC funding, Twistlock has big plans to advance cloud-native security in the container space.

    In this DevOps Chat, we talk funding, serverless and cloud-native security with Ben. As usual, the streaming audio is immediately below, followed by the transcript of our conversation.

    Alan Shimel: Hi everyone, it’s Alan Shimel, devopsy.kinsta.cloud, and you’re listening to another DevOps Chat. I’ve got a really exciting chat guest and subject lined up today. I’m happy to be joined by none other than Ben Bernstein. Ben is the CEO founder of Twistlock. Ben, welcome to DevOps Chat.

    Ben Bernstein: Thank you, Alan. I’m really excited to be here. Thanks for inviting me.

    Shimel: Not as excited as I am to have you here. You know, as we were talking off camera, we’ve done other podcasts with Twistlock, but I don’t think we’ve had the pleasure of having you on. It’s a real pleasure. Ben, we’ve got some big news we’re going to break today. Twistlock has raised – is it a round C?

    Bernstein: Absolutely. Yes, round C.

    Shimel: Tell us a little bit about it.

    Bernstein: We’re really excited about it. It’s a $33 million round, which bring us to about $63 million in total money raised. It’s led by Iconic Capital, which is pretty a unique family office that’s probably the largest family office in the world, headed by some of Silicon Valley’s top entrepreneurs, which is a very – something that really made us happy to see that we got the interest of such an awesome funds. So we’re pretty excited about this, and having them join our board. It’s also kind of unique because we sort of reached a growth stage, which is first for me, as a CEO, it’s kind of an interesting to see how the company evolves – sort of the level of maturity we’re starting to hit, which is just exciting. It’s just like seeing your kids go to college or something, I guess. [laughter]

    Shimel: Well, look, my oldest son is leaving Friday for college. I know how that feels, Ben. So $33 million in this round, about $60-something million in total. As we were talking off-mic, I was telling you my experience with raising money. Raising money is never easy per se. When you have a good product, a good company, and the right space, it gets easier maybe, but it’s never totally easy. So congratulations on a sizable round here. It also coincides with a new release for Twistlock. Is that correct?

    Bernstein: Yes, we actually recently released 2.5, which was a pretty interesting release for us, because it updated some of the – or reinforced our investment in Cloud-Native, which is not just container specific, but also augments our complete suite for Cloud-Native computing. So there were some pretty extensive serverless additions there, AWS Fargate addition there as well as some interesting capabilities around forensics, but overall it was a pretty extensive addition to our suite. So we’re very happy about that as well.

    Shimel: So Ben, you mentioned an interesting thing and that is this concept of the whole Cloud-Native space is exploding. We have the Cloud-Native foundation, and all Cloud-Native tools and so forth. Originally, when I heard Cloud-Native, it was very cloud computing, AWS, Azure, that kind of cloud, but with the advent of containerization and Kuernetes and Docker and so forth, it’s really almost I don’t want to say dominated – or synonymous, but it’s so closely linked. From a security point of view though, Ben, where do you see the overlaps, and then where is the difference from Twistlock’s point of view?

    Bernstein: You mean between specifically serverless and –?

    Shimel: Yeah.

    Bernstein: Yeah, so at the end of the day, I think there are two types of application security companies. There are box companies and there are cloud companies. When you think about cloud, it’s basically – it embeds in it the concept that you don’t own the infrastructure. It embeds in it the fact that the people that get the resources get everything in a box. They get the networking. They get the storage. They get everything with a click, whether it’s a public or a private cloud, and it embeds in it the fact that you’re using microsegmentation. It’s about code reuse. It’s about a lot of good things that we all are sort of learning in the past I’d say 8 to 10 years, unless you’ve been working in Google or some of the companies that probably invented this space in house.

    Everything I just said is not about a very specific technology; it’s about specific concepts. These concepts are very disruptive to the way security is being built, and we at Twistlock, believed initially that _____ be the poster child of how existing security cannot protect containers, but when we’ve seen that, it’s not just about containers. It’s about other technologies that are being used by DevOps teams in modern organizations going through so to speak a digital transformation. We decided that we should really expand what we do to go beyond containers pretty early on, and go to really focus on Cloud-Native, which is a suite of technologies, that even includes VMs, but is all about giving or empowering these groups, DevOps groups, to be able to move fast and still secure their work loads.

    This is something that’s hard for them to do with seven different legacy products, where they’re trying to script their way somehow into putting something on the hardware firewall, plus virtual appliance, plus something that needs to – that has a concept of a server, or was built around a concept of a server, where in reality, it should have protected the app, not the server. But anyway, that’s – and so in this – when you think about it in these terms, serverless and containers, and even VMs, if you use them in a certain manner it’s pretty much similar. If it’s immutative, it’s declarative, it’s predictable, a lot of things that really change even the level of security you could wrap around it.

    Shimel: You know, Ben, I also wanted to make the point that so much of this technology is wrapped around the – it’s intrinsically linked with DevOps and a new way culturally of how companies approach not just application development, but specifically application security. I’m wondering – some Twistlock guys, 2.5 guy, your new version out, how does the whole DevSecOps thing movement manifest itself into real features and functionality that we see in the Twistlock suite?

    Bernstein: So when we created Twistlock, we realized that existing security was sold to say seven different people in the company. You take the storage person and sell him storage security. You take the network person and sell him network security. You take the server person and sell him server security where when in fact, everything you were trying to do is to protect your app. Maybe there were other people who you sold different security solutions. What we’ve seen is these five people are actually one person in the Dev Ops area. It’s one person that does a single click and – or several clicks and gets all these good things, but he’s in charge of that because he gets all these things from a single source – the cloud.

    In our bet, which went beyond just specific technologies, and it is kind of counterintuitive to security in general, we said that security had to actually contain multiple layers of security from the same suite. So there’s no point anymore in getting vulnerability assessment from one vendor and east/west firewalls from a different vendor, and anomaly detection from a third vendor, and _____ from a fourth vendor, obviously unless you have a point in it. Most DevOps team, as long as you could – as long as the product is good, they would be happy to get a suite that allows them to get all of these things from a single source.

    That’s one of the bets that we’re taking. It’s a pretty dangerous bet because security has not been that way so far. Luckily for us, it seems to – it seems to be paying off so far. We have hundreds of customers and are doing pretty well.

    Shimel: To say the least. I think you’re being humble. $33 million dollars more in the bank. The usual thing is you’re going to use it for sales or marketing and engineering and support, but specifically what do you – with this kind of rocket fuel in the tank, what we can we look for from Twistlock?

    Bernstein: Well, to be frank, if – I was at the last DockerCon and I saw that people are actually looking for real cloud-native. There’s a real need. If you look at the language, you see that people understand the need for cloud-native security, and what we really want to create is the – a complete solution that people would love and continue to use. So we need to continue to invest in the product. The product is the key. We don’t know how to play golf with executives. We haven’t been very successful at it generally. We really think that what really shines is a good product and a good support team to actually make sure the customers are happy and are using the product right, and that customers are smart, and that they can evaluate things and buy through the channels that they want to use.

    But we’re going to keep doing that, keep trying to make sure that our product is really the most complete solution possible. It gets challenging over time as customers move more workloads into the cloud. They have more demand. We need to excel at doing that, but we’re going to be very focused on making sure our products are – really excels and from that, we believe that given intelligent customers and a supportive team that supports the customer will continue to succeed. So not a lot of huge news there, but just given the demand and given the sophistication of Fortune100 customers, we need to keep – even keeping a product as is requires you to continue and grow just because of the requirements coming from customers over time. We need to do more than just keep the existing product as is. We need to really grow and support new technologies. So anyway, it’s a complex task and we’ll continue at it.

    Shimel: Absolutely. Congratulations, Ben. Over the years, I’ve had a chance to work with many entrepreneurs, VCs, successful business folks. Any one of them will tell you doing what you’ve done here with Twistlock, regardless of where the end game actually winds up playing out at some point, is really something to be proud of. So congratulations to you and John and the rest of the Twistlock team on both the new version as well as the significant new raise.

    As I mentioned to you off-camera, Ben, the time goes so quick where we’re pretty much right on the edge of our time frame here. Wanted to just quickly end up, for people who maybe aren’t as familiar with Twistlock, want to get a little more information, where could they go?

    Bernstein: We have tons of information on our site, Twistlock.com, about use cases, about customers, about cloud-native in general. I encourage people who’d like to learn more to go there.

    Shimel: Fantastic. Well, Ben Bernstein, CEO and founder of Twistlock, thanks for being this episode’s guest on DevOps Chat. Congratulations on all of the good stuff, all of the good news coming out of Twistlock, and continued success.

    Bernstein: Thank you, Alan, for having me. Thanks everyone for listening.

    Shimel: All right, a pleasure. This is Alan Shimel for devopsy.kinsta.cloud. you just heard another DevOps Chat. See you soon, everyone.

    — Alan Shimel

  • DevOps Dozen 2018 – Nominations Are Now Open

    DevOps Dozen 2018 – Nominations Are Now Open

    The DevOps Dozen awards are back and now open for nominations. This fourth annual DevOps Dozen honors the best of the best—the leaders and innovators in the DevOps community. This year’s awards will include 12 categories, with a winner chosen from each. The top four to six nominees in each category will become finalists, who will be selected based upon the number of nominations they received. You can nominate up to two entrants in each category; however, you can make only one nomination per person. In addition, everyone nominating will be required to provide their name and email address; while that won’t thwart any ballot-stuffing, we hope people will be trustworthy during the nomination process. The winners will be selected by our panel of judges.

    Last day to submit your nominations for the DevOps Dozen 2018 awards is Oct 10, 2018. Here’s where to vote: https://www.surveymonkey.com/r/devopsdozen

    Who are the judges? This was tough. We couldn’t have anyone who might be eligible for an award. That disqualifies vendors, practitioners and many others. However, I think we have four great judges:

    1. Alan Shimel, founder and editor in chief, devopsy.kinsta.cloud
    2. George Hulme, longtime tech journalist and editor at devopsy.kinsta.cloud and Security Boulevard
    3. Jayne Groll, CEO and co-founder of the DevOps Institute
    4. Helen Beal, DevOpsologist at Ranger4.

    So what are the dozen categories for the DevOps Dozen this year? That you can get on the site itself, but here they are as well:

    [su_custom_gallery source=”media: 125437,125438,125439,125440,125441,125442,125443,125444,125445,125446,125447,125448,” link=”custom” target=”blank” width=”400″ height=”200″]

    Thank you again for your enthusiastic response to last year’s awards. The full list of 2017 finalists and winners are available to view here.

    There are so many great companies and people involved in DevOps that it’s always difficult to pick the winners. We know some worthy choices will not be voted tops in their category; however, acknowledging them in our awards process helps show how important they are in the DevOps space.

    As stated earlier, the top four to six nominees in each category will be designated as finalists, who then can submit a presentation on why they deserve the award to judges@devops.com. Finalists will be announced the second week of November and the winners, who will be chosen by our panel of judges, will be announced in December.

    If you have questions, send them to DD@devops.com. Voting for finalist nominees is open for three weeks, so don’t waste any time—nominate your favorites today. Good luck to everyone vying to be one of the DevOps Dozen 2018!

    — Alan Shimel

  • DevSecOps: Where DevOps and Security Meet

    DevSecOps: Where DevOps and Security Meet

    Catching up with three IT leaders on the role of security in the changing world of DevOps

    The DevOps methodology as a software and engineering culture goes back nearly 10 years—Patrick Debois coined the term when he named a Belgian software conference “devopsdays.” Since then, the movement has taken on a mind of its own, turning into the go-to strategy for enterprises the world over aiming to accelerate their development timelines and deliver better products faster.

    In the shifts and changes that have happened over the last decade, one has been the idea of “DevSecOps,” or the intersection where security practices and DevOps transformations meet. Recently, at the DevOps Enterprise Summit 2018 (DOES18) event in London, several key players in the DevOps world sat down to take a deep dive into the world of DevSecOps. In the following article, we’ll review some of the key points discussed by Ilkka Turunen, head of Solutions Architecture at Sonatype; Zane Lackey, founder of Signal Sciences; and Margo Cronin, senior solution architect for Amazon Web Services during our panel discussion at DOES18.

    The first point of the discussion centered around the role of security in DevOps, and how the name “DevSecOps” should never make you think security is secondary.

    “I’ve never been crazy about the term DevSecOps, because it’s like ‘Sec’ is an afterthought,” said Turunen. “You know, we were squeezing it in between Dev and Ops, the last kid that got on the bus, and we’re like, go on, just sit in there. For all of us, security is the first priority, the top job—’job zero,’ we sometimes call it. And therefore, for DevOps, it actually understands that security is key, and is the first thing that you do.”

    Turunen pointed to recent changes brought on by GDPR that have made privacy one of the pillars of software development, and how this has brought about further emphasis on security in DevOps transformations. In this new world of GDPR regulations, it’s not limited to just data portability and data breech notifications, but truly goes into “privacy by design.” As such, security is paramount.

    Later, the conversation turned to the idea of how one can create a culture where everyone thinks of themselves as a security practitioner, a seemingly necessary step to having foolproof security practices. The answer lies in creating an organization where security is part of the fundamental culture—a similar cultural change as to what happened around testing.

    “So if you think about testing 10 years ago, it was literally people running from test execution plans, and gradually they changed from that to becoming writers of tests, people that write the automatic-execution, help people, help the floor become more efficient at testing for themselves,” said Turunen. “Teaching them unit testing, all these other frameworks. So I feel like we’re at the brink of a similar kind of change. I think it’s a mixture of both incentives and psychology, and just changing roles.”

    Lackey puts it even more simply—that good engineering just goes hand in hand with good security.

    “The best way I’ve ever seen, like the highest performing organizations view it, is security is a subset of good engineering. In the way that resiliency is, reliability is, quality is, performance is, is a subset of good engineering,” said Lackey.

    Finally, the conversation turned to the role of public cloud service providers and how they can help uplift security for software organizations. For Cronin, the idea of machine learning holds a lot of promise for increasing security.

    “You now have services that can scan your landscape and say do you know these large files contain client identifying data, do you know you have keys there?” said Cronin. “And then you have services where you can then change that behavior automatically. But I think that’s where we’re going to see cloud service providers become a lot more active. You know, using machine learning to harden your production landscape before you actually even go to the security operators.”

    While the world of DevOps is constantly evolving, growth in highly regulated and compliance-oriented industries—coupled with increased global concern over data privacy—have put increased emphasis on incorporating security throughout the software pipeline. To learn more about how these DevOps experts view DevSecOps, and how they are making security a bigger focus in their organizations, you can watch the entire discussion on DevOps TV.

    Bonus: You can also watch Cronin’s DOES18 presentation on “Security Automation at Scale” and Lackey’s presentation on “How You Can Use DevOps to Make You More Secure.”

    And be sure to join us next time at DevOps Enterprise Summit Las Vegas, Oct. 22-24, 2018!

    — Alan Shimel

  • How to Convince Your Manager to Send You to DevOps World | Jenkins World 2018

    How to Convince Your Manager to Send You to DevOps World | Jenkins World 2018

    The largest gathering of Jenkins users and DevOps practitioners is less than a month away. DevOps World | Jenkins World 2018 will be held in two locations this year, Sept. 16-19 in San Francisco and Oct. 22-25 in Nice, France. With exciting keynotes from industry influencers including Dr. Nicole Forsgren, CEO and chief data scientist at DORA, and James Governor, analyst and co-founder of RedMonk, there will be tons of learning and networking opportunities. There will even be a “Westworld” themed party, making it an event you do not want to miss.

    So now that we’ve convinced you to attend, you need to convince your manager why they should send you to DevOps World | Jenkins World 2018. Don’t worry: There are lots of good reasons why attending would be beneficial to you and your company. Once you have successfully convinced your manager to attend DevOps World | Jenkins World, don’t forget to register! To sweeten the deal, you can enter the promotional code just for devopsy.kinsta.cloud readers: JWDEVOPSCUST. That code gets you 20 percent off your registration.

    Keep Learning

    With more than 70 sessions offered in San Francisco and 50 sessions in Nice, all presented by DevOps and Jenkins experts, DevOps World | Jenkins World provides a chance to learn from DevOps leaders. Be sure to emphasize to your manager the importance of learning from the very best in the DevOps community, in training and workshops and, of course, in the breakout sessions. From Jenkins founder Kohsuke Kawaguchi to CloudBees CEO Sacha Labourey and the aforementioned industry influencers, your manager will greatly appreciate the knowledge you bring back to the office from experienced industry experts.

    You should definitely take advantage of some outstanding training opportunities to enhance your continuous delivery, Jenkins and DevOps knowledge. Available training sessions include Jenkins Certification Training, Jenkins Fundamentals, DevOps Leader Certification Training, CloudBees Core Fundamentals, CloudBees Core on Kubernetes and Value Stream Mapping for DevOps. Additionally, you will receive a free Jenkins exam with the purchase of a full conference registration. That is a huge value-add for both your resume and your organization!

    Build Your Network

    DevOps World | Jenkins World brings together thousands of software development experts, thus providing numerous networking opportunities. The conference gives you the opportunity to learn of challenges other organizations in the industry have faced and how they’ve overcome them. If they have already solved a challenge you are just starting to tackle, you could walk away with knowledge that more than pays for the cost of the conference. Conference attendees can also share success stories that may inspire your organization’s next big win. Make it known to your manager that you will be exposed to people like you, who have similar business needs and challenges, whom you will be able to connect with and learn from.

    Invest in Your (and Your Company’s) Future

    As we previously mentioned, with the industry continuing to innovate and evolve, having the skill set to keep up with these changes help make you a valuable asset to your team. When convincing your manager to let you attend, make sure you also present how this knowledge will help push you and your team forward, ultimately propelling your entire organization forward. Highlighting the potential ROI of this opportunity will help your manager better justify the cost to send you to DevOps World | Jenkins World. Detail exactly how much airfare and lodging will cost, but also note what kind of impact it will have on the organization’s bottom line. The ROI will be evident—make that clear!

    We would like to think we have provided some pretty solid justifications for you, but if you still need an extra boost, we have also created an email template to use when sending all this over to your manager for review. Once your boss gives you the green light, go register!

    — Alan Shimel

  • DevOps Chat: The Impact of Automation on DevOps and Society, with Bob Reselman

    DevOps Chat: The Impact of Automation on DevOps and Society, with Bob Reselman

    Those of you who have been reading devopsy.kinsta.cloud for a few years are familiar with the RoelBob cartoons, which have a prominent spot on the home page. RoelBob’s creator, Bob Reselman, is also a technologist and creator of other forms of media. Lately, he’s been writing a series of articles about the impact of automation on society as a whole—not just DevOps.

    Bob is a really smart guy and a great interview, as well. Even if you don’t agree with this thoughts on automation, it’s worth giving what he says a listen.

    As usual, the streaming audio is immediately below, followed by the transcript of our conversation.

    Alan Shimel: Hey, everyone, it’s Alan Shimel, and you’re listening to another DevOps Chat. Got a really great DevOps Chat for y’all today. I’m joined by a good friend of mine, a frequent contributor, one of the team at devopsy.kinsta.cloud—none other than Bob Reselman, creator of the RoelBob cartoons, Bright Ideas TV, the creative force and brains behind Shimmy Tunes, as well as a writer in his own right, not only at devopsy.kinsta.cloud, but at a lot of the leading tech companies out there today.

    So, Bob—welcome!

    Bob Reselman: Oh, thanks for having me, Alan.

    Shimel: You know, I hope I didn’t embarrass you at the log-on, but you know, you’re something of a Renaissance man, right?

    Reselman: [Laughter] Right.

    Shimel: I was reading a little bit of your life history, your life story, Bob.

    Reselman: Oh, yeah. Well, I came to tech late. I came to tech in my early 30s, and the reason I got into it is because somebody told me that I could actually compose music on a computer.

    Shimel: [Laughter]

    Reselman: No, it sounds funny, but if you’re a composer—and I don’t mean—

    Shimel: Like in the MIDI days. I hear you, dude. I know people like that.

    Reselman: Yeah, back in the MIDI days, and you know, if you had a string quartet or even something larger, like an octet, to actually hear that going on, to hear it was very hard. You had to go out and either hire a quartet to play or just be really good at imagining, or be able to sit at a piano and be able to pay some stuff. And I’m not the world’s best pianist, so this medium, this technology really opened up a world to me.

    And then one day I’m sitting around and I’m starting to play with this, and I’m writing it, you know, my string quartet and stuff. I said, “You know, I think I could probably do something with programming.” And so, I did. I actually, I learned to program, and I’m one of those people that came in through the back door. Eventually, I ended up at Gateway, at that time, Gateway 2000, and I—

    Shimel: [Cross talk] cows, we remember it.

    Reselman: Yeah, the cows, yeah. I moved from Boston, Massachusetts to Sioux City, Iowa, which was a complete cultural transformation for me. But every day, I went into the future, this big, big building where we were making computers. I learned a lot, and we can talk about that, too.

    And at Gateway, I was really doing a lot of stuff I shouldn’t have been doing, but I did ‘em, anyway. And I mean that, I just, I sort of had to battle my way into technology. And they were very supportive, and I just learned a lot about some real, hardcore tech, working for that company, and for that, I’m ever grateful.

    And so, that was around ’98. Around 2000, I decided to move on, and I had started doing Big 6 consulting, went into Big 6 consulting. I went into New York and I worked in the financial industry for a while, and then I got good at it. Along the way, back around 1995, I published my first book about DB programming, and Wygant has been very good to me. I still get those royalty checks every month. I can’t complain. That’s how I got here—that’s how I got here, you know? And here I am today.

    Shimel: So, Bob, over the last couple years—I mean, look, we’ve been doing, so, devopsy.kinsta.cloud has been around four years. You’ve probably been doing writing and RoelBob stuff for, what, three years, two and a half years—something like that?

    Reselman: I think three. We’ve been together for a while, Alan. It’s been, you know, the “Casablanca” of technology, what can I say? We’re on the runway, walking into the fog, right? [Laughter]

    Shimel: [Laughter] Round up the usual suspects.

    Reselman: There are no usual suspects. [Laughter]

    Shimel: But Bob, you know, certainly with the advent of DevOps and a heavy emphasis on automation, but also, it’s not all DevOps, it’s the world we live in, as you’re fond of saying.

    Reselman: Mm-hmm, mm-hmm.

    Shimel: You know, automation and the specter of increased automation over the—you know, not only near term, but long term—is really, it’s a scary thing. It’s scary for me as a parent with teenaged boys in terms of what are they gonna do, but it’s scary for a lot of people, people in the workforce today. And it’s something that you have really given a lot of thought to, you’ve written extensively about it, and that’s what I wanna talk to you about today.

    Reselman: Mm-hmm. Well, I’m happy you do, because I do think it’s important, and I think it’s going to have a growing impact. A lot of people—within technology, we can sort of ________. We’re in the middle of it, and we’re pretty adept at adapting—I don’t know if that’s a real term, but we pick up stuff pretty quickly, and we’re good at getting new stuff onto our fingers very quickly.

    But there’s a whole segment of the culture that has problems with it, to be honest. And, you know, let me be direct. Let me be direct, here. My father, he was a cab driver. He was a cab driver, and when I look at what Uber and Lyft are doing to the cab industry in New York City, it’s pretty amazing. I mean, his first medallion, I think, cost him—I’m making these up, I don’t have the actual data, but I think he paid $250,000.00 for his first medallion. And back then, that was a lot of money. But there were only a set amount of taxicabs on the street, and so, there was a high volume, it was a good investment. Today, because of the ride sharing, share services the value of medallions is dropping dramatically. And that’s just one impact of automation.

    Uber and Lyft could not exist without, I wanna say, two fundamental technologies coming on. First of all, credit cards. The other one is GPS, and the third is cell phones. And you mix all three of those together, and anybody can really be a driver. Why? Because you can pick up qualified customers and bill them without having to worry about being paid. GPS will pretty much tell you where to go, and cell phones provide the mapping technology to get there—all of it highly automated.

    Now, what’s interesting to me is that I wonder about the actual Uber and Lyft drivers now as that automation extends. For example, I take Lyft. I take Lyft all the time, and I’m more of a ride sharer than I am a car owner. And I’m sitting in the back of a car, and I had to go to an appointment, and I started reading a book. And I noticed that we were going in the wrong direction. We were going in the wrong direction. I said to the driver, I said, “You know, we really are going in the wrong direction,” and her response was, “Well, this is where the map is telling me to go.”

    Now, what is relevant here is, how far are we really—what is the purpose of that driver, other than to be an interpreter of map data and to manipulate the technology accordingly? And that’s not that far from robotics, and people—

    Shimel: No, it’s not. And actually, I mean, Bob, Uber and Lyft’s end game is to go autonomous, obviously, right?

    Reselman: Right.

    Shimel: And take the driver out of it altogether. But the interesting thing, I’ve had, specifically around Uber and Lyft, but they’re really poster childs for this, right?

    Reselman: Mm-hmm.

    Shimel: When we start thinking about the future of autonomous vehicles, we start thinking about, what really is—what is the disruption in Uber? You mentioned three key technologies, but is Uber really a technology disruption company, or is Uber a company that, what it disrupted was, by taking advantage of all of the excess vehicles and time that drivers have and putting that to good use? And so, was that the true disruption there, or was it the technology that was the disruption, and part and parcel with that technology is the automation?

    Reselman: Right. I think the disruption—it’s the aggregation of the technology which is the disruptor. Now, what is being disrupted? I think there’s a fundamental social disruption going on. The rules of existing as an employee or a wage earner or a value creator in society is changing. And Uber’s talent in terms of transportation—because it’s everywhere, you see everybody getting into those Uber cars. But that’s really inconsequential compared to the larger impacts of transportation.

    So, for example, container shipping is, Swedes Burkett just released a thorough—and again, people can write me and I’ll give them the exact data, because I don’t have it in front of me—but I believe it’s called the Burkett, and that’s a large container ship that’s completely robotic. So, imagine how much containers get shipped on the open seas that have crews. Now, those crews will go away.

    The same as with trucking. Trucking is really low hanging fruit. There are 3,000,000 truck drivers, and Uber is active in the trucking—automated trucking industry. So, they’re looking to automate that, and that’s gonna have a disruption.

    I wrote—the last article I wrote for you all was called “Coming Apart in the Age of Automation,” and the unintended impact here is that we really are creating a bifurcated society in which one class has, can master the technology or becomes the merit class, and the other class is just sort of hanging on. And it’s a sad thing to say, but it is true. And, as we look around current events, we can see that more and more.

    Now, the good news here is that we’re in a—we are in a good position. And what I mean by that is that, if we go back and we look at the history of technology, particularly around the advent of mass production in consumer technology, which is really the automobile. The automobile really was a game changer, because it was intended to be a consumer product once Henry Ford figured out how to do the assembly part. And because it became a consumer product, it really lifted the whole middle class. It became—if you were coming off a farm in Georgia, you could go to Detroit, and without having to learn a whole lot of new skills, become a wage earner in a factory.

    That’s good. Nobody really understood the impact of the internal combustion engine back in 1900 or 1910, that in 100 years, this would have a significant impact. And what I hope we’ve learned along the way is that technology does have an impact, along with sociological and economic. And we can start planning for that accordingly. Sadly, what I’m not hearing is that planning. People hear—the argument is, technology, yes, will always displace people. There are no more people picking up the horse dung on the streets of New York. Those people went to work in factories, et cetera, et cetera. In other words, technology destroys jobs, but it creates more jobs.

    But we’re not hearing any sort of ancillary planning of what the downside might look like, and if there is a downside—which there might very well be—how we’re going to address that.

    Shimel: Yep. I—you know, Bob, maybe I’m cynical in my old age. [Laughter] I—unfortunately, planning is not our long suit, right? We live in a financial world where we live quarter to quarter, week by week, you know? A bad quarter can cost a CEO their job and lose trillions or billions—not trillions, but billions of dollars of market capitalization.

    Reselman: Mm-hmm.

    Shimel: The fact of the matter is, if you believe the media, most people in our age group, Bob, have not put away enough money for retirement.

    Reselman: Mm-hmm, mm-hmm.

    Shimel: We don’t believe in science or truth, [Laughter] and so we can’t even plan around what to do about climate change. Why should this be any different?

    Reselman: Well, I don’t know if I agree with your assessment completely.

    Shimel: Okay.

    Reselman: Because I just got through reading a book by Harari about, it’s an assessment of current conditions and future. And people forget that famine and people dying of starvation even 50 to 60 years ago was a common day event. A lot of people in China starved to death. That really did happen. People in Ireland, in 1840 when the potato famine came along, they starved to death. You didn’t have enough food, and you died. Death due to starvation is still around, but it’s not commonplace—nowhere near the condition that it used to be.

    The other thing is, when we look at warfare—yes, there are wars going on and there are mutual wars, but there hasn’t been a war on the scale of World War II since World War II. So, there’s stuff going on that sorta gets hidden behind all the—what would we say—the fascination with the bad stuff.

    The other thing to think about in terms of us as technologists is that planning is still part of the industrial fabric. What do I mean by that? It takes five years to design and manufacture a car. I learned this when I worked at Edmonds. Pretty much, if you start looking at model years, the big model changes are in the fifth year. Pretty much, if you came out with a Car A—in year one, you’ll have A, then year two, what used to be options become standard and then more options become standard. And then, by year five, you have enough research in place and enough retooling of factories in place to create a new vehicle and put it on the market itself.

    So, industry does have the ability to plan. I mean, just look—I mean, if we look at SpaceX, bringing that rocket back and just being able to send a rocket up, you know, one of those cylinder rockets, right, that you used to imagine from the ‘50s goes up? And we used to just blow ‘em up and leave them in space. Now, we can actually bring them down and allow that piece of pipe with rocket fuel in it to land safely on land. That’s pretty amazing. You can’t plan that in three months. That takes years and years and years of planning.

    So, we have the ability to plan. The question is, in terms of our social imperatives, and that becomes a real question. So, why—what’s stopping people from saving? Why are people afraid? Why is fear so high now? And then also, going back to jobs as, we’ll call them no-skill jobs, start being eliminated from the landscape because grunt work is always the easiest to replace; thinking work is harder. Then, what do we do about that?

    And there are people out there offering solutions, but they are pretty dramatic, and there’s two, and they’re dramatic, and to even start contemplating that really requires a lot of courage.

    The first one is, is that there’s a good case to be made that we are at the end of the consumer based economy. Again, let’s go back to Ford. You know, an automobile for everybody changed everything. And when you look at it, you know, how many cars can Bill Gates drive? Well, if indeed, he had 365 cars in his garage, he could drive a different one every day. The fact is, he probably doesn’t, and he probably takes an Uber. So, really, in the future, you know, we’re all gonna be sharing cars.

    So, this notion of ________, and I didn’t do a good job explaining it. In other words, what I’m saying is that, for a lot of people, having devices and technology is what makes the economy run. Everybody needs a cell phone. Having mass distribution of cell phones makes the economy run. Having mass distribution of food makes the economy run. Mass distribution, mass distribution, mass distribution.

    Well, at some point now, what’s happening is, we can produce as much as we like. Production is no longer a problem. Two hundred years ago, production was a problem. The factories couldn’t make the stuff fast enough. Now, the factories can. So, now we have infinite production, which means we have infinite consumption, which means we have a problem with too much plastic in the water, and too much carbon monoxide in the air.

    Shimel: Bob, I’m gonna butt in here, if you don’t mind.

    Reselman: Okay.

    Shimel: So, I just got back from China last month.

    Reselman: Okay.

    Shimel: There’s a real problem there, right? Because this is—they’re living it, right? And, you know, we look at the world’s steel market and tariffs and all that stuff, a lot of it is being driven by—China has built over capacity in terms of what they can actually use and even sell at a decent margin in terms of steel.

    Reselman: Mm-hmm.

    Shimel: But not just steel, they are producing solar panels, cellular phones. They just—in other words, they are the kings of this, “Hey, we’ll produce as much as we possibly can produce because we’re gonna, if we’re not gonna consume it, we’re gonna sell it in the world market, and if we can’t make a profit on it, well, we’re not capitalists, anyway, right?”

    But an interesting dichotomy that I saw there was that they still are manually labor intensive in certain things. So, their streets are pretty clean in the cities, and the streets are clean because, on every street, there’s a cadre of people walking around with bamboo poles and palm fronds, kinda thing—literally sweeping the streets. And they sweep it into a pile and then some other person comes by and they have all these uniforms. And it comes by on a machine, like a Zamboni machine excepts it a vacuum, and sucks up what that people sweep.

    Reselman: Mm-hmm.

    Shimel: It’s almost like busy work to me, but what was fascinating to me is that, on one end, I took the bullet train from Shanghai to Beijing, right, and 300 and something kilometers an hour. And all I could see out the window, Bob, were endless cranes and towers going up, right? Not just a building, but cities and towns being built one after the next, and all built around factories. They’re like old factory towns, they kinda looked like, right?

    Reselman: Mm-hmm, mm-hmm.

    Shimel: So, they got the infinite capacity to build things, but I really question the infinite capacity to pay for things, to consume these things.

    Reselman: Right. Well, you hit it on the head. It’s the notion of payment. That’s sort of like, it’s like an assumption that we might have to start questioning, which leads into the second point that I was gonna bring up. You read my mind, Alan—and do my a favor, when you’re reading my mind, please clean up after yourself.

    Shimel: [Laughter] Okay.

    Reselman: Right, so the first point is, we have to start examining the role of consumption as a driver of an economy. We just gotta start looking at that. That’s a big question with incredible ramifications.

    The second one becomes this notion of paying for stuff in order to get what you want. And to—let me share a real life funny. My wife has decided that she needs—she wants to get rid of a chair we never use. It’s a nice leather chair that we never, ever use, and we paid, I think, $600—whatever it was, it was too much. I’m not a decorator, but she paid it, and now she’s saying, “I wanna sell it for $200.”

    And so, she puts the ad out on Craigslist and nobody’s biting, nobody’s biting. Why isn’t anybody biting? Because my suspicion is, it’s a good price for a $600 chair, but they can get ‘em for free. They can get probably an equal chair for free. And, if you look at the cell phone, I mean, we’re giving away cell phones. We’re giving it all away, we really are.

    And so, this notion of, what you’re saying is, how are people gonna pay for it? Probably they’re not. Either one of two things are gonna happen. Either the buildings are gonna be left unoccupied and it’s gonna be, there’s a downward recession—or the alternative is to blast credit into the economy to create money and to have that money become a purchasing agent. Is there wealth created? Is there value created? I don’t know about that. I don’t know about that. But are there transactions created? Yes.

    So, I’m being long-winded by saying that it might be coming time to start looking at a serious examination of universal basic income. And let’s just sprinkle the fairy dust for a moment, and let’s sprinkle the fairy dust and say that we’ve just—everything is great, everybody’s just calmed down. They understand that automation is great and if we let machines have their way, the machines can do just about everything now. And every week, you know, you get a check in the mail that allows you to go down to the grocery store or, better yet, interact with Amazon Prime, and the drone shows up with your food. And you go to your TV set and there’s your streaming TV. And some people decide they wanna be philosophers ________, so there are brain surgeons, and other people just decide they wanna sit around and play video games all day.

    There’s our future, right? Is that so bad? Is that so bad? And people say, “Well, how will we innovate? How will we go forward?” And my question—and I don’t have an answer for this—is, I wonder if somebody who gets into something like brain surgery for the money or curing disease for the money? Maybe the recognition, we don’t know. But the notion of universal basic income, if you take away the moral reservations about—what would they call it? The moral risk, right, becomes buyable.

    The sad thing is, is that any—the experiments that are being ________ aren’t real world. And what do I mean by that? They tried in Canada to ________. And I forget the details; I’ll mail it to your listeners if they want it. They’re running UBI on $1,000 a month. The test group got $1,000 a month. Well, gee, I mean, can you really live on $1,000 a month? That’s one thing. Whereas, if you go to another country that has universal basic income, and the poster child is Cyprus. Cyprus gives every citizen 500 Euros a month. The reason it’s relevant here is that a rent of an apartment in Cyprus is only 520 Euros a month. So, 500 Euros a month becomes, between—with two people, 1,000 Euros a month becomes a viable amount and a reasonable standard of living.

    That’s where UBI needs to be. We need to be starting to talk about UBI numbers in the area of $40,000, $50,000, $60,000 a year per family, and then we have to deal with the ramifications. And the ramifications really aren’t so much economic as they are social. What happens when you move the social structures that work bonds? In other words, what happens when a whole society no longer has to get up in the morning and go to work? What happens then?

    And that becomes the danger point, because most people have no idea.

    Shimel: Huh. Excellent. I think—yeah. I don’t disagree with you, there.

    Reselman: Well, again, I’m not looking for conflict or disagreement. This is a great discussion, but for our listeners out there, the point is—we are in technology. We are the people that write the scripts. There are other people that do the automation. We are the people that are making the robots. We’re doing all this. And we’re in a good position now, because unlike Henry Ford, who really didn’t think it through with regard to what an automobile would do over a period of 100 years, whereas one of the engineers at Sony did in terms of television. A friend of mine’s wife’s father worked at Sony, and he raised a question to one of his engineers back in—I think it was in the ‘80s. And he said, “You know, we’re selling a lot of Trinitrons. What are we gonna do when these all come back?” At least he posed the question.

    So, if anything, for the listeners out there that I hope they consider is, what do we do when we’ve become very good at all this? What do we do when we’ve created a framework and a fabric of automation where—and labor almost becomes unnecessary? What do we do, then? And what are the ideas behind that? And that’s where I wish there was more conversation, at the least. And not be on, “There will always be more jobs” or the fantastic stuff, but real, concrete, well researched conversation.

    Shimel: Excellent. Bob, I’d love to continue this conversation, but we are so way over our time. [Laughter]

    Reselman: Oh, I’m sorry, I’m sorry.

    Shimel: That’s okay! We’re gonna need to pick it up on another DevOps Chat.

    Reselman: Okay.

    Shimel: Which is great. I bet next month, we’ll do it again.

    Reselman: Sure, sure. Yeah. I’ll do that. I’ll make the coffee. The dog’s been very good here, he’s been very quiet. He understands that he’s being recorded, so.

    Shimel: Otherwise we’ll automate him out of a job. [Laughter]

    Reselman: Yeah. [Laughter]

    Shimel: Anyway, Bob Reselman—RoelBob, author, futurist, commenting on the state of the world today—thanks for being our guest on this DevOps Chat. We’ll continue this conversation on another DevOps Chat soon, but for now, this is Alan Shimel, and you’ve just listened to a DevOps Chat. Have a great day, everyone.

    — Alan Shimel

  • DevOps Chat: Modern Applications with SignalFx CEO Karthik Rau

    DevOps Chat: Modern Applications with SignalFx CEO Karthik Rau

    Monitoring has come a long way since the days of 2 a.m. alerts, with automation and analytics now integrated in—and integral to—the life cycle of modern applications. It’s a topic Karthik Rau, CEO of SignalFx, knows well, and one we discuss in this latest DevOps Chat.

    In its three years of selling, SignalFx has grown a whopping 300 percent year over year—an astounding number, even for a startup.

    As usual, the streaming audio is immediately below, followed by the transcript of our conversation.

    Alan Shimel: Hi, everyone, it’s Alan Shimel and you’re listening to another DevOps Chat. Today’s DevOps Chat features Karthik Rau, CEO of SignalFx. Karthik, welcome to DevOps Chat.

    Karthik Rau: Thanks, Alan. It’s great to talk to you again.

    Shimel: Always a pleasure to have you on. So, Karthik, let’s just do a little setting the base here, baseline setting. And I’m gonna assume most of our listeners have at least heard of SignalFx, but maybe some haven’t and maybe some have heard it but they’re not sure exactly of who SignalFx is. Why don’t we start there?

    Rau: Sure, Alan. SignalFx is a monitoring and operational intelligence solution for the developers and operators of cloud-native applications. Our founding team, my cofounder and our original engineering team, all came out of Facebook and were responsible for building the monitoring systems at Facebook, back when they had a “move fast and break things” culture, which today everyone calls DevOps, but, back then, they didn’t really have a term for it. So, at a high level, what we do different from everyone else is we are focused very heavily on the analytics part of the monitoring problem. We collect data – time series, telemetry data – across the customer’s entire environment, from the hardware to the middleware to the application, all the way up even through the API layer, and we apply real-time statistical models around that data to identify patterns that are unusual and different, and alert on those trends proactively so that customers can get ahead of issues and be more proactive in their monitoring, rather than reacting to a bunch of noisy alerts.

    So our customers are able to, No. 1, get a much better handle of their distributed cloud-native application architectures, understanding the patterns, what’s happening. They’re able to detect issues as they emerge, which is very important in today’s environments because most people are pushing changes out a lot more aggressively, and so you wanna detect changes immediately, rather than wait and discover stuff after you’ve made a number of changes. And it’s particularly important for today’s application architectures where you’ve got a lot of bursty workloads, like with containers, where you’re spinning up and spinning down capacity in minutes and you really need your monitoring systems to be (a) real-time and discover components immediately and then (b) be a lot more sophisticated in finding issues as they happen.

    Shimel: Excellent. And, Karthik, you know, I should also mention that, in terms of UI, SignalFx is one of the best UIs, web-based UIs that I’ve ever seen. And I’ve looked at a lot of applications, a lot of programs, over the year – over the years. Year? I wish it was “year.” And, you know, so – and I’ve told you this before. I’m just think whoever designs the interfaces there is a rockstar, so just mention that, but –

    Rau: Yeah. Thank you.

    Shimel: You know, we spoke a little bit off-mic, Karthik, and we were going over what are some of the new metrics coming out of SignalFx, how business is going, and you mentioned some really eye-popping numbers, right? First of all, you guys are showing something like 300 percent year-over-year growth for the last couple years, which is – you know, everyone will say, “It’s a startup; they’re supposed to grow like that,” but, dude, until you’ve done it, you haven’t done it, so that’s an astounding number. But also a big move into large enterprises. Is that correct?

    Rau: Yeah. So, yes, absolutely. So we’ve been, as you’ve mentioned, tripling our business year over year, since we – over the past year, but significant growth even above that in the early years. We’ve only been selling for about three years. Our customer base is focused quite a bit on mid- to larger-size companies, so we’ve always been focused on larger accounts, whether that’s the web-scale players, who are operating large-scale applications with four or five nines availability requirements, but also a lot of the enterprise accounts, who what we’ve been really excited about is they’re really moved wholesale into cloud and cloud-native application architectures. And we’ve seen that trend accelerate over the last two or three years, so that’s been a large area of success for us. You know, we’ve got Fortune 500 customers across many verticals – media, retail, financial services, industrials, transportation – so we’re definitely seeing that trend accelerate across the enterprise, not just in a handful of verticals.

    Shimel: Absolutely. But, Karthik, what about for the person out here listening to this, right? And he says, “Wow, that sounds great. I love what Karthik says they’re doing and the Facebook kinda background and all of this great stuff, but I’m not a unicorn. I’m not even a large enterprise.”

    Rau: Well, I think that everyone today is trying to build software quickly, right? Gone are the days where you have a three-year development cycle and you release software and hope you get it right. It’s just not gonna work in today’s world of web services and your competition are tech companies that are moving at lightning speed. So the issue isn’t really – the world is changing. The way people are building and releasing and managing software is fundamentally different.

    And what SignalFx does, the analytics around SignalFx, you can look at it in two ways. One way is, yes, if you’re a large environment, you absolutely have to have it to reduce noise, but another way of looking at it is you could be a small environment and you wanna have a more predictive way of discovering issues, as they emerge, so that you too can move fast without breaking things, right?

    And if you look at it that way, having the kinds of capabilities that SignalFx provides are critical, even if you’re a department within a big company or you’re a startup with 50 people or 20 people. You still wanna be able to do the proactive analysis of, “Hey, this code push that I just rolled out, a canary release, is unusual relative to the rest of my application. And maybe that’s indicative of a problem with my code and I wanna roll it back before rolling it out across all of my users.” Right? You don’t have to be Facebook-sized or Google-sized to have that problem. You’re just building a modern application.

    So that’s why we do have customers across segments. I mean, our focus is certainly on the larger accounts, but we’ve got a lot of departmental deals within enterprises. We’ve got a lot of startups that are also using us, who care about having a more predictive approach to monitoring.

    Shimel: Yeah, no, you know, I think the key there – and you mentioned the word, Karthik, and it’s funny; it’s a word I’ve been hearing over and over again. And that this term of the “modern application.” I don’t care whether you’re big, small or Goldilocks. The modern application, as we call it, right, demands certain things, and one of them is obviously monitoring, but also modern applications demand automation, real-time type of data flows and insight. And it’s not just the guys who develop once every few years – that certainly is not a modern application – but it’s also more than just how frequently you update your code. I think the modern application, you know, what goes are in, the kind of stuff, or at least one element of it is the kind of stuff you’re talking about with SignalFx. Right? These go like hand in glove.

    Rau: Yeah. Absolutely.

    Shimel: So I think that’s – so, to me, more than size of company. I mean, that’s almost a determining factor. Another item I just wanted to mention on the – or bring up on SignalFx itself, as a company, is you guys recently announced a rather large round of funding as well.

    Rau: That’s right, Alan. On the backs of all of our success, we continue to build out our product and continue to accelerate our go to market. We just closed a $45-million Series D round in May and we’ll be using that to continue our investment in R&D. We’re continuing to expand globally. I think I’d mentioned to you offline here that we’ve just expanded into Europe. We also recently expanded into Australia. We’ll continue our expansion geographically, so, hopefully, a lot more people across the seas will hear about us and see us, in the coming quarters.

    Shimel: No doubt in my mind about it, Karthik. I can tell you, from – when I look at devopsy.kinsta.cloud’s demographics and metrics and analytics, it blows me away that only about 36, 35 percent of our audience these days are U.S.-based.

    Rau: Mm-hmm.

    Shimel: About 31, 32 are based in Europe. 15 percent in India. Australia is probably the fourth or fifth largest country, for instance, for our readers. So –

    Rau: Yeah, that’s right.

    Shimel: – you know, the thing about this market is it’s truly, truly a worldwide market. And I know, Karthik, if you’ve had the chance to go to China recently, but I was there for Interop China last month, talking about DevSecOps, and I will tell you that the DevOps market in China is exploding. I mean, just there’s a lot of people there, obviously, as there are in India, but DevOps is really catching fire.

    And, as you and I were talking about offline, Karthik, it’s one thing if you’re chasing that crowd or you’re chasing that wave. In the case of SignalFx, it’s a beautiful thing, where, maybe when you did launch, you were a little out ahead of the market, a little out ahead of the state of art, but they’re catching up to you now, right? They’re coming. And it’s good to be there, waiting for them.

    Rau: Yeah, absolutely. The market – what’s been most interesting about – you know, at SignalFx the last several years, has been, when we launched the company three years ago, our – what we did that was so different from everyone else is we had this real-time streaming analysis engine, streaming analytics engine, that could apply these sophisticated models within seconds across large data sets and help you be a lot more predictive in identifying issues. And no one else was doing it that way and still no one else is doing it that way. And, at the time, people would ask us questions of like, “Well, what does it really matter if you can do things in seconds versus minutes? ‘Cause the human attention span is only minutes and if you wake up in the middle of the night, it might take you minutes to go and deal with an alert.”

    Well, that was kind of in the old days. Now what’s happening is there’s so much more automation happening across the entire operations landscape. I mean, people talk about it as infrastructure as code, right? You basically automate the entire end-to-end process as much as you can. And, more and more, there are these frameworks that enable greater automation, like Kubernetes, and what we’re finding now is people are really recognizing that, “Maybe we don’t need roomfuls of NAC engineers waiting to find a yellow light or a red light to then go and manually invoke a script from a run book, if we can just automate it.”

    Well, guess what? If you’re gonna automate a remediation like that, garbage in, garbage out. You need quality in. You need to have quality signals. You need to be able to untease signal from noise and you need to be able to do it quickly. And if you can do it quickly, then you can automate quickly and you don’t – the whole notion of having a human wake up and spend minutes orienting themselves goes out the door ’cause you can just – or having the roomful of NAC people responding to it goes out the door. You can just automate it. And then the capabilities of SignalFx then are very unique and very critical to enabling you to drive this end-to-end automation.

    And what we’re finding is now more and more of our customers and marketplaces recognizing this, as they’re embarking down this path of leveraging microservices and automation around microservices and infrastructure as code. Having a system like SignalFx, with its real-time analytics, is absolutely critical. So it’s been fascinating to see that evolve over the last few years.

    Shimel: Yeah. No, for sure. You know, Karthik, it was interesting. I saw an interesting metric today. Something – I forgot who it came out of – Gartner or someone. Within two years, something like two-thirds of cloud deployments will be container-based, which kinda blew me away, to tell you the truth. Have you heard anything like that?

    Rau: I mean, that’s an incredible metric. I mean, I would say we’re certainly seeing a tremendous amount of interest in containers. Well, it’s gone from interest to actual deployments, right? So, two years ago, there was a tremendous amount of interest in it. Nowadays, I would say that is the de facto new architecture, so I think the keyword there is “new,” right? So two-thirds of new deployments, I totally believe that, that that will be the case, 100 percent.

    Shimel: Crazy. I mean, we talk about internet time and the time crunch and it seems to be accelerating like global warming is and climate change is, but the idea that we’d see that kind of number in that kind of time just kinda blows me away. So, Karthik, we spent a bunch of time with this stuff, going over the SignalFx, a little bit about the market, right? Let’s take a look at a crystal ball and gaze into where do you see SignalFx, let’s say, going over the next, let’s say, 18 tp 24 months?

    Rau: Well, we continue to invest across our business, right? So our focus right now is we believe there’s a giant problem that needs to be solved in the industry, which is, “How do you get better visibility and monitoring around the new stack? And then, beyond that, how do you get better visibility into how your operations are impacting your business?” So, as I mentioned at the top of this podcast, we think of ourselves as monitoring and operational intelligence for modern applications, so one of the things that we – we see all our customers go through a similar progression, where you’ll start doing the infrastructure monitoring for this new world, where you gotta look at the entire microservice, versus an individual node, and you start to get into application and look at application performance issues.

    But then, very quickly, customers typically start to look at how are all of these metrics affecting their business, right? You know, “How many of my partners are making API calls in my services? And who are my most expensive partners and my least expensive partners?” Or, if you’re a SaaS vendor and you wanted to do a gross-margin analysis by customer, all of the data already exists in your monitoring system, and we see more and more of our customers extending the use of these systems to answer broader questions around operational intelligence.

    So that’s kind of – those are the three sort of key pillars of what you use a system like a SignalFx for, right? It’s infrastructure monitoring, it’s application monitoring, and then it’s operational intelligence. So our plans, as a company, are really focused around those three pillars. You need to invest in product to support all of the use cases around those three areas. And then continuing to invest in our sales and marketing team so that more and more companies out there can benefit from what we have to offer. So that’s our focus over the next 18 to 24 months.

    Shimel: Fantastic. And, as we spoke about earlier, it’s nice to be out in front of the market, but, Karthik, your job, as the CEO, if you choose to accept this mission impossible, is how do you stay out front of it? You’re right? How do you know – how do you – I mean, you think containers are gonna be dominant, right, so you wanna put that cloud-native dominant. What do you think is sort of next big things coming out there?

    Rau: Well, in our space, I think the most fascinating new set of technology is around service mesh. You know, as more and more of the world moves toward leveraging containers and orchestration frameworks like Kubernetes, the service mesh is gonna be a really interesting way of automatically getting visibility into all of the flows between all of these different microservices, having a control plane to operate against all these microservices. And it’s still relatively young. It’s still in its infancy, but there’s a lot of great stuff happening there, you know, what you see Lyft doing with Envoy and Istio and LinkerD. There’s just a lot of really interesting stuff happening there.

    And the theme here is, as developers own more and more of running their applications and the runtime, what you’ll find is more and more of the stuff that used to be this black-box, proprietary thing that vendors would come in and do in the runtime are just becoming available as a part of the core services. So, in the case of service mesh, a lot of the instrumentation of metrics and traces and monitoring data is just you’re gonna be able to get it by virtue of running in a Kubernetes-style environment and you’re not gonna need these expensive, proprietary agents to come in and collect that data for you.

    So that’s great for customers. It creates a standardized mechanism of data collection and it provides a lot of automatic instrumentation, which is great for customers. Of course, then that just begs the next question, “Well, what are you gonna do with all that data?” So we’re focused on ingesting more and more of these new types of data from these new frameworks and making it even more – the more data we get, the more powerful and rich the context we can provide around our alerts and algorithms and dashboards, so we’re really excited to see that trend continue.

    Shimel: Very cool. Karthik, we’re about out of time. We’re probably over time here. I apologize for keeping you on so long. But, hey, man, you guys are kicking butt and taking names, and congratulations. For anyone listening out there who hears Karthik talk about growing 300 percent at SignalFx year over year and raising $45 million and it sounds like, “Well, la dee dah,” I’ve been there and I can tell you it’s not easy. So congratulations. Keep up the great work and we’d love to check back in –

    Rau: Thank you, Alan.

    Shimel: Let’s not wait a year to check back in with SignalFx. Let’s have you on here sooner than later.

    Rau: Absolutely. Let’s do it again soon, Alan. Sounds good.

    Shimel: Karthik Rau, CEO, cofounder of SignalFx, our guest here on DevOps Chat. You’ve just listened to another DevOps Chat. Have a great day, everyone.

    — Alan Shimel

  • DevOps Chat: CI/CD with CircleCI’s Rob Zuber

    DevOps Chat: CI/CD with CircleCI’s Rob Zuber

    Microsoft’s recent acquisition of GitHub has spurred a lot of conversations regarding which company is the next big acquisition target, and here on DevOps Chat is no exception. In this episode of DevOps Chat, I speak with Rob Zuber, CTO of CircleCI about the CI/CD space, the future of the market and, yes, M&A activity in the DevOps space.

    As usual, the streaming audio is immediately below, followed by the transcript of our conversation.

    Alan Shimel: Hey, everyone, it’s Alan Shimel, devopsy.kinsta.cloud, and you’re listening to another DevOps Chat. Today’s DevOps Chat features Rob Zuber, CTO, CircleCI. Rob, welcome to DevOps Chat.

    Rob Zuber: Thanks. Good morning.

    Shimel: Good morning.

    Zuber: It’s a pleasure to be here.

    Shimel: Or afternoon, in my case, or evening. Who knows when people are listening to this? But, Rob, thanks for being our guest. I think this is the first time we’ve had anyone from CircleCI on a DevOps Chat here. So, you know, you are a mold-breaker and thanks very much.

    Zuber: I’m excited.

    Shimel: All right. So, Rob, our audience tends to be pretty DevOps-y, and so I’m assuming they know of CircleCI or at least have heard of CircleCI, but maybe they haven’t. So, in case they haven’t, Rob, give us a little background, just a real quick elevator, on CircleCI.

    Zuber: Yeah. So we’re a big part of the delivery pipeline for many software organizations. We offer continuous integration and continuous deployment, both as a cloud offering so that you don’t have to manage any of it yourself, but, if you’re interested in doing that, we also have a server-hosted version. And, you know, our objective is to help people focus on their business and get their software into market faster, taking out of the way the overhead of managing a lot of the tooling around doing that.

    Shimel: Yep. And, Rob, just in way of history and background and setting the table here, CircleCI really is – it was kind of a cloud-native CI/CD solution originally and it’s only relatively recently that you started having sort of an on-prem solution as well, offered as an option. So it’s kind of opposite of the usual SaaS migration, if you will, right, where people turn on-prem stuff into SaaS solutions. You were kind of a SssS solution and now offer an on-prem option.

    Zuber: Yeah, that’s exactly right. And that’s probably partly a function of when the company was started, so CircleCI launched in 2012. At that point, people were pretty comfortable with cloud offerings. GitHub had been around for a little while, so people were used to having the source code in someone else’s servers, and so we were able to leverage that a little bit. And we were able to grow quite effectively off of that base, but we did reach a point where there were very large customers with very specific needs, where it made a little more sense for them to run the software themselves and be able to have a little bit more opportunity to customize the environment in which it was being run, etc.

    One thing that’s interesting about that – and you talk about the difference in which way you go across that transition – because we built a multi-tenant platform from the beginning and really focused on our ability to operate that on behalf of other people, we find that, even in an on-prem solution, especially for very large organizations, we have a lot of the capability around that management at scale and centralized management that doesn’t – that still gives freedom to the individual developers to do their work. So it is actually quite interesting, how the genesis of the product affects how it operates in those multiple environments long-term.

    Shimel: Absolutely. Rob, another area – and I didn’t really talk to you off mic about this, but another area I wanted to explore was, historically, was CircleCI originally just CI or was it always CI/CD?

    Zuber: I think you could kind of look at that two ways. I mean, there was CD pretty early in the product, at least for some particular cases, but, if you look at the evolution of the software industry, many more people were doing CI in 2012 than CD. I mean, it was sort of this slow transition of people getting to, you know, “First, we’re gonna figure out Agile process and just how we do our actual software development. And then we’re gonna add CI on top of that. And then we’re gonna add CD.”

    So we always had some CD capabilities, but the number of our customers or the percentage or breakdown of our customers using CD has grown pretty significantly over that time, and I think that’s partly an effect of the kinds of tooling we’re offering, partly a shift in what CD even means, and then partly just growth in the market and comfort level of people doing that, right? Of – especially – and CD, of course, is always challenging ’cause some people are talking about continuous delivery and some about continuous deployment, but, in particular, on the continuous deployment side, other things had to come into play – you know, feature flagging, canaries, just better control of what it meant to actually put something in production. And so the comfort level and increase in that has led to more people using our platform for CD as well.

    Shimel: Absolutely. You know, as an observer of the space, sort of the market, I’d seen it come – when I first launched devopsy.kinsta.cloud, four years ago, Rob, there was this clear sort of distinction between “We’re not CD. CD is something else. We’re CI,” or reversed – “Those folks are just CI. They’re not CD.” And it kinda just seemed like an artificial wall had been built, right? Not to get all political.

    But – and so I, for one, am happy to see sort of that wall being torn down and the natural flow of the software development life cycle, of the modern software factory, if you will, taking place, where CI kinda naturally flows into CD. And I think the next thing we’re seeing is this natural connection to what Gartner and some of the others call “ARA.” Right? Which I don’t even know what the difference between that and CD is, but I don’t know. What do you think?

    Zuber: Well, I think that, overall, this evolution, as I was saying, it always takes a long time for people to get – or, let’s say, for everyone to get comfortable with each of these stages of the evolution. And we’re always looking to the next frontier, right? So, at one end of the spectrum, you have those early adopters, who, in 2012, were doing CD or before that. I’m trying to think of the original sort of posts around CD that I think came out of, I wanna say, Etsy, but I don’t know if that’s actually true or me projecting kind of them as a pillar of this type of thinking. But, you know – and we’re still at a point where some people are just getting comfortable with and adopting it, so the spectrum is really broad, from early adopters to sort of overall mass adoption.

    And the early adopters have moved on to, probably, things that I haven’t even thought about, and so we’re always seeing that and it’s nice to have people try those things and, in some cases, fail, and, in some cases, discover really new and interesting ways of approaching stuff. And it takes – it definitely takes a little bit of a mindset of “I’m just willing to try this. I’m willing to take some risk and do new things,” and the people that do those create opportunities for the rest of us to learn from, the things that go well and the things that go horribly wrong.

    And so it’s one of the reasons that I just love being in the space in general, is just the constant kind of desire to do things better and find new opportunities, of course, with a good balance towards actually focusing on getting stuff done, but there’s just such a creativity and desire around improving, in any way we can, this process and how we get stuff out and how we build it reliably and work efficiently.

    Shimel: Absolutely. So, Rob, let’s turn a little bit to – we’ve done a nice history. Let’s look a little bit to the future now, though.

    Zuber: Mm-hmm.

    Shimel: Talk to me – what did – how – you’re the CTO. You kinda have a lot of the vision for CircleCI. Where do you see CircleCI and the market in general going?

    Zuber: Yeah. Well, that’s a great question. I think a lot of people’s perspectives of this market was changed a little bit in the last week or so, with news around Microsoft and GitHub and just the value that people are starting to recognize in developers, the happiness of developers, the efficiency, the value that they place on the tools that they use. So, for the market overall, I think we’re just a really exciting time, where we talked about this – or I talked about this creativity and passion to do things better, but we’re at a sort of inflection point where there’s a really, really high-level recognition of the value of that.

    I would say there’s been a significant shift in the mentality of many companies. And we talk a lot about how every company is becoming a software company, in that, even if you’re an airline, your biggest issue, when you ground your planes for a day, is that you have some software glitch somewhere, right? You know, multinational trading markets are shutting down on software issues. So the impact and value of software is becoming really, really visible and, as a result, there’s a shift in mentality about how we build software, from “This is a cost center that I just have to manage down,” to, “This is the core of my business and I need to be really investing and doing this in the best possible way.”

    And so that’s obviously exciting for us. And one of the things that’s really interesting for us, as we look forward, is that we – we’ve had the fortune of some success and growing and, to the best of our knowledge, run the largest or one of the largest build platforms on the planet. As a result, we know a lot about how people are building software, and so we’re investing a lot of our time and energy in figuring out how to use that to then help those people, meaning, if you’re building on CircleCI, you don’t just get an understanding of your particular code change that you just made, but you can get an understanding of how your team is doing, how your whole process is doing, how effective you are, relative to other teams out there.

    And I think that’s a place where we have a lot of opportunity to really add additional value for our customers, in not just, again, direct feedback on this one thing that you did today, but really helping understand your process, maybe where things aren’t working well, maybe where you have some opportunities to improve. We’re all in this, trying to be better every day. And if we can help customers at that at a higher level, that’s really exciting for us.

    Shimel: Yep. You know, it’s interesting you brought up the GitHub thing and to justify all this. And so I have some views on it. What a surprise. But, you know, Rob, couple things. No. 1, when you look at GitHub and the price Microsoft paid, it obviously is a ridiculous multiple to revenue. I saw a chart earlier today. I forgot if they said it was 21 or 24 times revenue, which is wow. Right? That’s why people do software companies.

    But another way of looking at it is, look, Microsoft has always coveted the developer community. And, over the last – I mean, for as long as I’m in technology, 25, 30 years, they’ve done not a crappy job of working with the developer community. Yeah, there are haters and Linux folks and the open source, when Ballmer was there, you know, but they’ve always gone after the developer community hard. And so they had an opportunity to buy a company that has, some estimates say, 28 million people or potential developers, right, in that community that GitHub has. So, when you look at 28 million and what they paid – don’t get me wrong; it’s still a lot of money, but it’s a little bit – you could see where they saw the value, okay?

    Zuber: Mm-hmm.

    Shimel: No. 2, having been in the tech, software infrastructure business a long time, I learned a lesson from my friend Brad Feld, who I sold my first company to and he financed or was one of the key VCs behind many of the companies I’ve been involved in, and that is, look, first mover or first – not the first mover, first acquisition in the space always gets the lion’s share and the best multiple. The second one does okay. The third one does a little worse. If you’re not in the top three, don’t bother. Right? That was something Brad always preached to us.

    So, when you look at Git – or GitHub, excuse me, being the first kind of acquisition in that space, getting this kind of multiple, they deserve it. Right? They were first. They were the first ones bought; they’re gonna get the lion’s share. I think the message to other folks in the GitHub space, specifically, is “Hurry up and get bought ’cause you don’t wanna be number four or five.” Right? You don’t wanna be left in the musical chairs game when the music stops.

    Part and parcel of that, though, Rob, is that companies like Microsoft, like IBM – we used to say “like HP, Cisco,” you know, big, big public entities – it’s very hard for them to be innovative. It’s very hard for them to do their own R&D. It’s very hard for them to build these communities themselves. And so what they would spend in R&D or community actually goes into their M&A budget and they buy those things.

    Zuber: Mm-hmm.

    Shimel: So, when we look at a GitHub, we look at a CircleCI, we look at any – a Chef, a Puppet, any of the – even the Jenkins or CloudBees, any of the players in this DevOps space that is so hot right now – GitLab, another one – they all are gonna be very attractive to companies of a Microsoft kind of girth. Right? Because the big guys can’t – they can’t do what you’re doing, Rob. They don’t –

    Zuber: Yeah.

    Shimel: You know.

    Zuber: Yeah. I mean, I think this is classic innovator’s dilemma, right?

    Shimel: Yeah.

    Zuber: Did I get that right? So it’s difficult. I mean, if you look at the first five year – I mean, we all talk about these overnight successes, right, and they always – they’ve been around for 10 years. And the first five years many of those companies is extremely painful, it’s a grind, and the incremental increase, the amount of revenue you’re driving or whatever, would be so insignificant on any one of these companies’ radar that they just – they won’t put the time and energy into it, right?

    Whereas you’ve got a company like ours or anybody in the space, honestly – I’ve done a bunch of different startups in different spaces – you’re living and breathing it, right? And you’re so tuned into what’s happening that you can see it. And that kind of incremental growth, to you, is everything and it’s super exciting and you get this passion behind it that allows you to build a very focused and, honestly, a great product. And I think GitHub is a great product. And then, suddenly, you have 28 million users – I’m quoting your number so I’ll assume you’re right –

    Shimel: _____ I’ve seen.

    Zuber: And a massive community. You know, and then, going back, as you were talking about the time and tech, I mean, I got into tech with the quarterly mailing of MSDN CDs and, honestly –

    Shimel: Exactly. Yeah.

    Zuber: – my favorite IDE – I’m a Mac and Linux user, almost exclusively, but I used Visual J++ in the late ’90s, when I started doing Java development. It’s still the best IDE I ever used. So Microsoft has been good, very, very good, with developers, but the kind of developer community has started to drift away from where they were going. And so this is – I wouldn’t call it a course correction because they still have all of their community, from a .NET and sort of Windows world, but this is an opportunity to be less about Windows, you know? And we’ve seen Microsoft shifting away from –

    Shimel: Oh, yeah. Satya Nadella’s Microsoft, Rob –

    Zuber: – just pure kinda _____ –

    Shimel: Not to step on you, but Nadella’s Microsoft is a very, very different place than when Steve Ballmer was there. Right?

    Zuber: Yes.

    Shimel: And they are moving to Azure and though Azure does Windows well, it does containers well, it does Linux, it does – you know, there’s very little it doesn’t do.

    Zuber: Right.

    Shimel: You know? And I will tell ya – I’ve told people this – I think, one day, Microsoft buys Docker. That’s my personal opinion. I think it’s another kind of – not to get into it or badmouth or anything like that, I just think someone’s gonna buy Docker ’cause the revenue has to justify the valuation, and so – and Microsoft’s a great candidate to do so. But, anyway, you heard it here first. But, Rob, that’s all fine and dandy. GitHub plays in sort of a different segment of this DevOps market than you guys do, certainly.

    Zuber: Mm-hmm.

    Shimel: And we really haven’t seen the consolidation yet, that I think we will in the CI/CD and, if you wanna call it, ARA space, but it’s coming. I’m sure.

    Zuber: Yeah, we’ve seen movement in the market, but most of it has been off the bottom end, if you will, meaning sort of the smaller people we would consider to be our competitors but didn’t quite reach critical mass and then got pulled in by other companies, for the people or because the product was going to be useful to them internally, that sort of thing. Not a roll up and now we’re taking this and getting it scales or _____ –

    Shimel: So we used to say, when I worked with Brad, those are companies that really were a feature, not a product.

    Zuber: Mm-hmm.

    Shimel: But, with that being said, Rob, we went off on a little bit of tangent here. We’ve used up way more time than we were supposed to. But maybe we could have you back on and – ’cause I wanted to really get into a little nuts and bolts around continuous integration, delivery, what it means for developers, what it means for ops folks, but why don’t we do this? We’ll call it a day on this 25-minute DevOps Chat and we’ll have you back on maybe next month. And let’s get into what it means for developers and ops folks in even testing, in this new world of CI/CD.

    Zuber: That sounds great. I’m always happy to talk about that as well. There’s so much happening in this industry, in this space right now, that it’s hard to keep it short. [Chuckles]

    Shimel: You know what? Hey, man, it keeps my kids going to college, Rob. [Laughs] Anyway, hey, Rob, Zuber, CTO, CircleCI, this episode’s guest on DevOps Chat. Thanks for joining us. This is Alan Shimel. You’ve just listened to another DevOps Chat. Have a great day, everyone.

    — Alan Shimel

  • DevOps TV: DOES18 London Video Panel Roundup

    DevOps TV: DOES18 London Video Panel Roundup

    The DevOps Enterprise Summit is one of my favorite places to connect with the world’s best technologists and DevOps practitioners. It’s the perfect forum for insightful conversations, valuable networking and immersive learning—and the comraderie is unmatched. For me, it’s always a pleasure to catch up with my great friends in DevOps and get an insider’s perspective from the leaders who are driving the industry and practices forward.

    This past June, DevOps Enterprise Summit London (DOES18) did not disappoint. We experienced firsthand some of the most iconic business transformation stories in DevOps. We also heard from the best technologists in the business. The programming committee introduced new themes and brought in fresh perspectives that reach beyond Dev and Ops. We got to see how the technology value stream influences the entire business from the standpoint of those impacted the most.

    Once again, devopsy.kinsta.cloud partnered with IT Revolution and DOES18 organizers for in-depth video panel conversations with the speakers and thought leaders. Next-generation ops and infrastructure, spanning the divide between tech and business, DevSecOps and experience reports were all topics of conversation at this year’s show. We talked about challenges, opportunities and what the future is going to look like for DevOps. Here are the highlights from the videos we shared on DevOps TV.

    Where are They Now?

    One of the things I look forward to most at DevOps Enterprise Summit (DOES) is reconnecting with leaders who have shared their DevOps journeys and experiences from the early days. These companies can act as the compass for those that are just starting IT transformation journeys. At DOES, we learn where these industry pioneers are headed, the ups, the downs and what they are working on/need help with next. For example, we continued the conversation with Jonathan Fletcher at Hiscox, whose DevOps journey has been incredible to follow. The Verizon team, who presented on Day, 2 sat down with me and talked about the long lasting effects their DevOps transformation has had on such an extremely large and already successful company. Last, but not least, representatives Capital One chronicled their DevOps transformation journey and their march toward high performing teams across the organization.

    DevOps Right Now

    If you want the scoop on where DevOps stands today, DOES is the place to be. I enjoyed the conversation I had with DevOps thought leader and author, Mirco Hering, who shared invaluable knowledge on the current state of DevOps. We also sat down with Ilkka Turunen, Zane Lackey and Margo Cronin to take a deep dive into one of today’s hottest topics: DevSecOps. Examining value streams of high performing companies was also top of mind and it was interesting to hear how adjusting that value depended on the changing needs of the customer. Nicole Bryan, Carmen DeArdo, Dominica DeGrandis, Mik Kersten and I had an insightful discussion about this topic.

    ITSM and DevOps Can Be Friends

    Whether you were a skeptic of ITSM or DevOps in the early years, it’s likely you didn’t predict that they would be compatible. We had a great conversation with the fantastic Jayne Groll, Rob England and Dr. Cherry Vu around ITSM, ITIL and DevOps—and how DevOps and ITSM can actually complement each other.

    Next Gen Operations and Infrastructure

    Gene Kim and the programming committee worked hard to make next-generation ops and infrastructure a big theme at this year’s conference by seeking some of the sharpest talents in this arena. We had the amazing opportunity to interview John Willis, Damon Edwards and Cornelia Davis to talk about where ops is headed.

    Spanning the Tech and Business Divide

    As I mentioned earlier, DOES18 examines how the technology value stream goes far beyond just Dev and Ops. We looked at its impact on HR, project management and more—and how DevOps applies to leadership these other areas of the organization. I had the pleasure of sitting down with Fin Goulding, Jelena Laketic and Mark Schwartz to discuss the role that IT leaders should play in a successful DevOps transformation and what things are of value when injecting high performance into a company. I also reflected on the different business organization strategies used to turn normal companies into high performers and common problems that can be overcome on that journey with Jon Smart, Morag McCall and Tom Clark.

    Competitiveness and DevOps

    If your organization isn’t constantly adapting to out compete the competition, regardless of whether you are practicing DevOps, you may have already lost. Jennifer Wood and Chris Hill stopped by to discuss the need for companies struggling to compete in their industries to adopt DevOps practices. We also got to get a glimpse into their own company’s transformation efforts as well. One industry in particular that is facing disruption is financial services. I was lucky enough to sit down with two high-profile finance based IT leaders, Shaun Norris and Nick Funnel, to engage in a discussion on the evolution of DevOps in their industry and the direction of DevOps in the future as technology continues to evolve for finance.

    Las Vegas is Around the Corner

    There are plenty more videos to check out on DevOps TV from DOES18 London and recordings of the onstage presentations at the conference as well. You can also view the PowerPoint slides here.

    I look forward to connecting with all my DevOps friends again at DOES18 USA in Las Vegas this October!

    — Alan Shimel

  • DevOps Chat: Alert Management with Everbridge’s Prashant Darisi

    DevOps Chat: Alert Management with Everbridge’s Prashant Darisi

    IT service management (ITSM) has been around for a long time, but its relationship to DevOps has been nebulous at best. In this DevOps Chat, we explore the connections between DevOps and ITSM with Prashant Darisi, vice president of Product at Everbridge.

    Everbridge is swiftly making a name for itself in the alert management space as a pure cloud company whose roots are firmly planted in DevOps. As usual, the streaming audio is immediately below, followed by the transcript of our conversation.

    Alan Shimel: Hello, everyone, this is Alan Shimel, and you’re listening to another DevOps Chat. Today’s DevOps Chat features Prashant Darisi, VP of Product at Everbridge. Prashant, welcome to DevOps Chat.

    Prashant Darisi: Thank you very much, Alan. Thanks for having me.

    Shimel: Oh, it’s our pleasure. So, Prashant, you know, just let’s get off the bat, many of our listeners may not be familiar with Everbridge. Everbridge is not quite your usual startup in that it didn’t announce funding last week or something like that. So, why don’t you give your listeners just a quick kinda corporate background on Everbridge?

    Darisi: Absolutely. Now, in the simplest single sentence, I would say Everbridge is the global leader for integrated critical event management solutions. We are a publicly traded company and we were founded following the tragic events of 09/11, where we realized that whether it is cross-team collaboration, cross-department collaboration, cross-city collaboration—there wasn’t a system out there that can connect all the dots to make sure that most important and pertinent information about safety of people, safety of enterprise, IT systems, physical assets and non-physical assets can easily ________.

    And so, that’s how this company got started. We are truly born in the cloud. So, the good news for our cloud customers is that we were not a bunch of on-prem companies that we pushed into one of the cloud platforms and said, “Hey, here we come, adopting the cloud.” From day one, a pure SaaS company. [Cross talk] Today we have more than 5,000 global customers, and we serve about 9 out of the 10 largest U.S. cities, nine out of the 10 largest U.S. investment banks, seven out of the 10 largest U.S. software companies, 6 out of the 10 largest global consulting firms, 6 out of the top 10 U.S. universities, 5 out of the top 10 pharmaceutical companies, all the 4 large global accounting firms, right, and 25 of the 25 busiest North American airports use our SaaS platform to ensure critical communications for anything that affects public safety, enterprise IT outages, cyber attacks, or even terrorist attacks and severe weather conditions. So, that’s who Everbridge is.

    Shimel: Excellent. And that’s very impressive, Prashant. Thanks for the background. You know, certainly, alert management alerting is in and of itself something that is not foreign to our DevOps audience, right? There are several sort of alert management, event management players who have really—I mean, they are sort of your traditional startups, right? They’re not public. I think one was actually acquired yesterday for $120 million.

    Darisi: That’s true.

    Shimel: But—you know, but they don’t, frankly, they don’t have the scale and the girth that Everbridge has, right? So, Everbridge was doing this before there was this DevOps movement and we were all excited about continuous delivery and continuous integration and that kind of thing.

    So, but now, you know, what—I guess my question is, Prashant, what has made the DevOps market interesting to Everbridge?

    Darisi: Yeah, for multiple reasons. One is, we have the platform that can support it, right? So, when we talk about how do we go and reach people—well, DevOps, for us, is more of a cultural change, right? I don’t want to pretend here, saying, “Hey, we looked at DevOps, this was the most exciting thing on planet Earth, and we start calling ourselves DevOps.” So, we are a critical event management company, but the beauty of this is that we drink our own champagne. When we talk about continuous integration and continuous delivery, we have, from a pure enterprise perspective, over 3,800 customers, and all of them get our new releases on the same instance, right? We offer it through ________ as well.

    Now, we could not, obviously, do any of this using a traditional waterfall method, either in terms of the velocity, or in terms of quality. So, when we talk about, do you guys use Datadog, do you use Jenkins, Drone, do you use GitHub, do you put your artifacts in JFrog—any of the popular tools that are out there. We’re not trying to promote any one product. We live, breathe, and die by these processes day in and day out. That’s a survival issue, because we’ve never had what we call an on-prem piece. This is the only way we deliver value.

    Now, if that’s what we’re doing and that’s the platform that helps people communicate and collaborate, why wouldn’t we naturally go into the world of DevOps? Traditionally, of course, we started into the ITSM piece of the world, right? This is where the ServiceNow, Remedies, and the HP SM worlds came into the picture. But, as organizations started shifting, Alan, I remember, I think you wrote—what, two, three years ago, that all the CIOs said 88 percent of them will adopt DevOps in the near future? That’s when even we started pivoting—how can we help these folks bring these solutions together?

    So, the reason why we’ve gone here is, we can obviously help folks communicate with each other. We have about, what, 100-plus communication devices, and one of the advantages we have is, why DevOps is great—companies are also starting to spread their development centers across the world. You know, I’ve done development for—what, two decades, as an engineering guy? But I never was on call, right? But look at where the world stands today.

    And so, if, just like technical support, engineers are starting to follow the sun model where you have a communication system that can cut across countries and do language translation, can you have collaboration tools like Slack, Tribe, HipChat, put it all together? Can you help customers do them with automation? Can you do language processing on who said what, what kind of diagnostic scripts were run? Last time when you patched the system, what were the results of it?

    The analytics of those things—we have the platform, and the fact that we manage 210 million contacts worldwide, and the fact that we can send 2 billion messages, that’s the number we delivered in 2017, and we have access to 100-plus communication devices—it became a very natural fit for us from a domain expertise from within the organization, what a customer that’s doing CI/CD needs, and from a platform perspective of what kind of scale and geographic reach you need to have to bring the two worlds together.

    So, I don’t want to pretend that we are born a DevOps delivery company, but we certainly are a born DevOps product company that today is public.

    Shimel: Got it. So, Prashant, you mentioned a couple things, there, Prashant. The first thing is, there’s a very common fact pattern that I’ve observed in talking to many vendors in the DevOps space, and that is that their involvement in the DevOps market started with their own use of DevOps, right? They started using tools like Jenkins and JIRA and some of the others you mentioned, and that their own use and adoption of these tools allows them to kinda see the benefits, right, of using DevOps, and also then allows them, frankly, to have some credibility when they’re talking to DevOps teams in the marketplace, because you yourself are a DevOps team yourself, right? You understand what it’s about.

    Darisi: Yeah.

    Shimel: Understand? Yeah?

    Darisi: Yeah, absolutely—completely understand. And, I think it’s, for us, just look at our own organization, right? And I don’t know how many of your listeners will agree. We have offices in Los Angeles, right here in Burlington where I’m sitting, Lansing, Beijing, London and Stockholm. Now, not all of them are development organizations, because we have grown organically. But we need to scale down that framework and true DevOps practices to keep ourselves, have some semblance of sanity. Otherwise, you know, we go nuts.

    So, I do agree that, because we live and breathe these systems, I hope we are able to deliver our solutions with a credibility both from a domain expertise perspective, but also, a very natural alignment with the tools that the customers are using, right?

    Shimel: Yep. Excellent. And then, Prashant, you brought up another kinda topic that we have been kinda running into and writing about more recently here at devopsy.kinsta.cloud, and that is the whole relationship between ITSM and DevOps, right?

    I think initially, you know, we started devopsy.kinsta.cloud back in 2014, there was this feeling of sort of ITSM goes with waterfall, if you will, or it’s from that generation, and that somehow DevOps and ITSM were mutually exclusive. But the fact is, what we’ve seen in real life is that that’s not the case, right? That there are—ITSM, there is a bridge from DevOps to ITSM and back. And that there are, there’s—you know, I always like to tell people, Prashant, there’s only one truth. I don’t really care what you call God or, you know, we’re talking about religion, right? Good is good, bad is bad, and truth is truth.

    So, the right things that we’ve learned to do in ITSM shouldn’t become wrong things in DevOps, right?

    Darisi: Yeah. [Laughter] Yeah. So, since you used the word God, I will say amen—you hit the nail on the head, right?

    Shimel: Yeah. [Laughter] Okay.

    Darisi: I’ll give you a simple, Alan, here’s the analogy, right? I need to go from here, Burlington downtown, a lot north of Boston downtown, and I need to go from here to there. I could walk, I could take a small car, or I could take a BMW. Now, if my GPS is wrong, a BMW will only take me to the wrong place faster, right? It’s, in the end, whatever we use—tools, methodologies, anything—they’re a means to efficiency. It starts with a cultural change, right? Putting the right processes in place, and then automating these processes for efficiency reasons.

    So, I would argue that—like I said, I just came back from meeting this very large priced customer, oil, and you could feel that the DevOps team thinks ITSM or ITIL or COBIT or any of these things—these are dinosaur practices. It’s not. Actually, you can use the elements of DevOps principles within ITSM. And you’re not going to solve everything using DevOps, because if you look at our shadow IT, there are some systems and infrastructures that are still being held traditionally in data centers that need to be highly secure. Then there is this concept of business driven apps where folks like to use Salesforce.com for their pipeline management. You’re not in control of that any more.

    So, somehow, you have to be able to figure out what’s the dependency of the so-called shadow IT system sitting in the cloud, completely managed by a third party vendor through an SLA agreement, and you’re on prem in your own private cloud enterprises.

    And so, I think the reason why people thought or still think, I think, ITSM is waterfall is this whole notion that, culturally, ITSM or ITIL or COBIT practices are all about who controls, right? Well, rather than talking about who controls, if the same principles can be applied within an IT organization to start enabling the business, start empowering the business to say, “Okay, you are in the better position to make the judgment call on something simple like access request, or what are the things that you need to look for when you deploy a patch or upgrade, and we will take care of the security aspects of it, and if something goes wrong, we will ensure proper communication and collaboration”—I don’t see any friction between the two worlds.

    There’s a tremendous difference in lexicon, for sure, but many, many banks and many, many organizations which are true IT organizations are saying, “Prashant, do you follow the agile model?” Right? “We are doing project management doing agile now. Oh, you’re coming here to do an implementation and integration of DNC Committee or ServiceNow or HP SM? Can your PS implementation team help us break it down across our sprints?”

    So, everybody has now started looking at the value of agile frameworks and beginning to see that, you know, the two worlds are coming together. And obviously, they’re embedding, from an HR perspective, people into each other’s team as well. So, then we talk about site reliability engineer, DREs, ________ operation folks, development folks, and perhaps even infrastructure folks all sitting in a standup or around a standup table. It’s all coming together.

    So, I think this is a little artificial, whether we’re trying to drive this line or a hard line between it, there are definitely different lexicons, but I think there is an easy way to bring these people together from a process perspective.

    Shimel: I agree 100 percent. And I think we’re seeing that kinda play out, right before our eyes in real time now. You know, we’ve seen, for instance, ServiceNow come out with a DevOps related system, right, that brings a lot of this together as well. I’m also involved and one of the co-founders of DevOps Institute, the DevOps Institute, and we have a drill down class on the bridge DevOps to ITSM.

    So, I think that’s all there. But Prashant, as much as there’s a bridge being built and we’re learning how ITSM and DevOps works together, another thing we’re learning is how critical event management works with so many of these DevOps tools—and you mentioned some earlier on, but can you share with our audience, give us an idea, you know, we talk about automation and stuff like that—how does Everbridge help with that?

    Darisi: Yeah. So, we’ll take it at the, let’s say, 10,000-foot level, and I’ll quickly and rapidly try to bring it down to a simple tool. But when we talk about critical event management, for us at Everbridge, a critical event or a disruption is a disruption is a disruption.

    And so, since I gave the example of a tornado approaching a building in Oklahoma City, let’s stick with that. Now, whenever such an event occurs, we know what is going to get impacted, but I’m not sure people do get that. For example, clearly, we know some people will be affected from purely an evacuation perspective. We know that the buildings and the physical assets within the buildings will get affected, and then we also know that we might be hosting a data center or a set of services that are going to get impacted.

    So, how can we help our customers figure out what we have coined as a consequence map. What is the consequence of a critical event or a disruption to a company’s business, both from a people perspective, physical assets perspective, and enterprise IT operations perspective?

    And this is where automation starts becoming very critical. How do you understand, from a CMDB integration, what are the components out there, or which business units are affected, right? So, Everbridge, from our perspective, we do CMDB integration on a very lightweight basis. We obviously don’t want to get into the CMDB business, but our job is response correlation, right? We are not in the business of reading logs and packets and telling you about events. We are not a log miner company, we are a response correlation company. When a critical event occurs, there are a lot of connectors and automated tools that will tell us something is not right. Now, there could be a direct correlation from a response perspective on a denial of service attack that goes and impacts the performance of a website.

    How do we make sure that we are helping our customers correlate their responses, right? How are we able to look at the product and location, the services that are impacted both upstream and downstream and trying to figure out, from a communication and collaboration perspective—Alan, you; Prashant, you—both of you are working on this critical event. One came through an item system, a new relic, or somebody telling you, and the other thing comes from a QRadar or a Resilient kind of a system saying denial of service underway. How do you know that you need to combine forces?

    So, Everbridge wants to be in the business of response correlation, far less about event correlation. So, our automation platform or the smart orchestration platform starts picking up data from these disparate sources, integrates with stuff like the CMDB and looks at the CIs and says, “Hey, I see that these critical events are related,” right? For example, a fire in a building can—it’s police, it’s ambulance, and it’s the IT systems that are sitting there—how do we correlate this? That’s the business we are in. And, for that, you need a smart orchestration platform that is looking at data or alerts coming from these different places.

    And then, when it comes to the pure IT pieces of it, right, how do we help from a DevOps perspective? Well, let’s start with the communication part of it. Can we reach out to these people, whether it is on call calendars, making sure that we follow the proper escalation procedures? I heard something else, Alan, you were talking to somebody, saying, “Hey, people still prefer e-mail,” or that’s still the number one choice. Well, in our Everbridge platform, for certain types of events, based on the criticality, we do not give the choice, even though every individual can pick 100 different types of modalities in which they can receive an alert, but for certain critical events, we will override that. We will wake you up during the morning—because guess what? An e-mail cannot wake you up, right?

    So, it depends on those business policies and rules, and that’s the kinda of work Everbridge wants to do. And then, once you have communicated with these people, how do we bring them together? I mean, just today, right, we had to start GoToMeeting, and if I had used the phone, I would put in a 10 digit number, then a 9 digit code, then an audio PIN. Well, the way we help our customers is, when you receive that SMS text, all you do is press 1, and you’re on the Smart Conference page. No numbers to type, no nothing. And if you are sitting somewhere in Europe, somewhere in the Philippines, India, China, U.S., each one of them will receive a local code. So, nobody’s on an international call. If there is a language translation that needs to get done of the same, exact trigger, we help our customers do that, too.

    So, now that you have a bunch of developers who are all responsible for taking care or of the resolution process, people typically will say audio is great, right, and oh, by the way, recording the audio is great as well. Can you enable us through a collaboration tool? So, this is where the second aspect of it comes, right? Whether it is using Slack, using HipChat, Tribe, Cisco Spark—we bring these people together.

    And all of this is recorded or, as long as the customer prefers, they’re all associated with the IT incidents, and then we want to leverage this data for knowledge transfer, for blameless root cause analysis, a post mortem of the events that happened so that next time when a similar pattern of incidents occur, we should be able to say, “Hey, last time when this happened, go and look at that Slack channel or the HipChat channel. We ran these two diagnostics ________. Have you seen this? Do you want to try this again?” And then, our connectivity on the remediation side, people could say, “Hey, I think we should move to Apache server,” right?

    And the way our infrastructure is set up, you can pick a certain set of Runbook procedures that are automated or, Alan, you could get a call and say, “The team that’s presently on call has decided that they need to reboot the server. Alan, you have been determined as the security architect that needs to approve this. Press 1 to approve an automatic reboot of the server, press 2 to join the conference bridge, or press 3 to enter the Slack channel.”

    This whole process is automated, right? Whether it is smart conferencing or the on call schedule or integration with these collaboration tools or the Runbook automation tools and the recording for archival knowledge base and analytics purposes—everything is done with our platform today.

    So, it can take various shapes and forms, but these are some of those key macro cases, Alan, of how our customers are using our product.

    Shimel: Got it, got it. Alright. Prashant, I told you when we started, Prashant, the times goes so quick here. We’re way over time already, but—so, we’re gonna have to call a wrap. Maybe we can come back and revisit and talk more about this within the larger kinda landscape of what we see today in IT as well.

    But for now, let’s call it a day. Prashant Darisi, VP Product for Everbridge, thanks for being our guest on DevOps Chat today, and we hope to have you back soon.

    Darisi: Alan, thank you very much for having me. Looking forward to another conversation. Thank you.

    Shimel: Okay. This is Alan Shimel for devopsy.kinsta.cloud, and you’ve just listened to another DevOps Chat.

    — Alan Shimel

  • Tricentis, QASymphony Merge: The Age of Continuous Testing Is Upon Us

    Tricentis, QASymphony Merge: The Age of Continuous Testing Is Upon Us

    Big news in the world of continuous testing today as continuous testing market leader Tricentis announced it is merging with QASymphony. Tricentis, a leader of continuous testing, is adding QASymphony’s leading testing automation platform to the mix. The full text of the press release is below.

    With the worldwide testing market pegged at more than $34 billion, this is a big move in a very big market. Tricentis raised $165 million last year from Insight Venture Partners and has put this money to good use: The QASymphony merger is Tricentis’ latest move. Previously, it acquired Q-Up, in June, and last year acquired Flood IO.

    Tricentis’ merger with QASymphony is happening at a time when continuous testing is becoming one of the hottest areas in DevOps. The demand for automated, continuous testing is driving a revolution in the QA market as companies recognize that quality is as important as speed when it comes to deploying new apps. It is a key cog in the modern software factory.

    I had a chance to sit down and speak with Tricentis CEO,  Sandeep Johri, about today’s announcement, the testing market and what the future may hold. Sandeep, who has previous experience at HP and other large providers, has a great vision of the market and where it is heading as well as the details that escape many “professional manager” CEOs. His hand is firmly on the wheel as he drives Tricentis forward in this space.

    Have a listen to our conversation below, and stay tuned—we will update and continue this breaking story as more details emerge.

     

    Tricentis and QASymphony Merge to Drive Innovation in Continuous Testing for Enterprise DevOps

    Next Gen platform disrupts the $34B testing services spend and transforms software testing for DevOps

    Mountain View, CA— June 20, 2018 — Tricentis and QASymphony announced their agreement to merge under the name of Tricentis. Tricentis’ market-leading Continuous Testing platform has earned the company unanimous “leader” recognition among the top industry analysts. QASymphony is recognized as the industry’s leading test management solution. The combined solution represents the most modern platform for transforming software testing to keep pace with digital transformation.

    “Tricentis and QASymphony are both recognized for their innovative testing solutions,” explained Sandeep Johri, CEO of Tricentis. “Tricentis is known for helping enterprises transform testing from a burdensome manual process that delays software delivery into an automated, continuous process that drives ‘quality at speed.’ The addition of QASymphony’s test management solution strengthens our leadership position and builds on our momentum replacing legacy testing tools.”

    “Today’s CIOs are responsible for ramping up innovation through accelerated software delivery,” explained Barry Libenson, Global Chief Information Officer at Experian. “Amid this demand for rapid innovation, CIOs are recognizing that software testing often delays their digital transformation goals. In fact, testing is now commonly cited as the #1 bottleneck to delivery speed. When testing lags behind development, the organization is forced to delay their innovation and that’s no longer an option. It’s inevitable that software testing must be transformed to keep pace with Agile development and DevOps.”

    “Global 2000 organizations remain locked into legacy testing platforms that were designed decades ago to enable manual testing processes,” explained Dave Keil, CEO of QASymphony. “Scaled agile and enterprise DevOps initiatives have changed the game. Yet, legacy testing technologies such as those by HPE (now Micro Focus) and CA are throttling speed and innovation. QASymphony has experienced triple-digit growth over the past year—allowing us to aggressively invest in our technology, infrastructure and people to meet the emerging needs of our customers.”

    QASymphony’s 100+ employees will be joining Tricentis’ 450+ employees. Sandeep Johri will lead the organization as CEO and Dave Keil will assume the role of COO. The combined company will have a global presence with offices in the US, EMEA and Asia. The transaction is expected to close within 90 days. EMBARGO UNTIL WEDNESDAY, JUNE 20, 2018 @ 8:00 AM ET USA

    The integration will reflect the commitment to innovation and customer success that both companies share—to learn more, register for the upcoming webinar. Additionally, the company will be showcasing the roadmap and solution at Accelerate 2018 in Vienna.

    DevOps Impact

    The market for software testing (recently estimated at $34 billion)1 has reached an inflection point. DevOps adoption is rising rapidly, and both Gartner and Forrester report that transforming testing is a primary factor for DevOps success.2 Yet, software testing remains a predominantly manual activity that delays releases and consumes 30-40 percent of an organization’s application budget3,4 Tricentis Continuous Testing solutions accelerate delivery and free up significant budget that can be reallocated to underfunded innovation initiatives.

    Gartner’s Joachim Herschmann and Thomas Murphy report: “As DevOps principles gain significant traction in enterprises, testing and QA is no longer a stage in delivery but an integral DevOps activity that exists in various forms through all areas. Automation has become an indispensable element in these efforts, and there has been renewed focus on software test automation tools as part of a larger toolchain that enables DevOps.”5

    About Tricentis

    With the industry’s No. 1 Continuous Testing platform, Tricentis is recognized for reinventing software testing for DevOps. Through risk-based testing, scriptless end-to-end test automation, and the industry’s most extensive technology support, Tricentis breaks through the barriers experienced with conventional software testing methods. Our innovative technologies simplify testing for even the most complex enterprise applications—transforming testing from a roadblock to a catalyst for innovation. The result is accelerated software delivery speed, improved cost efficiency, and reduced business risk.

    Tricentis is the only vendor to achieve “leader” status in all three top analyst reports (i.e., the “Triple Crown.”) This honor is based on our technical leadership, innovation, and a Global 2000 customer base of 800+ companies, including global enterprises such as Allianz, ANZ Bank, Experian, First Data, HSBC, Lexmark, Merck, Sentry Insurance, Starbucks, Telstra, UBS, Vantiv (now WorldPay), Vodafone, and Whole Foods. These customers rely on Tricentis to achieve and sustain test automation rates of over 90 percent—increasing risk coverage while accelerating testing to keep pace with Agile and DevOps. EMBARGO UNTIL WEDNESDAY, JUNE 20, 2018 @ 8:00 AM ET USA

    Tricentis has a global presence in Austria, Australia, Belgium, Denmark, Germany, India, Netherlands, Singapore, Switzerland, Poland, United States and the UK. To learn more, visit https://www.tricentis.com or follow us on LinkedIn, Twitter, and Facebook.

    About QASymphony

    QASymphony accelerates digital transformation with software testing solutions that help enterprises prioritize quality, develop reliable software and increase speed to market. The qTest platform streamlines software testing in agile and DevOps environments and centralizes testing efforts across the enterprise. By taking a strategic approach to quality, QASymphony enables enterprises to develop higher-quality software, faster, to better support new business models and customer experiences.

    The qTest platform streamlines development workflows by seamlessly integrating testing with leading automation, development and delivery tools including Atlassian’s Jira, CA Agile Central, Github, Selenium, Cucumber, Jenkins and many more. QASymphony is trusted by leading enterprises including Forcepoint, PFSweb, Cisco, Samsung, Verizon and Office Depot.

    1 Nelson Hall, https://research.nelson-hall.com/sourcing-expertise/it-services/software-testing/

    2 Gartner, Build Continuous Quality Into Your DevOps Toolchains: https://www.gartner.com/doc/3868367/build-continuous-quality-devops-toolchains

    3 Capgemini, HPE, Sogeti, World Quality Report: https://www.capgemini.com/service/world-quality-report-2017-18/

    4 Capgemini, HPE, Sogeti, World Quality Report: https://www.capgemini.com/service/world-quality-report-2017-18/

    5 Gartner, Magic Quadrant for Software Test Automation: https://www.gartner.com/doc/3830082/magic-quadrant-software-test-automation

    Media Contact

    Victoria Brown, Revere

    +1 (650) 850-2009

    Victoria.brown@revereagency.co

    QASymphony Contact Information Kira Mondrus

    QASymphony +1 (844) 798-4386 Kiramondrus@qasymphony.com

    Tricentis Contact Information

    Noel Wurst, Tricentis +1 (904) 673-4427 n.wurst@tricentis.com

    — Alan Shimel