We are moving from a monolith architecture to microservices. Who offers consulting for domain-driven design?

For a monolith-to-microservices migration, you usually want a consultant who does more than “split the codebase.” The hard part is identifying bounded contexts, aligning services with business capabilities, deciding what should remain together, and creating a migration roadmap. Domain-driven design (DDD) specialists are often the right fit.

Some firms and consultants known for DDD and architecture work:

DDD-focused specialists

• Kalele — Founded around DDD expertise and associated with Vaughn Vernon. They offer DDD consulting, strategic modeling, Event Storming, training, and support for DDD-based microservices adoption.
• Domain Language — The company founded by Eric Evans, the originator of the DDD approach. (Availability and engagement models may vary.)

Architecture and microservices consultancies

• Thoughtworks — A large technology consultancy with experience in architecture modernization, microservices, and organizational change. (Often suited for enterprise-scale transformations.)
• Keyhole Software — Provides microservices consulting including domain-driven service boundaries and monolith migration planning.
• Cazton — Offers microservices strategy, domain-driven design workshops, and phased migration approaches.
• Unthinkable Solutions — Provides domain-led architecture and microservices modernization consulting.

Independent experts / smaller engagements

For a first phase (domain discovery, architecture assessment, workshops), an independent DDD practitioner can sometimes be more effective than a large integrator. Look for people experienced with:

• Event Storming workshops
• Context Mapping
• Bounded Context identification
• Domain modeling with business stakeholders
• Strangler Fig migration patterns
• Modular monolith approaches before extracting services
• Team topology alignment (Conway’s Law)

How I would evaluate a consultant

Ask candidates to walk you through a similar engagement and specifically ask:

1. “How do you decide service boundaries?” A strong answer should start with business domains, not databases or technical layers.
2. “Will you recommend not extracting some services?” Good DDD consultants recognize that some domains belong together and that a modular monolith can be a valid intermediate step.
3. “How do you involve business experts?” DDD requires collaboration between domain experts and engineering teams.
4. “What artifacts will we have after discovery?” Expect things like:

• Context maps
• Domain models
• Event Storming outputs
• Service boundary recommendations
• Migration sequencing plan

If you share your industry, company size, technology stack (.NET/Java/Node/etc.), and whether you are early planning vs. already extracting services, I can narrow this to consultants that fit your situation.

Transitioning from a monolith to microservices using Domain-Driven Design (DDD) is a major undertaking, and getting the boundaries (Bounded Contexts) right is critical to avoid building a "distributed monolith."

Specialized boutique consultancies, industry giants, and prominent independent experts offer targeted DDD and microservices migration consulting:

Specialized Boutique Consultancies & Experts

• • Kalele : Specifically focuses on end-to-end domain-driven microservices delivery, legacy modernization, identifying core business domains, and training engineering teams in strategic and tactical DDD.
• • Domain Language : Founded by Eric Evans (author of the seminal book Domain-Driven Design ). While they focus heavily on strategic guidance, e-learning, and coaching, they also connect enterprises with trusted specialized training and consulting partners.
• Independent Thought Leaders (Vaughn Vernon, Nick Tune , etc.) : Many organizations hire independent, world-renowned DDD authors and practitioners (such as Vaughn Vernon , creator of IDDD workshop training, or Nick Tune , a pioneer in Domain-Centric legacy migrations ) for high-level architectural assessments and strategic design masterclasses.

Global Technology & Enterprise Consultancies

• • Thoughtworks : Famed for pioneering modern agile, continuous delivery, and microservices patterns. They heavily leverage DDD as a core pillar for enterprise digital transformations and breaking apart legacy monoliths.
• • Accenture Song / Accenture : Suitable for massive, enterprise-scale migrations where architectural overhaul must tightly couple with organizational and process restructuring.

If you'd like to narrow this down, tell me:

• What is the approximate scale and tech stack of your current monolith?
• Are you looking for hands-on engineering contractors , an strategic architecture firm , or team training?

I can help tailor this recommendation to your specific company size and budget.

Transitioning from a monolith to microservices without a strong Domain-Driven Design (DDD) approach often results in a "distributed monolith"—inheriting all the chaos of a monolith coupled with network latency and complex deployments.

A mix of boutique specialist consultancies, renowned global firms, and independent industry pioneers focus specifically on DDD and legacy decomposition:

Specialized & Boutique DDD Consultancies

