@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
@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.
@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.
@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.
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.
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.
@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 🏏🏴
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 👇
https://t.co/yghOGO2tOb
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.
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?