11 Side notes JAX London 2016

Quick notes from session 10 of JAX London 2016. Applying DDD at pace for Effective Microservices workshop preseneted by Russ Miles.

· Q.Assistance · 1 minutes ·

A photo taken from above showing a meeting table with people woriking with their laptops.

Overview

Session: 13th Oct — 9:00 to 17:00 Applying DDD at pace for Effective Microservices by Russ Miles, Atomist

Notes

This was a workshop session. During the morning Russ performed a master lesson about how to prepare our mind towards Mirco-services solutions. Here I present just some of the hotkey concepts of the theoretical part of the session.

  • Anti-fragile is the core concept behind Micro-services. Embrace change.
  • Do not aim for the right / best solution, rather aim for the seed of an evolving organism.
  • Describe the system by its events only. Consider the things that happen in order to find the events of a system. Create a ubiquitous language not about the entities of the model, but about the events between those entities.
  • Use a more scientific method approach.
  • Events are immutable. They must be logged and persisted.
  • Find meaningful event names.
  • Avoid acronyms, they are an impediment to communication.
  • Avoid code names for systems, rather describe what the system does.
  • Apply single responsibility principle for events.
  • Good names come from meetings with stakeholders while describing the system.
  • Find the causality of events. The flow of events as they trigger other events.
  • Define the bounded context. The context where the team can know what happens, what are the events and the team can evolve the solution all based on internal/technical reasons.

The workshop was much more fun than this list of concepts. Russ is a top-level speaker and I even would say he reaches the level to be a Technologist Philosopher with well rooted and practical principles. It is hard to summarise all the content that he delivered in this session. Probably would be much better to keep an open eye and attend to the next Miles’s master session.

That was all for this session.


Many thanks for reading, please leave a comment if you have any quality hint.

Keep on testing, better!

More posts

  • A diagram of two intersecting sets with SDETs on the left, business experts on the right and Test Automation in the intersecting area.

    The three QA amigos: SDTs, AEs and the VBEs

    A usual misunderstanding among many teams is to regard testing as one team without any specialization. Moreover, the biggest mistake that I have seen is to give the same job title to all "testers" regardless their skills and contributions.

  • Abstract ai generated image of a webstie with astro and google sheets.

    Web Google Sheets

    This post thoroughly reviews how I implemented a new static website with the Astro framework and Google Sheets as the Content Management System CMS.

  • A photo of a guy looking at a whiteboard with a flowchart diagram

    How to build Mermaid Diagrams into an Astro MDX blog

    Discover how to seamlessly integrate Mermaid diagrams into an Astro MDX blog using a custom devContainer setup. This post dives into the challenges of pre-rendering text-based diagrams—like flowcharts and sequence diagrams—for a static site, offering a streamlined solution with Docker Compose, Playwright-core, and Chrome. This practical guide will simplify your setup, ensure consistency, and boost performance.