Gary Olliffe

@gigaclear you have a problem… whole community without service here in north bucks… and no after hours support contact.

@hpgrahsl 150+ OSS plug-ins seems like a low number... but it depends on how you count ... I'm at 210+ and 220+ in total OSS collating across multiple sources. It makes for some pretty cool dependency graph. Sadly not at #BackstageCon #KubeConEU this year. #BuildWithGartner @Gartner

#BackstageCon just officially started as part of the #CNCF co-located events right here at #KubeConEU 🇫🇷

@fintanr @cloudfoundry A: The scope of 'platform' expanded to include all of the "outer architecture" needed to continuously deploy and operate many (micro)services...and also too much renaming existing i&o/"devops" teams.

As I listen to some of the staffing recommendations (ie x% of staff, where x can be in excess of 10%) out there for platform engineering teams in enterprises I am wondering how did we drift so far from the really low ratios @cloudfoundry teams were (and some still are) getting.

@fintanr @nmeans @monktoberfest Awesome...Great session.

This was a stunningly good talk by @nmeans at @monktoberfest. Well worth a watch.

@fintanr @googlecloud @rseroter Nice pithy way of explaining the value of platforms to devs/engineers 👌

The Modernization Imperative: Shifting left is for suckers. Shift down instead @googlecloud cloud.google.com/blog/products/… << in which @rseroter channels what feels like the (often ignored) advice given in 100s of inquiries I had in $oldjob.

@fintanr @Google At least they didn't send it to the Google Graveyard

@fintanr Been trying to keep folks focused on what platform engineering means but that damn word "platform" is just but that too tempting to hitch another wagon (or prefix) to.

We appear to have entered the era of platform engineering taxonomies. That human ability to overcomplicate everything in order to fit it into the past rather than looking towards the future, is, as always, infinite.

@fintanr Right...this Prime team have refactored their architecture based on current constraints and knowledge gleaned from developing and operating their prior architecture. Big shrug.

My former colleague at Gartner, @garyolliffe, has given iterations of a talk called “You are not Netflix” for six, seven years. It is equally applicable to the hullabaloo about the Amazon Prime Video post going on today. If you are at that scale you have different constraints.

Some great sessions at #QConLondon today...but... here's a tip if you are presenting tomorrow... please double your font sizes! So many slides today with unreadable or barely readable text, even from 6th row.

Great to be back at #QConLondon... brain in gear and ready to go!

Trying to address tech debt in your legacy apps by "refactoring" to microservices?...proceed with extreme caution... Converting your monolithic big ball of mud into a big distributed ball of mud is like paying off your mortgage with your credit card.

@boyney123 Great post, same issues with any kind of interface at scale. Treat events as you would any other API - abstract the implementation (source) detail, plan your versioning, catalog the contracts, apply policy to access.

When scaling event-driven architectures, common issues arise Thought it was me... but speaking to folks these issues keep coming up over and over... e.g Discoverability? Leaky events? Coupling? Implementation > Behaviour? Visual & resources to help 👇 serverlessland.com/event-driven-a…

@samnewman I feel sad that i saw "loving the fielding maps..." in the notification and thought this was about an old REST API design approach i'd missed. Cricket was a nice surprise 🏏🏴󠁧󠁢󠁥󠁮󠁧󠁿

Loving the fielding maps for the Women’s #T20WorldCup2023. Showing not just the position, but also the expected ground the fielders can cover. Very cool.

@MohammadSH @rseroter @richwatson Sometimes quality and quantity do go hand in hand 😀. Let us know if you've got feedback.

@rseroter @garyolliffe @richwatson Will be waiting for your tldr version 😅

76 minutes to read this new Gartner ($$) report on platform engineering? Come on, no way. I have things to do. Oh, @garyolliffe and @richwatson wrote it? CLEAR MY CALENDAR.

Into event-driven architectures? Want to learn more? Last week I started to build EDA Visuals and now have 20 bite sizes visuals to help you learn. I have now compressed these into PDF format for you all to download for free 🚀 Hope it helps 👇 serverlessland.com/event-driven-a…

My usual beef with reference architectures is that they launder the creators' assumptions into "best practices" without helping you put your own needs in context. Turns out there's a cheat code to get past this problem, and the team that built "Emblem Giving" found it:

@Gartner_inc @mbrasier @garyolliffe Now @garyolliffe is just showing off, as this @Gartner_inc report—Adopt Platform Engineering to Improve the Developer Experience—is a fantastic blueprint for those that want to set up a platform team correctly.

RIP @ProgrammableWeb : ProgrammableWeb is Being Retired... thanks to those who created it and sustained it for so long. programmableweb.com/news/programma…

EDA question for you all, something I'm curious about.... As you scale event-driven solutions within your org, what are the problems you face beyond the initial setup?

I don’t often create OpenAPI specification but when I do it: