HTML MASTER CLASS /// LEARN TAGS /// BUILD STRUCTURE /// SEMANTIC WEB /// HTML MASTER CLASS /// LEARN TAGS ///

Untitled Lesson

⚡ Total XP: 0|💻 backend XP: 0

Skill Matrix

UNLOCK NODES BY LEARNING NEW TAGS.

Select an unlocked node to view details root

Pascual Vila

Frontend Instructor // Code Syllabus

Common Pitfalls & Errors

The Error //

Defining a port interface but having the core import a concrete adapter directly instead of depending on the abstraction

// Wrong: core still coupled to a specific adapter
import { StripeAdapter } from "./adapters/stripe";
class CheckoutUseCase { constructor() { this.gateway = new StripeAdapter(); } }

// Correct: depends on the abstraction, injected from outside
class CheckoutUseCase { constructor(gateway) { this.gateway = gateway; } }

The Solution //

If the core imports StripeAdapter directly rather than the PaymentGateway interface it implements, the core is still coupled to Stripe specifically — defeating the purpose of defining the port at all. The core should only ever reference the port interface; the concrete adapter is injected from outside.

The Error //

Applying hexagonal architecture to an entire existing large service in one big-bang restructure

// Risky: restructuring everything at once
// Better: start with one complex, high-value bounded area
// e.g. src/core/payments/ + src/adapters/{stripe,paypal}/

The Solution //

A full-codebase restructure is high-risk and slow to deliver value — a more pragmatic approach applies the pattern to one bounded, genuinely complex area first (like payment processing needing multiple provider implementations), proving the value before deciding whether wider adoption is worth the effort.