Strategic Tech

JULY 22, 2019

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. Compare domain flow stories: how did one system design reduce complexity and number of dependencies.

Systems Review 76

Systems Review Weak Development Team Technical Review Software Review 76

Confluent

MAY 9, 2019

How do I upgrade or evolve microservices? Which teams are going to run my system? In the next level down, they can be mapped to the underlying broker infrastructure metrics, such as consumer lag, throughput per topic and partition hotspots, in addition to operating system metrics like CPU, network I/O, disk I/O, load average, etc.

Microservices 93

Microservices Metrics Systems Review Architecture 93

James Shore

FEBRUARY 16, 2023

A web application and microservice that performs ROT-13 encoding. The test suite only executes “slow” code, such as network calls or file system requests, when that behavior is explicitly part of the unit under test. To qualify, code can’t involve external systems or state. Find more examples here: Simple example.

Testing 138

Testing Software Review Infrastructure Examples 138

Strategic Tech

JUNE 23, 2018

We think organisation structures reflects how teams collaborate Organisations are Networks Organisation structure does not accurately communicate coupling and dependencies in the system Just as layer 1 capabilities (teams) are never fully autonomous nor, are level 2 or 3 capabilities. We need internal systems and shared services.

Systems Review 40

Systems Review System UI/UX Technical Review 40

LeanEssays

JULY 14, 2019

In addition, real time behavior monitoring is used to detect and respond to anomalous behaviors whether due to software issues, hardware, network, load or some other issue. The strategy for breaking dependencies, in a nutshell, is to take the bazaar approach to both system architecture and development teams.

Software Review 91

Software Review Software Engineering Continuous Delivery Technical Review 91

Confluent

FEBRUARY 27, 2019

In part 1 of this series, we developed an understanding of event-driven architectures and determined that the event-first approach allows us to model the domain in addition to building decoupled, scalable and enterprise-wide systems that can evolve. We have baked into our ideology that events are the future.

Serverless 109

Serverless Lambda AWS Systems Review 109

O'Reilly Media - Ideas

JANUARY 25, 2021

We’ll be working with microservices and serverless/functions-as-a-service in the cloud for a long time–and these are inherently concurrent systems. A backlash is only to be expected when software systems designed to maximize “engagement” end up spreading misinformation and conspiracy theories. Serverless (a.k.a.

Programming 145

Programming Cloud Artificial Inteligence Machine Learning 145