b'

Let\\u2019s finally get to the punchline on this \\u201ccloud-native enterprise architect\\u201d 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\\u2019t answer the question perfectly, but it does point towards good why\\u2019s and even some how\\u2019s. We do alright at trying to pull it all together.

Rough Outline

\\n
• Business \\u201coutcomes.\\u201d
\\n
• \\u201cSo what is it you\\u2019d say you do here?\\u201d
\\n
• Marketing and sales for tech decision making - getting budget, etc.
\\n
• The EA Strawperson - biz/IT alignment, governance, proscribing stacks
\\n
• Risk-modeling and procurement costs get better
\\n
• EA as the ROI whisperer.
\\n
• SRE book discussions, Pivotal Conversations #58 (Andrew and Cot\\xe9).
\\n
• The technology, and what\\u2019s new? AWS RDS as an (almost) end-to-end example.
\\n
• So, EA\\u2019s jobs to this point: business stuff\\u2026 versus defining the platform and tech choices (e.g., \\u201cuse this pagination library or die!\\u201d).
\\n
• But: product people do the business stuff\\u2026 you prescribe one platform/PaaS\\u2026 and then most teams now choose their own stuff above the platform.
\\n
• And doesn\\u2019t microservices do the rest\\u2026?
\\n
• Cloud-native EA\\u2019s probably spend a lot more attention to process, like SRE-thinking\\u2026 reducing duplication of services\\u2026 someone has to have a global, big picture view of everything.
\\n
• Being a change agent: boot-strapping to this DevOps/cloud-native/blah blah
\\n
• The ultimate goal: the business wants to evolve quickly, try new things to try to grow and defend itself quicker; the IT must work, or, at least, be resilient; I don\\u2019t want to pay a lot for this muffler; making it easy to do the right thing.\\n# Background
\\n
• Past discussions on cloud-native EA: Pivotal Conversations #72 and Cot\\xe9 Show #36.
\\n
• Some rough notes on research.
\\n
• Books: Enterprise Architecture as Strategy and Continuous Architecture.
\\n