Hono for Large Scale Apps
Hello,
We have decided to use Hono as our API framework for our new web app. We have used it for a few months now and finding it fantastic. My only confussion is since the start, I had the typical controller, service and repository structure. I recently discovered on the Hono documentation that they do not recommended the typical 'RoR' controller pattern. I completley get the reason, but would like to know of examples of how people are building apps with many routes and how they are splitting up their business & database logic.
Thanks
We have decided to use Hono as our API framework for our new web app. We have used it for a few months now and finding it fantastic. My only confussion is since the start, I had the typical controller, service and repository structure. I recently discovered on the Hono documentation that they do not recommended the typical 'RoR' controller pattern. I completley get the reason, but would like to know of examples of how people are building apps with many routes and how they are splitting up their business & database logic.
Thanks
