No, "using a product" from a vendor is not vendor lock-in. Especially in the case of a product like this, which turns your employees' work product (queries) from "something that works only with Oracle" (as would be the case if you used Oracle's tooling) into "queries that work with potentially any database."
So when your Oracle rep calls and says "bad news, your license costs went up by 150% this year. What are you going to do, switch databases? Hahahaha!" you can reply "well you know, we can actually flip a switch and run on Postgres now. We'll get back to you."
Yeah, it never quite works out that easily in practice. But by using products from a selection of vendors that support other ecosystems than just one, you're reducing your vendor lock-in.
Comments
No, "using a product" from a vendor is not vendor lock-in. Especially in the case of a product like this, which turns your employees' work product (queries) from "something that works only with Oracle" (as would be the case if you used Oracle's tooling) into "queries that work with potentially any database."
So when your Oracle rep calls and says "bad news, your license costs went up by 150% this year. What are you going to do, switch databases? Hahahaha!" you can reply "well you know, we can actually flip a switch and run on Postgres now. We'll get back to you."
Yeah, it never quite works out that easily in practice. But by using products from a selection of vendors that support other ecosystems than just one, you're reducing your vendor lock-in.