Just plodding away with my littl app and I decided that it was time to get rid of the frontend making DB calls and the backend competing with it for database connections.
So a little bit of thought, a bit of prompting and we now have a much more seperated application with clear demarcation of front and backend.
All achieved with Cursoe, shipkit rules, a bit of knowledge and a cavalier attitude to software development ( all backed up and version controled through numerous git commits)
As you can see from the spider-like diagram (the one with red) DB-Connectivity-pre-migration I had Drizzle-ORM on the frontend making DB calls, and then at a later stage added in SQL alchemy in the backend with the view to moving all db calls to the backend , thereby not exposing my DB connections to the Internet. The second diagram(The green one) DB-Connectivity-post-migration shows a much leaner and performant application. You can easily see where the front end starts and finishes and where the backend takes over.
And then i just threw in some other 'interesting' facts. All in all an enjpoyable excercise, granted with a bit of teething problems, but hey, thats what make it fun.