
The bottom line
Relational databases enforce structure; NoSQL gives flexibility and pushes responsibility for a sound model onto the design. Get the access-pattern modelling and indexing right and NoSQL delivers excellent scale and developer speed. Get it wrong — over-normalised documents, missing indexes, unbounded arrays, the wrong consistency level — and it degrades badly and expensively under real load. in Exeter We also give an honest fit assessment: for highly relational, transactional data, a relational design (our database design service) is often the better answer. The goal is the right data store, not the trendiest.














