What is the best development pattern or architecture to follow in SAP CAP Node.js projects (SOLID or something else)?

[Fab2295]

I’m working on a growing SAP CAP (Cloud Application Programming Model) project using Node.js, and the team wants to adopt a consistent development pattern or architecture to keep the codebase clean, maintainable, and scalable.

I’m familiar with general backend principles like SOLID, but I’m not sure how well they apply in CAP, since a lot of the database interaction is handled through CDS services, entities, and the framework’s built-in handlers.

So my question is:

What is the recommended architectural pattern for CAP Node.js development?
Should we try to follow something like SOLID, or are there CAP-specific or Node-oriented patterns that work better?

I’d appreciate guidance or examples on patterns such as:

• Service / Handler separation
• Domain-Driven Design (DDD)
• Clean Architecture
• Repository or Data Mapper patterns (and whether they make sense in CAP, since CDS services already abstract the DB)
• Modularization strategies for large CAP projects
• Any best practices from real CAP projects in production

If you have suggestions, examples, or official recommendations from SAP, that would be extremely helpful.