Remove Design Remove Software Architecture Remove Systems Remove Training
article thumbnail

Nurturing Design in Your Software Engineering Culture

Strategic Tech

There are a few qualities that differentiate average from high performing software engineering organisations. I believe that attitude towards the design of code and architecture is one of them. Both valuing design and striving for continuous delivery are necessary. So we need to make it part of everything we do.

article thumbnail

Modelling Bounded Contexts with the Bounded Context Design Canvas: A Workshop Recipe

Strategic Tech

How do we break a large system into smaller, more manageable modular components? In Domain-Driven Design, a large system is decomposed into bounded contexts , which become natural boundaries in code as microservices and as teams in the organisation. 30 minutes) Bounded Context Design Canvas (min.

Design 76
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

How the Swedish Transport Agency learned distributed systems in six months

Particular Software

In-person training and conferences have been postponed, cancelled, or transitioned to the virtual world. We’ve certainly been affected by this shift at Particular with the cancellation of our popular Advanced Distributed Systems Design (ADSD) course this year. My colleagues who’d attended it before felt the same way.

article thumbnail

Trends and Topics for 2022

Adrian Cockcroft

I did a few talks on this subject early in the year, and linked this to the sustainability advantages of serverless architectures. The need for systems to be resilient is still increasing, and chaos engineering tools and techniques are developing as a key way to validate that resilience is working as designed.

article thumbnail

How architecture evolves into strategy

O'Reilly Software

Technology systems are difficult to wrangle. Our systems grow in accidental complexity and complication over time. Architecture begins when someone has a nontrivial problem to be solved. The product management team states what must be done to solve the problem, and the architect describes how to realize that vision in a system.

Strategy 100
article thumbnail

Forming an Architecture Modernization Enabling Team (AMET)

Strategic Tech

external consultants or training) Preference for waiting for the problems to arise (indicating the need for an AMET) or forming an AMET early to prevent issues arising Confidence level that modernization will actually happen (sometimes it is just too unclear and lacking priority) How quickly do you want/need to modernize?

article thumbnail

MLOps and DevOps: Why Data Makes It Different

O'Reilly

Let’s start by considering the job of a non-ML software engineer: writing traditional software deals with well-defined, narrowly-scoped inputs, which the engineer can exhaustively and cleanly model in the code. In effect, the engineer designs and builds the world wherein the software operates. Software Architecture.

DevOps 138