Software Architecture as Systems Dissolve

Slide 1

Slide 1 text

Software Architecture as Systems Dissolve   SATURN 2018 Eoin Woods - Endava  @eoinwoodz

Slide 2

Slide 2 text

Thank You Eltjo Poort for nominating me and for   your contributions to the ﬁeld

Slide 3

Slide 3 text

Thank You Nick Rozanski for long term collaboration on software architecture

Slide 4

Slide 4 text

Thank You

Slide 5

Slide 5 text

Who am I? •Eoin Woods • CTO at Endava • 10 years in product development - Bull, Sybase, InterTrust • 10 years in capital markets applications - UBS and BGI •Software engineer, then architect, now CTO •Author, editor, speaker, community guy

Slide 6

Slide 6 text

Systems are Dissolving

Slide 7

Slide 7 text

https://commons.wikimedia.org/wiki/File:Sodium-chloride-3D-ionic.png

Slide 8

Slide 8 text

https://commons.wikimedia.org/wiki/File:Glycine-condensation-2-3D-balls.png

Slide 9

Slide 9 text

https://www.dreamstime.com/stock-illustration-oxytocin-molecule-isolated-white-model-hormone-produced-naturally-large-amounts-childbirth-causing-image51747855

Slide 10

Slide 10 text

Our Five Ages Intelligent  Connected  (2020s) Internet  is the System  (2010s) Internet  Connected  (2000s) Distributed  Monoliths  (1990s) Monolithic  (1980s)

Slide 11

Slide 11 text

Our History

Slide 12

Slide 12 text

Monolithic •Structuring of programs •Batch processing dominates •Fundamentals of modularisation •Architecture a vendor concern https://mtm2017.mybluemix.net/part_two/part_two_ch04.html

Slide 13

Slide 13 text

Distributed Monoliths •Client + Server + Database •“Batch” to “Online” •Software Architecture basics •Architectural style from vendors

Slide 14

Slide 14 text

Internet Connected •CS + Internet connection •“Online” to “Always On” •Software Architecture explosion •Vendors sell “NFR” boxes

Slide 15

Slide 15 text

Current Era

Slide 16

Slide 16 text

Internet as the System https://www.google.com/about/datacenters/gallery/ •Mobile UI + APIs •“Always On” to “Access Anywhere” •Software architecture becomes dynamic •Vendors sell “platforms” (PaaS)

Slide 17

Slide 17 text

Architectural Drivers Constant Competition => Continuous Development &   100% Uptime Unknown Users => Measurement of Behaviour Unpredictable Demand => Dynamic Response to Load Part of the Internet => Consumable by Systems Visible from Anywhere => Constant Attack Threat Accessed Globally => Compliant Everywhere!

Slide 18

Slide 18 text

New Principles •Evolve continually •Respond dynamically •Analyse don’t ask •An API for everything •Secure by Design •Internationalise instinctively

Slide 19

Slide 19 text

New Practices •Continuous Delivery •Allow modular evolution •“Cloud” ﬁrst •Measurement a basic service •Structure around “public” APIs •Build to be securable

Slide 20

Slide 20 text

On the Future

Slide 21

Slide 21 text

Intelligent Connected

Slide 22

Slide 22 text

Intelligent Connected •Data & Algorithms => Qualities •“Access Anywhere” to  “Intelligent Assistance” •Architecture Seen at Runtime •Vendors sell “intelligent behaviour” Our future as software architects … http://www.geomarketing.com/what-marketers-need-to-know-about-the-world-of-connected-intelligence

Slide 23

Slide 23 text

Intelligent Connected Less More Structural Design Data and Algorithm Design Deﬁned Structure Emergent Structure Decisions Principles, Policies, Algorithms Certainty Probability Operational Processes Operational Policy & Automation How will it aﬀect software architecture?

Slide 24

Slide 24 text

In Summary

Slide 25

Slide 25 text

Our Five Ages Intelligent  Connected  (2020s) Internet  is the System  (2010s) Internet  Connected  (2000s) Distributed  Monoliths  (1990s) Monolithic  (1980s)

Slide 26

Slide 26 text

The future of software architecture has never been more exciting …   or perhaps less certain

Slide 27

Slide 27 text

Thank you Eoin Woods  Endava  eoin.woods@endava.com @eoinwoodz