Can we take that governance and work with the platform team to codify, to automate that which they were doing on a per application basis – that’s, quiet frankly slowing down the delivery of the software – can we take that governance and can we have them work with the platform team to codfiy, to actually automate on a per application basis, have them expose that as a service on the platform
–Cornelia Davis on governance and cloud-native, “Who Does What? Mapping Cloud Foundry Activities and Entitlements to IT Roles,” August 2016
In other words: you should not only automate the audit three-ring binders of compliance, but enforce as much as possible in the platform.
The rest of the talk is good stuff on how think through re-arranging your organization to be all DevOps-y, with the help of Pivotal Cloud Platform to automate all the infrastructure and middleware stuff:
My colleague Richard has a nice post suggesting the new functions enterprise architects can play in a cloud-native organization. I like this one in particular, help make the change:
Champion new team organization patterns. As an architect, you can bring developers and operations teams together. Recognize that functional silos slow down delivery. A DevOps-type approach really works. Architects are perfectly positioned to pioneer new team structures that increase velocity and customer attentiveness.
It’s brief, but there’s plenty of other good chunks of advice in there.
Source: How to Remaster Enterprise Architecture for a Cloud-Native World
Earlier this month I did a webinar with Nick at 451. He does a great job summarizing all the digital hoopla going around and I finish up with, predictably, why and how Pivotal can help out there, along with a few customer examples. Check it out!
Check out this talk on “cloud-native”:
We’ve got all your answers to “what exactly is ‘cloud-native’?” in this episode with special guests Pivotal’s Kenny Bastani and RedMonk’s James Governor. Kenny gives us a good overview of what cloud-native is, as Coté summarizes it: handling the configuration and automation for your applications along with all the supporting frameworks and platforms to do that. We then discuss the process (“culture”) angle, the origin of Spring Boot, the concept of “lock-in,” and if public cloud is needed or not. Bonus: serverless talk!
In this week’s episode, Richard and I talk with Dino about the work Pivotal does to help companies quickly start migrating applications to Pivotal Cloud Foundry. Check it out, and subscribe if you haven’t already.
What’s the best way to categorize and prioritize your IT projects? Splitting them up between systems of record (ERP) and systems of engagement (user-facing apps) is a popular mode of thinking, highly related to bi-modal IT. In this episode, guest Ian Andrews explains why this framing is a bad idea and offers a value-driven way of thinking about it instead, along with plenty of commentary from Coté and Richard.
Subscribe to the podcast feed, check it out in Soundcloud, or listen below:
Subscribe, follow, feedback
- As always, we try to avoid politics. However, if you’re interested, check out Coté’s summery of the refugee madness over this weekend, it wraps up comments from several people. Also, Pivotal had a very heartening internal discussion of it.
- Also, in the depressing vein, Coté reviews some books on “automation,” which John Allspaw rightly says should be called “new technology,” fair enough; the 1983 paper on automation and humans that Allspaw recommends is a good read too.
- Coté will at DevOpsDays CLT next week. If you’re quick, we have some spare passes. Email firstname.lastname@example.org. He better put together that talk!
- CF Summit coming up: June, 13th to 15th. The CFP is open until Feb 17th – come talk at!
Ian Andrews on bimodal, systems of engagement vs. systems of record
- Systems of engagement vs systems of record – why is this distinction not helpful based on Ian’s conversations with actual customers. And, of course, bimodal.
- Spring Boot’s story, and Spring Cloud.
- Contrasting those with JEE needs shifting. That InfoQ piece Ian references.
One of your favorite technologies is on the death wagon, again. Gartner recently recommended avoiding JEE for new, cloud native application development. This predictably kicked up all sorts of push-back from the JEE stalwarts. In this episode we discuss the report, the responses, and all the context to figure out what to make of all this. Spoiler: JEE isn’t dead, as ever, it’s just a part of the ongoing gumbo that is a Java application.
Subscribe, follow, feedback
Gartner on JEE for Cloud Native
The new version of Pivotal Cloud Foundry (“PCF” as folks like to say) is out. It has a whole slew of updates across the board.
My selective highlights:
- Google Cloud & Azure support, so you’re all multi-cloud ready (still with OpenStack, VMware, and AWS support).
- Will run 250,000 containers concurrently; in addition to scaling based on CPU usage, you can now auto-scale on HTTP Latency and HTTP Throughput.
- Updates to Spring Cloud, Zipkin, and Spring Boot Actuators for diagnostic stuff.
- MySQL updates, esp. for multi-zone support in AWS.
- “Tasks” one time processes that are an initial cut at “serverless”
- A slew of security updates.
See more – much more – features and details in Jared’s blog post wrapping the release up.
I get asked to talk on DevOps a lot. Here’s my current (late 2016 and 2017) presentation, going over the why’s, the how’s, the technologies, and the meatware that supports including some best and worst practices based on what Pivotal customers do. See the slides.
Also, here’s a more blatantly pro-Pivotal (and longer) version that you might have seen, esp. if the talk title was something like “Digital Transformation in the Streets.”
Much of it draws a lot on my cloud native journey booklets as well.
Like reading about doing agile, DevOps, and “cloud native” in the real world? Help me finish up my current booklet on that topic by reviewing my almost finished draft.
I’ve been working on this since around August of this year. I’m almost done! There’s some of my content you might have seen around the web here and there, but most of it is new. I’ve tried to wrap up all the common topics I talk about with large organizations and put in as many cases and anecdotes – proof and data! – from “donkey” organizations as possible.
Help me get more eyes on this, and also read an “early edition” before you have to get your boy Johnny Leadgen on the case.