pattern-bridge

To decouple abstraction and implementation, you define a shared implementation interface and a base abstraction that delegates work. This separates platform-specific logic from core business logic, allowing both hierarchies to evolve independently without tight coupling.

Keeping notification workflows platform-independent requires splitting the service into a base abstraction that delegates to provider-specific implementations. You create refined abstractions for logic variations while delivery channels like email, SMS, and push are handled by the implementation layer.

You separate payment processing logic by applying the bridge pattern to split the abstraction from the implementation. The core processing logic delegates to a shared interface, while specific payment providers like Stripe and PayPal are implemented as independent platform-specific classes.

Use the bridge pattern when large classes force a single hierarchy that couples platform providers to core logic. It is needed when you must support multiple delivery channels or providers and want both abstraction and implementation layers to remain independently evolvable.

Yes, you can create refined abstraction subclasses for each business variant without duplicating provider-specific code. The base abstraction delegates work to a stable implementation interface, ensuring changes to platform providers do not ripple through your core logic.