It’s another in the Matt Curry discussions sub-series! We discuss how enterprise are shifting over to a microservices approach, or not. As Matt explains:

We discuss what the deal is with Canadian whiskey and then talk about why we like The Economist.

Your pals, @cowboyd & @cote.

IoT will be big by 2035, a trillion devices driving a $1tn of spend/year, according to this paper. How does one come to that figure, and what exactly is IoT. Even better, how would you put together the business case to justify doing an IoT project? Well, you’ll get an average of 5x returns, the paper says, so that’s a compelling start. Also, you should buy some ARM chips. Put together by one of ARM’s investor relations people, this paper is squarely targeted a money people interested in IoT and ARM.

See also the raw notes on the paper, references, and more details on the paper. Also, of course, available as a PDF attached here.

This paper in question (attached here, as well) was suggested by Alek.

As always, thanks for being a patron of Software Defined Talk, it's super-encouraging and meaningful. If you liked this episode, perhaps send the attached PDF (as all great white papers are transmitted) and encourage your friends to check out both Software Defined Talk and to become a patron get our exegesis episodes.

Please tell us what you think and suggest any white papers, talks, press releases, or other tech world ephemera that'd be fun to over-analyze!

This week, Brandon and Coté talk analyze Coté's 2016 stump-speech, Not a DevOps Talk. We talk about the process of putting together a talk like this, how it flows, and the desired effect and rhetoric behind it all.

See the extensive show notes and much more detail in the attached PDF or online. There's also a bonus write-up about two of Coté's Register columns.

As always, thanks for being a patron of Software Defined Talk, it's super-encouraging and meaningful. If you liked this episode, perhaps send the attached PDF (as all great white papers are transmitted) and encourage your friends to check out both Software Defined Talk and to become a patron get our exegesis episodes.

Please tell us what you think and suggest any white papers, talks, press releases, or other tech world ephemera that'd be fun to over-analyze!

Let’s finally get to the punchline on this “cloud-native enterprise architect” quest. Here, Matt Curry, Andrew Clay Shafer, and I discuss the things that would motivate such a role and try to chart out what functions the cloud-native EA would serve. This still doesn’t answer the question perfectly, but it does point towards good why’s and even some how’s. We do alright at trying to pull it all together.

Our first white paper review, starting with "what is digital, and what are/should enterprises do about it. See the detailed notes on it, either in the attached PDF, or in Dropbox Paper.

You should be able to find your members only RSS feed and add it to your podcast listener.

First, thanks to our initial, super-fan handful of members who'll be getting this.

Second, tell us if you like this show, format, and, if so, some studies/papers you'd like us to go over.

Third, if you can help us promote this, and grow membership (or at least envy that you get access to!), that'd be awesome. Feel free to email the PDF around, a link the notes, or even the MP3 if you want to be a bit of a privateer.

What’s the “business” side of enterprise architecture? And how does EA’ing start mapping to DevOps, cloud-native, and all the new stuff? In part one of this discussion, I talk with Matt Walburn about how EA’s fit into The Business.

Special Guest: Matt Walburn.

In this Drunk and Retired cameo episode: What's up with Irish and Italian names, and why is the Irish brand so much bigger than the Scottish brand? Also, it seems like there's a lot to learn from 2,000 years of Europeans fighting. Charles and Coté quickly meander through all of this.

Links:

• Ongoing topics list — Rolling list of ideas for things to talk about here.
• Gulf Shores, Alabama — A fine place for a beach vacation.
• The Horse of Pride — It’s like _Hillbilly Elegy_, but for 20th century France.
• frontmacs.el — "A package-based, web-centric, customizable, awesome-by-default, acceptance-tested Emacs distribution curated by your friends at Frontside."
• swiper.el — "Ivy - a generic completion frontend for Emacs, Swiper - isearch with an overview, and more. Oh, man!"

Without a build pipeline, you might as well pack it up and go home. Matt Curry and I talk about his team’s experience with putting a pipeline in place and dip a bit into how Concourse and other options, like Jenkins. Matt also goes over some of the common meatware barriers to getting CI/CD in place.

Find us here: @mattjcurry and @cote.

All these cloud-native apps don’t magically figure out how to talk with each other themselves. They need to usual help with finding each other (registries) and then mediating and managing their ongoing “chatter” with one-another (API gateways). While killing time at the Pivotal booth at OSCON, I talked with Spencer Gibb who works on these things and more in Spring.