Another comment, this time related with lingüistic domain.
When I speak in terms of "Driver" / "Driven" , I don't relate these terms with "Frontend" (Driver) and with "Persistence" (Driven); no, I speak in terms of "controllers", "databases" and so forth. So, when you create folders...do you create folders called "driver", "driven" or "controllers", "persistence"...?
Another deeper level than "driver" is "Controller" and much deeper than "controller" is "render" and "non-render" (it includes controllers which send json, xml, cvs, download pdfs and so on...).
Yes, from the perspective of Hexagonal Architecture, both REST API Controllers & Databases are infrastructural concerns, i.e. they are Adapters. The only distinction is that REST API Controllers are on the "Driver" side whereas Databases are on the "Driven" side.
Another comment, this time related with lingüistic domain.
When I speak in terms of "Driver" / "Driven" , I don't relate these terms with "Frontend" (Driver) and with "Persistence" (Driven); no, I speak in terms of "controllers", "databases" and so forth. So, when you create folders...do you create folders called "driver", "driven" or "controllers", "persistence"...?
Another deeper level than "driver" is "Controller" and much deeper than "controller" is "render" and "non-render" (it includes controllers which send json, xml, cvs, download pdfs and so on...).
How to stop of creating levels? xD
I consider "Presentation" as infrastructure, hence my three layers are: infrastructure, application and domain.
Inside infrastructure I add controllers, databases and so forth.
Yes, from the perspective of Hexagonal Architecture, both REST API Controllers & Databases are infrastructural concerns, i.e. they are Adapters. The only distinction is that REST API Controllers are on the "Driver" side whereas Databases are on the "Driven" side.