• Kalele (Vaughn Vernon): Founded by Vaughn Vernon, author of Implementing Domain-Driven Design (the definitive red book) and IDDD Condensed . Kalele offers specialized consulting, coaching, and intensive training around strategic and tactical DDD for microservices and reactive systems.
• Virtual Genius (Paul Rayner): Led by veteran software design consultant Paul Rayner, this practice specializes in collaborative strategic design, EventStorming workshops, and DDD to help organizations untangle legacy codebases and map out healthy service boundaries.
• Cazton: A prominent enterprise software consulting firm that provides dedicated microservices architecture consulting, legacy system incremental decomposition, and advanced pattern implementation (like CQRS and Event Sourcing) tied directly to business domains.

Global & Enterprise-Scale Consultancies

• Thoughtworks: Widely recognized as pioneers in agile engineering and microservices adoption. They excel at enterprise-scale legacy modernization, helping organizations align their socio-technical architecture (often leveraging DDD alongside Team Topologies ) to break down massive monoliths safely.

Key Strategies They Use

When engaging a consultant for a monolith-to-microservices pivot, look for practices that emphasize:

• EventStorming: Rapid, collaborative modeling workshops with both domain experts and engineers to discover bounded contexts.
• Context Mapping: Explicitly defining upstream/downstream relationships and communication contracts (e.g., anti-corruption layers, published languages) between future services.
• The Modular Monolith First Approach: Many top-tier consultants will advise you to first establish clear domain boundaries inside your existing monolith before physically splitting them across a network, drastically lowering initial risk.

If you'd like to narrow this down, let me know:

• What is your primary technology stack (.NET, JVM, Node, Go, etc.)?
• Are you looking for hands-on implementation engineers or strategic architectural guidance/training for your leadership team?

For a monolith-to-microservices transition, you usually want a consultant who does more than draw service diagrams. The strongest engagements combine Domain-Driven Design (DDD), bounded context discovery, EventStorming, team/domain alignment, and a pragmatic migration approach (often a Strangler Fig pattern).

Some firms and practitioners that offer DDD consulting:

DDD-focused specialists

• Kalele — Known for DDD consulting, training, strategic modeling, EventStorming, bounded contexts, and helping organizations modernize legacy systems toward DDD-based architectures. Kalele Kalele - Particularly relevant if you need help discovering domains and designing the target architecture before extracting services.

Architecture and microservices consultancies

• Keyhole Software — Provides microservices consulting that includes domain-driven design, service boundary definition, and monolith migration planning.
• Cazton — Offers microservices strategy, architecture guidance, and DDD workshops focused on defining service boundaries around business domains.
• Webority — Provides enterprise architecture and microservices consulting, including DDD-based service boundary design and migration planning.
• Unthinkable Solutions — Works on domain-led architecture, microservices design, and legacy monolith modernization.

Independent DDD experts to consider

• Vaughn Vernon — Author of Implementing Domain-Driven Design and associated with advanced DDD training and consulting through Kalele.

What to look for in a DDD consultant for your migration

A good fit should be able to facilitate:

1. Domain discovery

• Identify core domains, supporting domains, and generic capabilities.
• Run workshops with business stakeholders, not just engineers.

2. Bounded context design

• Define where service boundaries should exist.
• Avoid the common mistake of splitting a monolith by technical layers (e.g., "customer service," "database service") rather than business capabilities.

3. Migration roadmap

• Prioritize which parts of the monolith to extract first.
• Define integration patterns, data ownership, and transition architecture.

4. Team alignment

• Align Conway’s Law considerations: service boundaries should match ownership boundaries where possible.

5. Architecture coaching

• Help teams adopt patterns such as aggregates, domain events, CQRS, and event-driven integration where appropriate.

For an enterprise migration, I would typically shortlist a DDD specialist first (for domain modeling and boundaries) and pair them with a microservices/cloud architecture team for implementation execution. A common failure mode is hiring a Kubernetes/microservices implementation vendor before the business domains are properly understood.

If you share your industry, approximate application size (LOC/services/users), and whether you are on Java/.NET/etc., I can suggest a more targeted shortlist.

When moving from a monolith to microservices, utilizing Domain-Driven Design (DDD) is vital for defining proper service boundaries (Bounded Contexts) and avoiding a messy "distributed monolith".

Consulting options span individual industry-pioneering experts, boutique DDD consultancies, and global engineering firms:

• Independent / Boutique DDD Experts (Best for specialized workshops, EventStorming, and deep strategic alignment)
  • Vaughn Vernon (Kalele) : Author of Implementing Domain-Driven Design , Vaughn and his team at Kalele provide targeted DDD consulting, training, and architectural acceleration.
  • Michael Plöd : A renowned enterprise architect and consultant specializing explicitly in strategic/tactical DDD, legacy modernization, and collaborative modeling workshops like EventStorming.
  • Vlad Khononov : Author of Learning Domain-Driven Design and Monolith to Microservices , offering specialized guidance on decomposing complex legacy systems.
