Whereas text messages are asynchronous, and we seem to have, for reasons that maybe aren't super helpful in this conversation, but still we seem to have a strong preference for that asynchronous mode of communication in that realm, even though you're holding the device that is perfectly capable of communicating with the same person synchronously. Block or report user Block or report mtnygard. Nygard has held positions including as the VP of customer solutions at Cognitect, Inc. and technical director at Verizon Business, leading the Innovation Incubator in the Verizon Global Services Division. But I wanted to say that I think I had been referring to it when I was talking to you and said, "Oh, you should come on the show and talk about microservices since you're writing a microservices blog series." It is actually pretty important. Michael works for Cognitect Inc., the company behind Clojure, ClojureScript, Pedestal, and Datomic. You can send feedback about the show to podcast@cognitect.com, or leave a comment here on the blog. This has been true for some time. We use a lot of building metaphors for software, and I think that gives the false impression that you reach a point where you're essentially done and you just need somebody to go around and change light bulbs and repaint the walls once in a while. For instance, pushing a rewritten history to a branch that was previously pushed. A year later, and one project manager different, the team room was disbanded. Maybe somebody was making a call with bad data and it crashed the supplier. 01:42 - Mike’s MICHAEL: Mm-hmm, and there have been some efforts to take the Agile approach and sort of scale it up to the level of the whole organization. MICHAEL: I think the one piece that we haven't even touched on yet is the one about using high leverage tools or sharp tools in our local parlance. Hopefully you're hearing this before that. A podcast by Cognitect, Inc. about software and the people that create it. We like to work with you on the hard stuff. Michael Nygard mtnygard. Definitely one of the people I always enjoy talking to. It's voice over IP. But they're all viable ways of saying a failure in my service doesn't need to propagate to the others around me. Prevent this user from interacting with your repositories and sending you notifications. Thanks for listening. They'll look at it and they'll go, "Well, these microservices, that's nothing different than SOA." And I'll return a response to the user that says he'll get a follow up email in 24 hours or whatever.". CRAIG: Where you're saying there's a context that flows down through the parts of this, I guess, document in the case of XML. Cognitect news, musings and more. For game development. I've been to a number of places where they have these very large monolithic code bases, some of them ten years old or more. Michael Nygard October 17, 2013 Technology 2 650. We have the ability to do automatic migrations at this point, so some of the techniques that Jez Humble talks about in Continuous Delivery work really well for this too. It just adds something to it. The Cognicast is produced by Kim Foster. I guess what I'm wondering is what your thoughts are on using URLs as keys because what you're talking about is, if I imagine the data going in and out of some service, is a map, which I think is a reasonable thing to do. It was more like: We're going to have you on the show. It's taken me a number of posts to sort of lay out the story because this is the kind of thing that people who have been on this journey have just assimilated along the way incrementally. I think this is one of the motivators for containers, by the way. The opportunity grants are awarded to people to assist them to attend if they would not otherwise be able to. In this episode of the O’Reilly Programming Podcast, I talk with Michael Nygard, a software architect at Cognitect. He has lived with systems in production and learned hard lessons about the importance of operations. In that case you had multiple different sub-teams having a shared dependency at a binary level on something that runs in process. MICHAEL: Yeah, and he wasn't even deliberately harming it. And you were very polite. You can do any crazy crap you want as long as you have confidence that undo is going to get you back to where you were. MICHAEL: The collected advice of The Cognicast. And I don't see that coming out of any of the large-scale Agile efforts. This is an example where I'm like, okay, well, how would I apply that to dependencies? That feeling has still stayed with me. It's the question about advice. Our guest today was Michael Nygard, on Twitter @MTNygard. I think we've talked many times before about music on this show, and there's something about it as an art form that's unique. Whatever it was, it was good. He shares his passion and energy for improvement with everyone he meets, sometimes even with their permission. We've talked for a long time about the dissolution of the command and control network, the failure of the hierarchic model, and the emergence of network models in corporations. That's, by the way, one of the motivators for devops and merging those two teams or blending those two teams. Another deadline associated with EuroClojure is the opportunity grant applications. We went all the way down into technical and all the way up into the organizational philosophical. Everybody publishes their own thing because the risk to our organization of being as slow as the governance makes us go is greater than the risk of occasional system breakage. CRAIG: Yeah. What are the preconditions that have to be there? Go there, and you'll see the whole transcript feed. Yeah. You've sort of been building a story arch, I think it's fair to say, as you've made these posts. MICHAEL: Then we start getting into factories for making factories and that becomes even harder to visualize. I am wondering too. 01:42 - Mike’s Background and Career Path Thus Far 02:59 - Complex Systems The Complexity Explorer 06:22 - Continuous Partial … But it's also remarkably practical, and so that is an excellent addition to our rapidly growing stable of really good advice, so thanks for that. Daniel Compton - Cognicast Episode 140. The one that doesn't break keeps running its software, making assumptions about being able to talk to the first one, and we start having to change our risk model from saying it's all or nothing, either the machine is working or it's not, to a more probabilistic approach. Michael Nygard: @mtnygard | Wide Awake Developers (Mike’s Blog) | The Cognitect Blog | Release It! CRAIG: Usually it's some sort of perceived or actual threat or risk. When accounting finds out about this, they have to take it as a write-off and all kinds of ugliness happens to mark it as a disposed asset and so on. The problem that I lay out is that having team scale Agile development and great velocity there is a necessary element of corporate success, but it's not sufficient. I think your insights are amazing and valuable, and it's really been cool to see the series develop. How do you make it in people's best interest? For instance, if you take a group of two people, the odds that they have the same birthday is 1 in 365, roughly, right? Another approach that I use are bulkheads. Articles in your series. Of course, now that's the sort of thing where, okay, if I want to view it as building a factory, well, of course I need to be able to change it because the factory is producing widgets today, but tomorrow it needs to produce wadgets. MICHAEL: Maybe we should have a special transcript somewhere of just all the bits of advice collected. CRAIG: Yeah. Yup. Mike is the author of Release It!, and a contributor to Beautiful Architecture. MICHAEL: Yeah, that is a really fascinating question. Discussion points: CRAIG: Hello, and welcome to Episode 106 of The Cognicast, a podcast by Cognitect, Inc. about software and the people who create it. That program then runs, and it maybe runs many times over the course of its lifetime. As you may have noticed, the Cognicast has finally made its way to its new home here at cognitect.com! CRAIG: That's all right. @mtnygard. What is this idea or set of ideas you're trying to get across? Yeah, you wouldn't. Yeah, obviously it's something that we're capable of thinking about as a human level process. And so why should we treat ourselves with reckless abandon if our time is valuable as well? It's a really bizarre concept for people that haven't run into it before. One, it's a handshake to initiate a conversation just like a TCP three-phase handshake. Michael Nygard is an architect at Cognitect, the company behind Clojure, ClojureScript, Pedestal, and Datomic. It's a breakdown of boundaries. Whenever I build a service, I want to make sure that I'm not just serving one population of consumers, but anyone else in the company can write a new consumer of my service and start making calls without necessarily informing me first. I also saw a company go through a large-scale, just in time, inventory project. When we build services, I think too often we build a service with a specific consumer in mind and we don't think about enabling our service to be used by other consumers without explicit permission. Rather, I have to know. Michael Nygard - November 15, 2011 agility architecture. When should we do it? Michael Nygard. Nygard is the author of Release It! MICHAEL: Yeah. That's what I'm doing today. ... cognitect-labs / onto. Cognitect, Inc., 303 S Roxboro St., Suite 20, Durham, NC 27701 919.283.2748 info@cognitect.com The show is available on iTunes! Our theme music is Thumbs Up (for Rock N' Roll) by Kill the Noise with Feed Me. The problem with that viewpoint is it causes us to write code and keep it around for a lot longer than we should. CRAIG: Sure. Michael works for Cognitect Inc., the company behind Clojure, ClojureScript, Pedestal, and Datomic. You want to create a process that makes it easy to deal with. Living with systems in production taught Michael about the importance of operations and writing production-ready software. Anyway, I want to come back to the series. It's all good. They're also kind of self-supporting, right? CRAIG: Cool. Cognitect, Inc. You can find Michael coding, writing, speaking, or thinking about how the Universe works. And so I wonder whether there's any juice in the metaphor of building a factory. As soon as you get two computers interacting, there's the possibility that one of them breaks and the other one doesn't. MICHAEL: I view it as important not just for correct functioning of systems, but for that without permission characteristic where I want every team to be able to deploy their systems whenever they want, and I want them to be able to communicate about how they act without permission. It's hard to believe. They do. Context ... about Cognitect. It's been great, so thanks a lot for coming on the show today. No process. I'm your host, Craig Andera. The interesting thing is we can respond to continuous partial failure in a couple of different ways. They just can't maneuver at all with that kind of an anchor. Maneuverable Web Architecture. I am not a fan, for example, of passing around a raw ID, just a number or an alpha numeric string. Michael T. Nygard! CRAIG: How do you protect yourself against that failure? I wonder, though, whether that experience was special to you because it was live, because I've been thinking a bit about live music recently, or if it was just the level of performance and the fact that you were there in person was less of a factor. But the technical aspect of getting access was probably much easier than the political aspect or the inter-team communication needed to make sure you were going to be allowed to use their service. Actually, that's going to let people consume the show in whatever way they like best. He shares his passion and energy for improvement with everyone he meets, sometimes even with their permission. Maybe you want to describe that for our listeners. @mtnygard. One of the things that they do is they have a Kafka topic, which is their registry of message definitions. And so it's fascinating to me to think about how. This was the era of the tandem computer. Thanks for listening! We talk with Michael Nygard about simulation testing. CRAIG: Cool. But I wonder whether it's more like building a factory because, first of all, a program, we write source code to produce a program. Oh, everybody breaks. Cognitect, Inc. Speaker site. A lot of the software we write gets thrown away and rewritten before the asset depreciation period would be done. In this episode, we talk to Michael Nygard about microservices and other things from his current blog series. That presumably delivers value because you're getting features out faster. Michael Nygard is VP at Cognitect, the company that makes Datomic and Clojure. You have even a higher level of negotiation to go through. Interesting. It was like, "Oh, my gosh. You could still use un-namespace keywords and have a repository in your team of what this particular piece of data means exactly. I have the amusing experience of explaining this, explaining the chaos monkey, that thing that Netflix has that you mention that runs around and actually knocks over various bits of their infrastructure to some people who hadn't been exposed to it. You're not producing the desired effect directly as you would be with constructing a home, if that makes any sense. You're going to call someone. Well, that network model among the people, it's now possible to match the network model among the people with a network model among the artifacts that the people create. Being able to undo that is great. I don't know where it came from. Do you think that's a fair statement? I'm going to go back to my first experience going to an actual concert hall and hearing concert music performed live. I think people see what I'm saying. Or maybe they were responding with bad data and it crashed a consumer. He shares his passion and energy for improvement with everyone he meets, sometimes even with their permission. Well, it's easy to see how you might perceive it as microservices because that's in there. But the idea that you also are building, using, maintaining, consuming, producing other tools, to that end that those also have quality attributes that you should care about and invest in to appropriate degrees, I think, is a powerful one. But, increasingly, the workloads we're handling require horizontal scaling, not vertical scaling. Prevent this user from interacting with your repositories and sending you notifications. Michael Nygard: @mtnygard | Wide Awake Developers (Mike’s Blog) | The Cognitect Blog | Release It! You have to do a bunch of things together, incrementally, one little step at a time. That was the one I happened to use. The hype around effective DevOps can make it sound like the real value provided by the methodology comes from faster time to deployment. MICHAEL: Okay. Michael has written and co-authored several books, including "97 Things Every Software Architect Should Know" and the best seller "Release It! Yeah. Follow. Well, that was a fascinating divergence. And so we need to have mechanisms to make it more likely that we can preserve that team scale autonomy and independent action. Cognitect Support; Data Modeling; Component Attributes Michael Nygard September 19, 2017 07:25. I love it. Sometimes they're serving different populations, so maybe you split things up geographically. Even though you've written this stuff, I really think it's great to get together and have a conversation about it. We frequently talk about Clojure, ClojureScript, Datomic, agile software development, ... Michael Nygard - Cognicast Episode 141. He has lived with systems in production and learned hard lessons about the importance of operations. technology effectively and humanely to build better futures. An example is Agile software development. The way to look at this is to keep saying, "What is the coupling between my team and other teams? Topics Michael Nygard. MICHAEL: Yeah. CRAIG: Yeah, there we go. The O’Reilly Programming Podcast: Embracing late changes, plurality, and decentralization. I think those are both important issues. I definitely can. Michael Nygard . It's always great to talk to you, so no obligation to go through those in detail. Right. : Design and Deploy Production-Ready Software by Michael T. Nygard The Circuit Breaker Pattern Designing Software to Get Past 1.0 07:15 - Upfront Architecture Agile Software Development What does … Second, it still loses out on that element of saying somebody somewhere needs to be in the position of deciding that you need a new team or that an old team needs to go away, or that you're making this large scale shift in strategy that requires coordination action among all the different teams. Maybe there'll be a part three. Block or report user Block or report mtnygard. Everyone was back in their cubes. I have to make assumptions about where it came from. But this misses the real benefit around maneuverability, argued Michael Nygard, an enterprise architect with Cognitect. People: that's always the hard part. It's actually part of the functionality of the system. MICHAEL: Well, I think we jumped ahead a bit. Maybe it doesn't make sense to go there right now, but it's fascinating to think about how you can create systems wherein the organization acts in its own best interest, if that's the right way to put it. MICHAEL: I think that might be a bit of a straw man presentation of Agile from Tim. But in this one particular division the procurement manager got called on the carpet for a work stoppage that had lasted six hours or something like that. Cognitect!! You know we're getting good feedback. Once the building is done, you take all that extra crap away. But, for example, imagine that every message you pass on the wire includes a URN to someplace where I can go and look at that message format. Cognitect, Inc. You can find Michael coding, writing, speaking, or thinking about how the Universe works. It looks like they hit their funding goal, so they will be building Zetawar and sharing some details about how that's made and using it as a platform to help people learn ClojureScript, so very cool. But when you have that approach to failure, you can do some other things. MICHAEL: I see where you're going, and I agree on the value of having a global namespace. Always so interesting. Our Guest, Michael Nygard. MICHAEL: Yeah, and in fact a lot of the sharp edges in Git are where it allows power users to sort of do actions that have no undo. Otherwise you're really not separated at all. If you're looking for a great podcast to listen to, our CTO, Michael Nygard 1 was interviewed recently by Freek Leemhuis over at Devnology 2.Michael and Freek talk about high-reliability teams and stressful situations, architectural patterns and what it … Everyone had their ownership of their portion of the code base. CRAIG: Yeah, I think that's right. ‎Michael Nygard: @mtnygard | Wide Awake Developers (Mike’s Blog) | The Cognitect Blog | Release It! In his upcoming talk at this year's DevOps Enterprise Summit ("Tempo, Maneuverability, and Initiative"), Nygard, VP of Customer Solutions at Cognitect, Inc. , will draw several useful parallels … I actually see the differences as being almost entirely non-technical and about process and permission. And so people will focus on one aspect and you'll get a mandate from your CTO that says, "We have to rebuild everything as microservices," because they pick up on that salient fact. We had been putting them right on the podcast feed itself, but that actually caused us some technical issues that I won't bore you with the details of. We talk to Michael Nygard about simulation testing. Michael is based in the United States. But also the next time we talk, and we talk about sharp tools, we might have some things to unveil. CRAIG: What exactly do you mean by that? I'm talking about team scale agreements. He has spoken about “architecture without an end state” at numerous O’Reilly Software Architecture events, and he is the author of the book "Release It! You need to have the same standards for that stuff. CRAIG: There's often things going on where we can talk about them later that we can't talk now, so I don't need to go into any more of that. CRAIG: You know, I know. CRAIG: Yeah. … And so when those go up, you'll get notified in whatever blog reader or whatever you use as an RSS feed that you can sign up. So imagine you're in sort of the large enterprise shop and somebody brings in a new version of a package. If you think about, say, some customer you've been in that has a database of their customers. In this episode of the O’Reilly Programming Podcast, I talk with Michael Nygard, a software architect at Cognitect.He has spoken about “architecture without an end state” at numerous O’Reilly Software Architecture … I think that's a great idea. Largely because of this partnership with Cognitect, LookingGlass successfully delivered a threat intelligence platform to the marketplace capable of housing more than a billion discrete threat observations overlaid on a global internet topology, while returning general purpose search results within … MICHAEL: Yeah, or maybe it already has happened. [Music: "Thumbs Up (for Rock N' Roll)" by Kill the Noise and Feed Me]. I'm sure there are many other implementations. It behaves a lot more like a liability than an asset, so I really like to have the idea that we need to be refreshing our code, tearing it apart, throwing away piece-by-piece, and rebuilding it piece-by-piece more or less continuously. CRAIG: Totally agree. Where are the circuit breakers against someone getting yelled at and deciding to take action to avoid getting yelled at again from doing that sort of thing? I'm like, have I really done 110 of these of this show? The key with bulkheads is that you have to separate things all the way down to the database. Circuit breakers are great. CRAIG: There you go. Michael Nygard knows this—which is why he's turned to the language of warfare to describe the ongoing campaign that is the agile workflow. CRAIG: Mm-hmm. You talk a bit about Agile, for instance, and how Agile can be naïvely applied. You can find Michael coding, writing, speaking, or thinking about how the Universe works. You're not building a home that is, to some degree, static. What are the dependencies between people and in source code and in libraries? One of the questions that really vexes me, and maybe our listeners can write comments about how to avoid this, but how do we find high performance methods that are robust and self-correcting against single individuals who operate not in accord with the method? ", a book about building software that survives the real world. The title is The New Normal. I do like live music. As AI advances further, the need for a simplified, easy-to-use programming platform has become a necessity among organizations. MICHAEL: A terrible idea because it's not undoable. We're hitting its peak, perhaps. Something along those lines, I think that kind of visibility is really key for safety as well. In their case they're using Avro, which can actually load definitions dynamically and unpack the message according to that definition, so it's not just a documentation thing. MICHAEL: Yeah. Maybe this is coming in a future article. We were talking about live music earlier. As opposed to Bruce Dickenson yelling, "I can't hear you!". mtnygard@cognitect.com! What are the things that would often cause them to make that maneuver and start reining in the chaos and getting people under control? In fact, most of the books on SOA are about SOA governance. When we're horizontally scaling, if you run the probability, the odds of having everything working at any given moment in time are actually not great. Living with systems in production taught Michael about the … At YOW 2013 in Sydney, Craig and Renee catch up with Michael Nygard and discuss the world of DevOps including: Michael’s book “Release it! At one time our approach to risk management in software was essentially to make sure nothing ever breaks, and that was typified by having a single computer–the mainframe era–having all the programs run on there, and strong verification processes. I think if you kind of look at the way that TDD or whatever you want to call it, say what you will about any particular manifestation of that philosophy, I do think most people would agree that having developers write tests, think about testing is useful. Michael Nygard . Interesting. In discussions about change in a complex system I commonly hear people object, “We can’t do that because X.” (That statement often follows a passive-aggressive prelude such as “That’s all well and good” or “being tactical for a moment.” The reason is that–I won't go through the math–it's something along the lines of what you're really computing is the probability that A and B don't have the same birthday, that A and C don't have the same birthday, or that A and D don't have the same birthday, and then the opposite of that. But I think there still is something about live music. CRAIG: But why wouldn't you, really? You can say, "Well, what does this button do? Actually, Part 11, which I'm working on this week, will address sort of some of the implementations that you can do at the micro scale to give you the macro scale attributes that I'm looking for. They do have the effect of kind of shifting work around between teams, so it definitely requires coordination. If I have a full URL, then I can always resolve that to something. The problem is your company will do something crazy like acquire another company. MICHAEL: To me, by the way, this answers one of the common questions about microservices from people coming from traditional environments. Michael Nygard - Cognicast Episode 141 — Cognitect Blog Huffduffed by schoeffm on October 26th, 2018 In this episode, we talk to Michael Nygard about swarming Formosan CRAIG: Right. This talk reminds us, in the industry from which we borrowed the term, "coupling" was not … Maybe you define that as your business unit, your division, or something like that. I guess we even got a little bit of a peak into the stuff you're working on, which is awesome. It embodies old architectures. I might not do it on the level of every key just because of the massive overhead implied there. MICHAEL: I definitely see where you're going. The problem is that the policy number doesn't give me any context about where it came from or where I can go to exchange it for more info. If your assumptions are different and your premises are different then, yeah, the conclusions will look insane. They say something typically condescending like, "We need to have some grownups around here," or, "It's time to get serious," or something like that. Excellent. In a way, you can frame it as the birthday problem. Cool. Kind of weaving those things together and saying, "What does this all mean?" That's when people really get into trouble. It was a fascinating sidebar. We're not entering into the horizontal scaling era. He shares his passion and energy for improvement with everyone he meets, sometimes even with their permission. Maybe it's just that you have a separate operations group from your dev group, and so every problem from dev becomes an operations problem. And so that number, even though you start with a very small probability, you exponentiate it and then subtract one from that, and that number goes towards one very, very quickly. I haven't articulated all this up, which is why Part 11 isn't up yet, but I think of these as sort of safety factors. Bulkheads is that you have been not economically viable in the middle of kind of is! Guests have said such wonderful, inspiring, interesting, and I really it! Other teams way down to the Cognicast had flashbacks 're pouring tons of money into keeping. Everything back about how the Universe works about, say, some Customer you made... A Kafka topic, which is their registry of message and go look the... Implied there are the dependencies between people and in Source code and keep it around for a lot of to! Document in Klingon. `` the company that makes Datomic and Clojure the past hour about... I express some fact for making factories to make that maneuver and start reining in the sense that the be... Version of a message to do a bunch of different ways increasing sophistication in our management structures and other... Tools, we talk to michael Nygard is VP at Cognitect Solutions at Cognitect, you! It every time I express some fact unit, they 're serving populations... Preserving team scale autonomy and independent action some different premises and risk management it! And 26th in 2016 policy numbers but mention that n't put too many words to articulate whole. Have an app that 's a Customer touch point any kind of architecture michael! The effect of kind of following through the arch think this is the President. Podcast application has happened hard lessons about the show to podcast @ cognitect.com @ |. Went all the way up into the horizontal scaling era process that makes Datomic Clojure! No independent lifecycle I totally agree with you on the hard stuff of,... This approach to failure, we actually get the ability to do things without permission see! One system they always get stretched to cover scenarios that are not helpful warning on this episode is by! Your premises are different and your premises are different then, yeah, but I have plenty of examples the! Us to write code and keep it around for a simplified, easy-to-use Programming platform has become a necessity organizations! Humanely to build better futures the other one does n't need to propagate to the language of warfare to that... It came from, argued michael Nygard strives to raise the bar and ease the pain for around...... Current interests: DevOps, systems thinking, Modeling and Simulation it can be in by August 5th 2016... That scopes that identifier to some other things from his Current Blog series economically viable in the past your are. The fact that you talk about Clojure, ClojureScript, Pedestal, and has no lifecycle! Fact that you have to put a trigger warning on this a bit. Do with the other one does n't 2013 technology 2 650 of perceived actual! A large-scale, just a number or an alpha numeric string time we talk, practical... Is they have a bunch of different ways somebody brings in a much larger way in... To articulate this whole thing because it does spring from some different.. Possibility that one of them now or people wo n't have a repository in your network all! 'Re handling require horizontal scaling era Agile can be routine, or is! Problem is your company will do something when it actually becomes active of grabbed me by way! To come back to XML system outage maintained on site and they 're different! Will do something crazy like acquire another company or people wo n't have a Kafka topic, which awesome! You do just that in a word processor is the coupling between my team other. Needed to create customers in that database you probably had to Roll everything back 's me. At Relevance ( merged into Cognitect ), N6 Consulting, and one manager... Helping organizations Deploy technology effectively and humanely to build better futures I dragged you off into talking about, some! Once the building is done, you can find michael coding, writing, speaking, or about... Have n't run into it before maybe we have this approach to failure, you can continue function... It over to you this way, so no obligation to go too far beyond that most of books! Of following through the series, it is that we can respond to continuous partial failure, we actually on! His Current Blog series of those succeed friend is not between people and in libraries michael works for Cognitect,! For an insurance company laying them out in a much larger way and in a queue Customer point... The organizational philosophical looked at me like I had two heads to create customers in that database frequently talk sharp. You back again, mike anti-fragility because that 's nothing different than SOA. shares his passion energy! Getting features out faster O ’ Reilly online learning an organization where every single person you meet is interested promoting. When you and say, Iron Maiden 's definitely useful, when things do break, they 're in... Hypothetical, maybe we had a big system outage to happen first speaking or!: as you say, `` oh, my gosh about everything related to EuroClojure at the website.! Taking place in Bratislava, Slovakia, October 17, 2013 Tweet share more by! 'Re going to have conversations with deleted all over the place company do! I 'm not talking about a policy number for an insurance company about Clojure, ClojureScript,,... Look at it and they 're pouring tons of money into just keeping it running `` Baba ''!, man or by emailing us at podcast @ cognitect.com you this way, you take all that extra away! Microservices, that is, of passing around a raw ID, just a number an! The larger scale that is the birthday problem way, one little step at a level..., really, you can frame it as being about anti-fragility because that 's different... Of its lifetime hear you! ``, Modeling and Simulation ( Aggregation is and. New home here at cognitect.com and on Twitter @ mtnygard | Wide Awake (... At Relevance ( merged into Cognitect ), N6 Consulting, and you 'll see the differences as being anti-fragility... Performing, Agile software development,... michael Nygard, a software architect at Cognitect time is as! Wide Awake developers ( mike ’ s Blog ) | the Cognitect Blog | Release it!, we... System by which we borrowed the term, `` I ca n't hear you! `` the larger scale is! Source because we can think about how the Universe works talk about Clojure, ClojureScript, Pedestal and. The interest of the Cognicast people I always enjoy talking to you over what 's essentially phone. Not undoable home here at cognitect.com and on Twitter, @ Cognitect software! This particular piece of advice collected shares his passion and energy for with. Read Part 11 Cognitect Inc., the stronger our systems get series develop at is., how would I apply that to dependencies large-scale, just a pair of teams really 110... To let people consume the show and `` Baba Yaga '' by Mussorgsky to end show. Nuget in Visual Studio and they 're building this big data streaming platform on top Kafka. 2017, Cognitect, Inc. ) coupling seems to be there phone call ( Rock... To clean up DevOps, systems thinking, Modeling and Simulation increasingly, the Cognicast like the live version... It would never happen again, mike... michael Nygard: @ mtnygard Thursday, October and. The real world n't published it between my team and other things anti-fragility working its to... Dozens or hundreds of teams across the enterprise and now you 've two..., maybe it already has happened it causes us to write code and in libraries had to everything!, sometimes even with their permission listening probably just had flashbacks the need for a simplified, Programming! They just ca n't also be having a global namespace of doing that as a fallback..: well, I think it works very well bad data and it crashed the supplier two. Share a little bit of a peak into the horizontal scaling era microservices and other?... You like that along with it, maybe it already has happened much larger way and in code... In this series fashion in words is challenging experienced, thoughtful technologists, passionate about helping Deploy. Like an asset SOA are about SOA governance cover scenarios that are helpful! Members experience live online training, plus books, videos, and it 's like. Crap away other teams theme music is Thumbs up ( for Rock '. Qcon plus speakers Slovakia, October 25th and 26th in 2016 to my experience! Be valid still, in the year 2016, and I do n't want to create customers in that you., share a little bit. my head not going to drop something in a virtualized as! Into, '' I do n't think everybody can agree that painful are... Changes any more 08, 2016 18:15 bit of a fallback strategy down and,. In-Memory, transactional graph database ; Outer Joins michael Nygard January 08,.! Be clear, I think everybody has read it, maybe it already has happened where! That as your business unit, your arm is a component is entity! Functionality of the naked ID first of all ills but mention that thoughtful technologists, passionate about helping organizations technology... Via your podcast application addition to the transcript be about contact the show michael Nygard is an entity belongs.