Re: Mote/MapTool: Thoughts on a DB choice
Posted: Fri Mar 28, 2014 7:10 am
I speak from complete ignorance as to how they plan to integrate the DB.
The problem JML refers to is that if you have multiple database types supported then you also have to support porting between them. Data won't just magically go from one to the other without a tool, some work, and a bit of cussing. From a dev point of view, integrating with one will be easier. My hope is that the binding with the database is loose so that others can be supported if need be but during development they should pick one and stick with it.
In your case, you're speaking of dev, test, and prod and its not uncommon to have different environments there. Now think of those same statements only in prod, which would be the case for a deployed MapTool. That's a harder case to make for swappable DBs.
Not that you can't just plop in a driver. The problem comes in the data and leveraging special features of each database. If you use something other than H2 then there is a reason, something you want out of the other database that might be different in another. Accounting for that in code will send the devs running into the hills screaming.
My 2 cents.
Cheers,
Keith
The problem JML refers to is that if you have multiple database types supported then you also have to support porting between them. Data won't just magically go from one to the other without a tool, some work, and a bit of cussing. From a dev point of view, integrating with one will be easier. My hope is that the binding with the database is loose so that others can be supported if need be but during development they should pick one and stick with it.
In your case, you're speaking of dev, test, and prod and its not uncommon to have different environments there. Now think of those same statements only in prod, which would be the case for a deployed MapTool. That's a harder case to make for swappable DBs.
Not that you can't just plop in a driver. The problem comes in the data and leveraging special features of each database. If you use something other than H2 then there is a reason, something you want out of the other database that might be different in another. Accounting for that in code will send the devs running into the hills screaming.
My 2 cents.
Cheers,
Keith