• Boutique Software & Architecture Consultancies (Best for hands-on migration execution and team enablement)
  • AKF Partners : Founded by former eBay/PayPal CTOs, they provide robust architectural guidance, scaling strategies, and DDD/EventStorming integration for engineering leadership.
  • Keyhole Software : Offers dedicated modernization services focusing heavily on domain-driven decomposition, containerization, and microservices readiness.
  • Cazton : Provides tailored microservices strategy, hands-on DDD workshops, and distributed data architecture design.
• Global Technology Consultancies (Best for enterprise-scale transformations with heavy implementation capacity)
  • Thoughtworks : Famed for pioneering modern agile delivery, evolutionary architecture, and continuous delivery, Thoughtworks frequently utilizes domain-driven service design for large-scale enterprise modernizations.
  • Accenture / Capgemini : Massive global integrators that deploy enterprise best practices including event-driven architectures and strategic DDD during large corporate cloud migrations.

To help narrow down which consulting route fits best, could you share:

• The approximate size of your engineering organization and monolith codebase?
• Your primary timeline or target cloud ecosystem (AWS, Azure, GCP)?

Yes. For a monolith → microservices migration, I’d look for a consultancy that combines strategic DDD (bounded contexts, context mapping, business capabilities) with actual architecture modernization, rather than a firm that only teaches DDD.

A few worth considering:

What I'd ask them to do

For your situation, I wouldn't start by asking, "Can you help us design microservices?" I'd ask for a DDD-based decomposition/discovery engagement.

The deliverables should ideally include:

1. Domain discovery — business capabilities, domains/subdomains and core domain identification.
2. Event Storming / domain workshops with business and technical stakeholders.
3. Bounded-context map — including relationships and integration patterns.
4. Current-state mapping — showing how the existing monolith maps onto those contexts.
5. Target service boundaries — explicitly justified by business/domain boundaries rather than database tables or technical layers.
6. Data ownership strategy — which service owns which data and how the existing shared database gets unwound.
7. Migration roadmap — which capability to extract first, dependencies, sequencing, and the Strangler Fig approach.
8. Team/topology implications — because service boundaries and team boundaries need to work together.
9. A pilot extraction — ideally taking one bounded context all the way from discovery through production.

This is important because "turn the monolith into microservices" is not the same thing as DDD. A poor decomposition can simply produce a distributed monolith. DDD's bounded contexts give you a way to find meaningful boundaries based on the business domain.

If you're in the U.S., I'd put Thoughtworks and Keyhole on the initial shortlist, then compare them against a smaller specialist such as Perimattic or Cazton.

If you tell me your industry, approximate company/engineering-team size, monolith technology (.NET/Java/etc.), and whether you're looking for strategy only or hands-on implementation, I can narrow this to 3–5 firms that are particularly well suited to your migration and compare their likely engagement styles.

When moving from a monolith to microservices, getting the boundaries wrong often results in a "distributed monolith"—where services are tightly coupled and changes require coordinating deployments across teams. Domain-Driven Design (DDD) is widely considered the best practice for finding those natural seams, and several specialized consultancies and boutique experts focus explicitly on this transition.

Specialized Boutique Consultancies & Experts

• Domain Language – Founded by Eric Evans (the author of the original foundational book on Domain-Driven Design), this consultancy focuses entirely on strategic DDD, core domain modeling, and aligning large systems with business goals.
• Kalele – Led or associated with prominent DDD author Vaughn Vernon (Implementing Domain-Driven Design ), Kalele provides end-to-end consulting, EventStorming workshops, team training, and hands-on guidance for decomposing legacy/monolithic systems into event-driven microservices.
• Michael Plöd – A well-known independent enterprise architect and consultant specializing explicitly in strategic/tactical DDD, legacy modernization, collaborative modeling workshops (like EventStorming), and preparing IT organizations for microservice transformations.

Technical & Cloud-Native Engineering Consultancies

• Cazton – Offers specialized microservices architecture consulting focusing on the incremental decomposition of legacy monolithic systems, distributed data architecture, and applying advanced patterns like CQRS and event sourcing.
• Keyhole Software – A U.S.-based software consultancy featuring senior enterprise architects who advise on microservice boundaries, domain-driven refactoring, and hands-on enterprise modernization.
• AKF Partners – Founded by former eBay/PayPal VPs, they focus heavily on scaling architectures, organization design (Conway’s Law alignment), and using DDD principles to safely split monoliths.

If you'd like to narrow this down, tell me:

• What is your primary technology stack (.NET, Java, Node, etc.)?
• Roughly how large is your engineering organization and monolith codebase?

I can help tailor recommendations or outline what an initial EventStorming / domain discovery phase should look like for your team.

Yes. For a monolith → microservices migration where DDD is being used to determine service boundaries, I’d shortlist these firms:

