Software Architecture for Agile Enterprises

Software Architecture for Agile Enterprises INNOQ Online Technology Lunch,  May
2020 Stefan Tilkov, @stilkov  [email protected] Image by Michael Gaida from Pixabay

www.innoq.com OFFICES Monheim Berlin Offenbach Munich Hamburg Zurich FACTS ~150
employees Privately owned Vendor-independent SERVICES Strategy & technology consulting Digital business models Software architecture & development Digital platforms & infrastructures Knowledge transfer, coaching & trainings CLIENTS Finance Telecommunications Logistics E-commerce Fortune 500 SMBs Startups

@stilkov architecture/ ˈɑr kɪˌtɛk tʃər /:  noun A fancy word for the
stuff you should not ignore

Modularization Autonomy End-to-end responsibility

@stilkov Awesome Shop CMS Archive General Ledger Print Shop HR

Context

Invoicing Accounting Auth Catalog Checkout & Order Search

Invoicing Accounting Auth Catalog Checkout & Order Search Domain Architecture

@stilkov Invoicing Accounting Auth Catalog Checkout & Order Search

@stilkov

@stilkov Macro Architecture

@stilkov Ruby on Rails MySQL Java Spring Boot OSS Product
COTS Java Spring Boot NodeJS ElasticSearch

@stilkov Ruby on Rails MySQL Java Spring Boot OSS Product
COTS Java Spring Boot NodeJS ElasticSearch Micro Architecture

@stilkov Coming up with the “right” system boundaries is an
architecture activity that must be done first

@stilkov Managing dependencies is the most important ongoing architecture task

@stilkov You cannot decide to not have an architecture; if
you don’t actively create it, be prepared to deal with the one that emerges

number of  developers strength of   decoupling methods modules components
μservices systems

From a layered system … System Logic Data UI Module
Module Module

… to a system of systems System System System Logic
Data UI Logic Data UI Logic Data UI

Pattern: Evolutionary Architecture @stilkov

@stilkov Invoicing Accounting Auth Catalog Checkout & Order Search Team
Architecture

@stilkov Conway’s Law: Organization → Architecture “Organizations which design systems
are constrained to produce systems which are copies of the communication structures of these organizations.”  – M.E. Conway

@stilkov If your goal is to support autonomous teams, architecture
is an essential ingredient

@stilkov Size is the #1 enemy of agility; keep your
systems as small as you reasonably can (but no smaller)

@stilkov Extremely loose coupling requires very few rules, but those
need to be enforced strictly

Pattern: Regulated Market @stilkov Troy / CC BY-SA (https://creativecommons.org/licenses/by-sa/2.0)

@stilkov Pattern: Autonomous Cells Stakeholder Stakeholder Stakeholder Biz Dev Ops
Biz Dev Ops Biz Dev Ops

@stilkov Not every person has to become a full-stack developer,
but every team should be a full-stack team

Recommendations

@stilkov 1. Establish autonomous teams as key ingredient

@stilkov 2. Manage the inter-dependencies of organization and architecture

@stilkov 3. Create evolvable structures and strictly maintain few rules

Krischerstr. 100 40789 Monheim am Rhein Germany +49 2173 3366-0
Ohlauer Str. 43 10999 Berlin Germany +49 2173 3366-0 Ludwigstr. 180E 63067 Offenbach Germany +49 2173 3366-0 Kreuzstr. 16 80331 München Germany +49 2173 3366-0 Hermannstrasse 13 20095 Hamburg Germany +49 2173 3366-0 Gewerbestr. 11 CH-6330 Cham Switzerland +41 41 743 0116 innoQ Deutschland GmbH innoQ Schweiz GmbH www.innoq.com Thank you! Any questions? Stefan Tilkov @stilkov  [email protected]  +49 170 471 2625

Software Architecture for Agile Enterprises

Software Architecture for Agile Enterprises

More Decks by Stefan Tilkov

Other Decks in Technology

Featured

Transcript