Hexagonal architecture (ports and adapters): worth the complexity?

our team is debating adopting hexagonal architecture (ports and adapters) for a new mid-size service we're building. on one hand, the idea of isolating business logic from infrastructure concerns is really appealing for testability and maintainability. it makes sense that the core domain shouldn't care if it's talking to a database, a REST API, or a message queue. on the other hand, it seems to add a fair bit of boilerplate, especially for a small 5-person team that needs to ship quickly. creating interfaces for ports, implementing adapters, DTOs for data transfer, it all feels like a lot of extra files and indirection for a typical CRUD operation. for a service that's not super complex but has critical business logic, is the increased upfront complexity worth it? i'd love to see some practical project structure examples where this really shines without becoming overly burdensome.