Summary

Platforms are often represented in enterprise architectures, “marchitectures,” or as I like to call them, “burgers.” Today, I walk through some past, great burgers, from CORBA, to J2EE, to Cloud Foundry, and more. In doing so, I over some advice about how to find and care for your burger, especially when it comes to keeping your burger fresh.

Planned on topics

All the great burgers.
We’re talking about distributed applications – an application and the services (“backend,” “middleware,” database, ERP-system, etc.) run as their own application, accessed over an API (usually over a network, but could be on the same box, too).
What is it in service of? Software for large organizations: enterprise architectures.
Examples:
Older Delta Airlines, as in Enterprise Architecture as Strategy, 2006:
Generic banking:
Early on, CORBA. Hard nope.
J2EE.
Then SOA; RedMonk COA.
Me on PaaS in 2011.
We realized that ops was a problem, and part of the application (Shafer, 2005, and all the rest of the DevOps people).
Overcoming Infrastructure Obstacles When Depoying Product-Ready Kubernetes, Nathan LeClaire (unplublised/in review): “fuzzy seperation between how the app is defined and how the app is run.”
Brian Gracley finally defines the cloud native burger:
“Structured-” vs “Unstructured Platforms” framing.
The burger with all the toppings:
A big burger with all the vendors:
~2017 PCF diagram: .
New cloud native burger – Janakiram MSV, The New Stack, Oct. 2020:
This week’s burger, Digital Ocean’s App Platform, in feature matrix pricing form!
Protecting your burger:
Guard against bloat and innovation slow-down – Spring has always been a hedge for this in Java.
Vendors should do enterprise product management.
Industry (defacto) standard: broader knowledge, staff interest, bigger partner/integration ecosystem.
Always sniff out the vision – the implicit/explicit appdev/ALM model; “shift-left”‘ing; enterprise features over “don’t do that” (governance, AD, har, har).