> Don't use services that lock you in. Why, if they bring value? > Instead use a layer that abstracts that. How can I "abstract" BigQuery? > If it's abstrac

> Don't use services that lock you in. Why, if they bring value? > Instead use a layer that abstracts that. How can I "abstract" BigQuery? > If it's abstracted behind an agreed upon industry standard protocol (MySQL, pg, mongo connections or S3/NFS storage, etc)? This still doesn't answer the question of "can be implemented within kube for at-cost prices." BigQuery is amazing at processing enormous amounts of data at fraction of time and cost it would take, say, MySQL to process the same data. How can I "abstract it away" and "implement it at cost with kube". Even if it's purely standard stuff like PubSubs, or Apache Beam, there are value-added options that are hard to get from other providers (or implement yourself): anything from monitoring to management to scaling to... I'm not to crazy about vendor lock-ins myself, but "abstract everything away and you can easily move over if needed" is largely a myth.