Messaging integration decoupled from the domain
Integrate messaging without coupling the product domain to a specific library or provider, and be able to test it without a real external service.
Last updated: 2026-09-18 · Owner: Flexora engineering team
Alternatives considered
- Discarded
- Connect the domain directly to a specific messaging integration.
- Chosen
- Interpose a replaceable adapter layer, including a test double.
Decision made
Define messaging through a replaceable adapter layer between the domain and the external integration, with a test double available.
Rationale
Avoids locking the product into a particular integration and allows verifying behavior without depending on a real external service.
Frequently asked questions
- What did Pyae decide about "messaging integration decoupled from the domain"?
- Define messaging through a replaceable adapter layer between the domain and the external integration, with a test double available.
- How do you integrate WhatsApp or another messaging channel without coupling it to the domain?
- By putting a replaceable adapter layer between the product's domain and the actual external integration, which is exactly what Pyae does. The domain never talks directly to the messaging library or provider.
- What's the advantage of a replaceable adapter for messaging?
- It lets you swap messaging providers without touching the domain logic, because the concrete integration point stays isolated behind the adapter. Pyae uses this specifically to avoid locking the product into one particular integration.
- How do you test messaging without depending on a real external service?
- Pyae's adapter layer ships with a test double, which lets you verify system behavior without needing the external messaging service to be available during tests.
This kind of decision applies to your project too
If your operation needs custom software with technical decisions that are documented and built to last, we can help you define them.