Standards and Transferability
OK - I'm not a database expert, so forgive what might be a dumb question, but is there no way that the data format and functionality can be standardized so that the host doesn't matter?
In the US the defense department (their spelling, not mine) sometimes uses a "buggins turn" approach to procurement of expensive disposables like missiles. The initial development and first couple of manufacturing tranches are aggressively competed between the usual companies (Boeing, Lockheed, Raytheon, etc.). However, the development contract gives ownership of the design to the DoD, including a full technical data pack which includes everything needed to manufacture, test, deliver and maintain the missiles. In this way the DoD can compete future manufacturing tranches between the usual companies and sometimes, in effect, it becomes a sort of buggins turn. The advantages of this is that the DoD doesn't get locked into one supplie, with the resultant price hikes, and also that the money gets spread around the companies so that one doesn't end up as massively dominant or, as in the case of the UK, only one or two remain.
So, back to my original question - is there a way in which the databases and functionality that the MoD requires for this cloudy stuff could be designed in a manner that means it could easily be transferred from one supplier to another in the spirit of both keeping costs down but also avoiding market dominance, developing local expertise, jobs, etc.?