Återblick, hur fungerar Event sourcing?
Hur fungerar en event store?
Varför fungerar inte traditionella Event stores bra i molnet?
Hur vi undviker DTC och varför?
Hur vi använder aggregater och delvis som actors.
Kommutativa uppdateringar mot idempotenta
Projectioner och vyer.
Konsistenta och inkonsistenta domän modeller!
Uniqueness krav och varför det oftast inte är ett konsistent beslut
Och allt annat som finns kommer upp
'Let´s Go Get Small' features freeskier Dave Treadway as he, together with Henrik Windstedt, venture way out into the Canadian coast range on snowmobiles. Their mission? To explore. To simply see what's on the other side of the next mountain. To see what's possible on skis. Watch them push limits in order to explore the unexplored, all while feeling really small in the vast territory that surrounds them.
Directed by Fred Arne Wergeland
Cinematography by Fred Arne Wergeland and Athan Merrick
Edited by Peder Bratterud and Fred Arne Wergeland
Music by Bjørnar Johnsen and Herman Christoffersen
Color grade: Terje Lund
Produced by Norseman Productions
Ask somebody in the building industry to visually communicate the architecture of a building and you'll be presented with site plans, floor plans, elevation views, cross-section views and detail drawings. In contrast, ask a software developer to communicate the software architecture of a software system using diagrams and you'll likely get a confused mess of boxes and lines. I've asked thousands of software developers to do just this over the past decade and continue to do so today. The results from these software architecture sketching workshops still surprise me, anecdotally suggesting that effective visual communication of software architecture is a skill that's sorely lacking in the software development industry.
Of course, as an industry, we do have the Unified Modeling Language (UML), but asking whether this provides an effective way to communicate software architecture is often irrelevant because many teams have already thrown out UML in favour of much simpler boxes and lines diagrams. Abandoning UML is one thing but, perhaps in the race for agility, many software development teams have lost the ability to communicate visually.
This talk explores the visual communication of software architecture based upon my experience of working with software development teams across the globe. We'll look at what is commonplace today, the importance of creating a shared vocabulary, diagram notation, the value of creating a model plus how to use tooling and static analysis techniques to automate diagram generation.