One of my clients is proposing a project that requires good storage
performance and high reliability. It's an entirely new project so there's no
legacy code to deal with.
Russell, before choosing a technology... it might pay to give some rough ball parks of data sizes and potential size of growth and traffic you would expect to see. This will help determine the tech selected. Remember what goes in today becomes the next decades legacy app.
Does anyone have any suggestions for planning at this early stage?
Some specs first before jumping in.... Also have you had experience with NoSQL databases? It's quite a leap from a traditional RDBMS if you've never gone that way before.
I wouldn't rule out a clustered database so quickly. See what features the project requires then match the technlogy.