Ask HN: I think I need to use NoSQL?
However after spending a week inheriting a prototype which is all over the place. I am starting to think I will have to use something I never dreamed of using; NoSQL whether that be MongoDB, Redis or Cassandra.
To give you some background:
A large enterprise with ageing software infrastructure is looking to replace a system which consists of
A COBOL terminal app, 3 VB powered spreadsheets and a lot of emailing.
The solution the team has prototyped is effectively a spreadsheet with a business rules engine.
This spreadsheet at the moment has lots of tabular data and could change over time.
I've spent several sessions with my team looking at entities and mapping their relationships. However we keep hitting ruts.
There are other issues too:
* The business / stakeholders, can't agree on what data is needed and it is constantly changing
* The current schema has several tables but are just filled with CLOBs that store JSON
* A lot of the data the business wants presented would be hard to store in a normalised format
* The frontend is making multiple API calls from different services and assembling a document in redux / local storage. This is an antipattern!
* Business priorities are changing every sprint / product owner is getting arm twisted to add new "fields" , so that department X can get more out of this app
* The relational model could cause added maintenance and refactoring when new changes come around
However I have concerns against suggesting this:
* I am in a junior heavy team, with noobies
* Seniors are scared of new practices.
* I don't know how easy it is to do things like business reporting etc.
* It would mean a heavy refactor of the internal models
* How do I transplant existing data on production into a new DB technology?
* I have very little experience in NoSQL
Looking for people's thoughts or suggestions.