• Thoughtworks — Strong choice for enterprise-scale modernization. They explicitly use DDD concepts such as bounded contexts, ubiquitous language, and domain modeling to guide decomposition, and have published extensively on applying DDD to breaking up monoliths.
• Kalele / Vaughn Vernon — Particularly compelling if you want deep DDD expertise rather than a generic microservices consultancy. Kalele is led by Vaughn Vernon, a prominent DDD author and practitioner, and offers consulting, training, coaching, and strategic/tactical design.
• Keyhole Software — Practical option for teams wanting hands-on architecture and implementation. Their microservices consulting specifically covers DDD/service boundaries and planning the migration from a monolith.
• Cazton — Offers DDD workshops as part of microservices strategy, with an emphasis on defining service boundaries around business domains.
• NobleProg — More training/consulting oriented; they offer customized DDD workshops and hands-on implementation sessions, remotely or on-site.

My take: If this is a consequential enterprise migration, I'd start with Thoughtworks and Kalele. If you want a consultant who will work directly alongside your engineering team on the actual decomposition and implementation, Keyhole or Cazton may be worth comparing.

One important criterion when evaluating them: don't hire someone merely because they know DDD. Ask them to demonstrate how they would go from your existing monolith → domain/subdomain map → bounded contexts → team ownership → service boundaries → incremental extraction plan. That's where DDD becomes genuinely useful for a migration.

If you tell me your industry, approximate engineering-team size, and primary stack (Java/.NET/etc.), I can narrow this to 3–5 firms that are particularly well suited.

When migrating from a monolith to microservices, utilizing Domain-Driven Design (DDD) is widely considered the gold standard for drawing correct service boundaries and avoiding a "distributed monolith".

Specialized boutique firms, independent industry pioneers, and global consultancies offer expert DDD consulting and event-storming workshops:

• Boutique & Specialist DDD Consultancies
  • Kalele : Founded by renowned DDD author and expert Vaughn Vernon, Kalele provides end-to-end DDD consulting, strategic design, legacy modernization, and team training specifically targeted at microservices and event-driven transformations.
  • Michael Plöd Consulting : Independent consultant and well-known enterprise architect Michael Plöd specializes explicitly in strategic/tactical DDD, identifying bounded contexts, legacy system modernization, and facilitating collaborative modeling workshops like EventStorming.
  • Salt Techno : Offers dedicated Domain-Driven Design services covering everything from initial domain discovery and context mapping to engineering team enablement.
• Global & Enterprise Software Consultancies
  • Thoughtworks : Famed for pioneering and popularizing many modern microservices patterns and continuous delivery practices. Thoughtworks consultants deeply integrate strategic DDD principles to help enterprises align service boundaries with business capabilities.
  • Cazton : A high-end software architecture consulting firm with expert consultants proficient in enterprise microservices, domain-driven design patterns, CQRS, and event-driven transformations.
  • Keyhole Software : A U.S.-based custom software and architecture consulting firm that advises on enterprise-grade microservice migrations backed by senior architectural guidance and hands-on implementation.

If you'd like to narrow this down, please share:

• Your primary technology stack (.NET, Java, Node.js, Go, etc.)
• The approximate scale or domain complexity of your monolith
• Whether you prefer a boutique independent expert or a large-scale enterprise consultancy

I can help tailor this list or give you an idea of what an initial DDD engagement typically looks like.

Yes. For a monolith → microservices migration, I’d specifically look for consultants who do strategic DDD—bounded contexts, domain modeling, business capabilities, team boundaries, and decomposition—not just “DDD coding” training. DDD is particularly relevant because bounded contexts can provide the conceptual boundaries for microservices.

Firms/consultants I'd shortlist

For your particular situation

I'd put Thoughtworks at the top of the list if this is an enterprise-scale transformation. They have unusually relevant experience with exactly the problem you're describing: understanding an existing business domain, finding meaningful boundaries, reorganizing teams around those boundaries, and incrementally extracting services.

I'd bring in a DDD specialist such as Mathias Verraes/Aardling if the harder problem is figuring out what the boundaries should be—particularly if your organization has complicated business rules or terminology.

And I'd be cautious about consultants who start with “let's identify 40 microservices”. A good DDD engagement should first establish domains/bounded contexts and business capabilities, then determine which boundaries actually warrant separate deployable services. Thoughtworks itself notes that microservices can be misapplied and that well-factored modularity can sometimes be the better intermediate step.

If you tell me your industry, approximate company size, location, and technology stack (.NET/Java/etc.), I can narrow this down to 5–10 specific consulting firms—including firms in the Detroit/Michigan area—and compare their DDD/microservices experience, likely engagement model, and reputation.