 inside the cube at Velocity Conference live in Santa Clara Convention Center. I'm John Furrier, the founder of SiliconANGLE. This is theCUBE. I'm joined by my co-host. Hi everybody, I'm Dave Vellante of Wikibon.org. This is theCUBE and John Ausfaz here. He's the Senior Vice President of Technical Ops at Etsy. John, welcome to theCUBE. We heard some great keynotes this morning. So I got to ask you, it's the web getting faster. Did we learn that? I think we heard a little bit, that's a good question. I think we heard a little bit from a number of folks that the web isn't necessarily getting faster. And this is something that we, I think, should expect with every new incremental ability that we have. We have new standards, we have new practices. Video is cheaper than it once was and rich experiences are much cheaper to make. So then therefore, we can make the pipes faster and we can make the pipes bigger, but we are going to absorb that. So it's not like we build websites and then all of a sudden the networks and the pipes and sort of the practices allow us to go faster. That may be true, but we will always exploit the, rightly so, exploit those to do more on the web. So I would say that it's a perception. I don't know if we have real data to support that it's actually faster. So give us the rundown on this morning, on what we can expect for the rest of the day. What you're excited about here at the event? So I'll tell you, this is the reason why I love Velocity. It is a practitioner-oriented conference. This community has very low tolerance for, for buzzwords, it has very low tolerance for hand wavy. It has very low tolerance for words that aren't backed up by working code and working infrastructure. So, having said that, this audience, like I said, is over the last six years at Velocity has been talking and sharing about the types of failures and successes that they have. And sharing that, not as a commercial advantage, not as a competitive advantage in marketplace, which exists, but as a way to collectively, much like the web, make things better. And so that's, I think, that's what's quite different between Velocity and other conferences, which are the things I'm excited about. So the tech operations is kind of, I don't want to say cult, but it's a really tight-knit community. You mentioned tolerance. Jonathan Hellinger, who was at Facebook, and I talked a couple years ago in 2010 when Facebook was really scaling up their operations. So that was called web scale of time. Now the term is hyperscale. But that world is now very relevant with DevOps and with the role of what the cloud can do and to power not just web, but mobile. So how does Velocity fit into those, that megatrend, because DevOps or technical operations at scale is a huge challenge. It's the application lifecycle, lifetime of an app, agile programming. What is the Velocity mission related to those megatrends? I'm going to lean in on you here and say that differentiating hyperscale from small scale is, I think, asking a very different and not as relevant question as you might think. What Velocity is about, and this is the reason why you would see web performance, which front-end engineers, Steve Souters, my co-chair, an expert in this field, and operators, right? At the same conference on paper, you would think that these might be at best, at worst, diametrically opposed, or at best somewhat just adjacent in their domain expertise. What Velocity is about is about making informed design and operational decisions that include trade-offs. You have trade-offs when you're a four-person in a garage startup or whether you're Facebook. And shining light, shining a big, massive flashlight on the trade-offs that you're making and making them explicit, that is what the conversation is about. On the design side. On all of it. And when I say design, I don't mean visual. I'm talking about infrastructure design, I'm talking about code design and software development patterns. The system, the architecture of the system. The entire system. And that speaks to some of the entrepreneurial landscape. Now, they're saying the series A is the new series B, and Driessen Horowitz had a post on that, one of the partners they had talking about, hey, seed funding, half a million dollars, and now there's enough tech out there to get some integrated design where you can show some scale, show some movement, either in the adoption of revenue or application viability. That kind of speaks to this, right? I mean, if you design it properly, you can get some. It depends on the definition of properly, right? Properly for Facebook meant in Zuck's room at Harvard, right? Yeah. Those are very different decisions, and probably quite apt at the time, than what Jonathan made years later. And so, again, I think that where the conversation, the better question is not building it right the first time, it is, or building it right at any part of your evolution, it is making it very clear on what you are building and how, when you expect all designs will fall over. It's only a matter of time. And so, a lot of velocity attendees are pretty familiar with spending too much time to get something out that's absolutely perfect is going to scale infinitely. Why would you do that if you have zero customers, right? Versus the trade-offs that you would make when you have a billion users. So, it's a bit of a much more complex, but it's not as delineated, I would even argue delineated by even funding, to some extent this is, but I would say it's just a yet another influence on those decision-making. John, we know you got to go, but you think your point about a conference for practitioners is right on, if you listened in this morning, it wasn't a bunch of hand-waving and celebrating the progress that you've made as a community, it was all about the challenges, the problems, the risks, how to identify those. So, we heard a lot of good meaty content this morning. What's up for this afternoon and tomorrow, give us some highlights. My, I think what you're going to hear is a plethora of perspectives. I think you're going to hear, and that's the thing that we're hoping for, is to get a diversity of opinion, and that has real meat. We don't want to talk about theory. What you're going to hear from a number of cases, and a lot of these are, you can consider them as sort of case studies. From the operation side, you're going to see a lot, a continued from last year, emphasis on the word resiliency. Building something perfect that will never go down is exactly a pipe dream, and instead of spending time preventing failure, and instead focusing on how can you best absorb variations, right? The cloud is basically a forcing factor on this, because failure is expected very much, and I think that's probably, history may say that that's actually the larger benefit because the cloud can fail, so that's good. Okay John, I know you got to run for your next segment. Thanks for coming on theCUBE. I know you're tight, really appreciate it. We'd love to spend more time with you, but you're in high demand. Thanks for coming on theCUBE. We'll be right back. We're going to drill down, have a lot of conversations with the technologists, the practitioners, and the folks putting the meat on the bone, as we say. A lot of sizzle at other events, but the steak is here at Velocity, meat on the bone, use cases, operations, design, great philosophy, a lot of diversity. So thanks for coming on. We'll be right back. The next guest after this short break. All right, thank you.