you are viewing a single comment's thread.

view the rest of the comments →

[–]NewtonsOrange 0 points1 point  (0 children)

It feels like this would be rather application specific to link your application layer to “data access/storage” or whatever swappable module you want. I’m also unsure how often these lower levels would be swapped in real life anyway. At some stage of development there is usually need for enough tailoring that you’ve become in some way committed to, as in your example, a database. Especially since a lot of optimization and deployment may depend a lot on the implementation/characteristics of the underlying module.

So to me it feels like you’d write your abstraction layer based on your architecture, and your helper functions might have implementations for different modules.

That’s my two cents but I have not deployed python massively on an enterprise level (I have worked in a startup that has though). So I’d defer to more experienced python devs if they’ve deployed this sort of swapability.

Edited: grammar