Architecture and microservices

Making changes across services

A small change crosses several services. Ownership, data flow and the impact on other systems are unclear.

An example exercise

Illustrative task. We choose the actual exercise around your team’s work and tools.

Follow a new field from the API to the interface. Identify affected services and check that existing clients still work.

How we work

Identify the affected services and dependencies.
Draft a change plan with AI and review it technically.
Check API interactions with examples and tests.

What stays with your team.

A service map for the selected change.
API examples and integration checks.
An agreed implementation sequence and responsibilities.

Making time for the work

A series of working sessions on a selected cross-service task. Depth and duration depend on system complexity.

We agree session count and length, group size, preparation, follow-up and fees before starting. Environment preparation and practice get their own time allocation.

What do we need to start?

Relevant repositories or API descriptions, representative data and participants who know the systems.

Explore the other workshops