: 74 : 75 : 1 |
Please fix the NSF database
and by 'Fix' i mean:
1) Remove the obvious size limitations such as 32k view lookups, maximum field numbers and plain text field limits
2) Provide a good JDBC and .Net Drivers that enables access to the database from remote locations
3) Improve scaling (yes i know that it has huge theoretical size abilities but the performance degrades a lot when you add lots of documents or lots of views )
4) Externalise the View indexes
5) Provide Sharding in Clusters (optional)
The NSF has done us proud over the years and there have been lots of small improvements with each ODS structure update but it's still not what it should be (too many size limitations and performance problems), and this is the right time to fix it!!
WHY?
1) NoSQL is a growing product platform, estimated to be worth on par with the relational market within about 5 years
2) You already have a hell of a lot of experience in it.
3) You have a existing market for it (Notes apps), which it will help revitalise and is one of the final components in your ongoing "X" cause.
4) It will make money, if Oracle are busy building a proper NoSQL db platform then you know its a good idea. I know quite a few companies that would jump at the change of using a noSQL db from a trusted vendor.
5) The market is still young, you have time!!
You don't have to link it to Notes directly if you don't want to, stick it on the XWork server and call it XNSF or something if you feel like it (as long as Notes apps can access it). Yes I know you have recently given us good relational access, but relational is starting to look a bit old hat for a lot of webscale apps, we NEED a good NoSQL., CouchDb has shown you the way, and MongoDb has taken the ball and is running with it giving developer and businesses what they want, these 2 are the leaders in the document based NoSQL world.
|