|
You're quite right, of course. In my scenario, I want to provide a package for easy download and deployment. Each customer will indeed run their own mysql db, if they choose to self-host the containerised software. I plan to offer a paid hosting service, where I'll rent bare metal in a data centre, onto which I'll install management and orchestration tools of my choosing. An identical container for any environment is my ideal, since this will make maintenance, testing, development etc simpler. Consequently each customer hosted in my data centre will, in effect, get their own mysql instance. This way the identical software in each container will be dumb, and expect an identical situation wherever it's installed. Now, in reality, I may do something clever under the hood with all those mysql instances, I just haven't worked out what yet :) Actually it will probably be Postgres, but I'll use whatever db is most suited. So yes, some duplication and wasted disk space, but that's a trade off for simplified development, testing, support, debugging, backups, etc. |