>> How many times have you required that your program runs against different sql databases without modification?
Our main commercial product currently supports 2 database engines, and we'll be offering a 3rd next year. For enterprise offerings it's pretty common for the client to prefer, or outright specify, the engine.
Commodotizing your complementary technology is a good way to not become dependent on any specific database, and hence can pivot quickly when required.
Fortunately I don't have a plane, so I don't have code to fly in any atmosphere.
The rest of us go with Postgres, or SQL server, or Oracle, but definitely don't have to prepare our systems to run in PostgreSQL on Mondays, on SQL server on Tuesdays and so on.
Our main commercial product currently supports 2 database engines, and we'll be offering a 3rd next year. For enterprise offerings it's pretty common for the client to prefer, or outright specify, the engine.
Commodotizing your complementary technology is a good way to not become dependent on any specific database, and hence can pivot quickly when required.
Fortunately I don't have a plane, so I don't have code to fly in any atmosphere.