I am designing a commercial database app. Originally I'd planned on redistributing a RDBMS (probably PostrgreSQL), so the users would have a DB on their networks. Now I'm wondering if that's such a good idea.
Does every database need the ministrations of a DBA? Or will a well-written app and a reliable RDBMS work without maintenance?
Is installing the database on multiple platforms, hardware etc. a big undertaking?
Short version: it varies. If you include the installation of the RDBMS as part of your software's installation, it can work smoothly. For a database that is specific to your application, you'll probably want to make sure backups are easy for the user to handle.
Ultimately, it all depends on the app, and whether your RDBMS will be doing things besides handling your database.
Thanks for that.
What other things might I be using the RDBMS for? Do you mean sharing it with other (unrelated) database apps?
I'd like to get a feel for the pitfalls of this approach and how much of a support overhead it would entail.
If your customer already has an MS SQL Server or Oracle installation, then they may have dozens or hundreds of databases with various applications interacting with them. Those customers probably won't want to add PostGreSQL to the RDBMS's they have to manage, by the way.
Most any database-driven application will use an RDBMS somewhere.
Now we're getting at the nub of the issue:
What management of RDBMS's is required by the end user? My potential customers have no IT expertise, they just need software that works. It sounds like installing a client-side RDBMS might be a no-no.Those customers probably won't want to add PostGreSQL to the RDBMS's they have to manage...
Am I restricted to selling client-side databases to customers who are willing to employ a DBA?
PostGreSQL sounds like it could be an issue for non-IT folks. I've used Firebird, and found it very easy for customers. SQLite may also be a good option.
There are currently 1 users browsing this thread. (0 members and 1 guests)
Bookmarks