NSFDB2 is dead, or at least, isn't going to be resuscitated, according to Bob Picciano himself. In the Press briefing, he was asked where it was going, and he confirmed that it's going nowhere. The difficulties of managing Notes unstructured data in a structured storage backend are too great. Instead, and this is the good news, the effort is being refocussed on making NSF truly great as the best, and only way, to store and manage Notes data using the best that IBM have to maintain and improve NSF. The way that came over was very, very clear and the implications are very clear. NSF is the backbone of Notes and Domino, and Notes and Domino are the backbone, the centre, the flagship of the Lotus collaboration portfolio.
Comments (9)Mick Moignard January 19th, 2009 11:57:49 AM
I'll drink to that!
That is big news to me. At our company we have just decided to look very seriously at moving the storage of our very large application to NSFDB2 because of View Indexing contention with NSF storage. Looks like we will have to reconsider then.
Thanks for pointing that out. Was there an official announcement I missed?
'cept Mark Haller & Nasir Javed
But now the question is...when do fully dynamic views, joins inside and across nsf and external tool queries against NSF will be possible...saying NSFDB2 is dead and not providing a replacement solution is a little strange position...
@Milos true but nsf2db2 has not been pulled out of the product. It is just not moving forward but you can use it now and wait for what is coming next. If I could choose between saying nothing for years (like it happened with Domino.Doc) and some clear words I would always choose the clear words.
@ Milos and Henning ...
Isn't dynamic views, joins inside and across DBs ... where XPages in the client is heading?
@ Jens - a nightmare of the first order, and one that drove me to sleepless nights - millions of records in single DBs with a view index going corrupt on you mid-afternoon, with 150 customer call staff taking calls - been there a few times now. Splitting DBs up and realigning components of the application to core business process could be the way to go ... huge DBs and indices in Notes just doesn't seem to work. I realise way off topic but the solution to tech problems isn't always tech hey? :-)
No relational capabilities = no future for the application server
{ Link }