From what I understand, no-SQL databases differ from SQL databases because they allow the developpers to designe the tables to fit the usage, rather than fitting the model. Which means most of the time that if I have an API which uses Cassandra or Neo4J, Cassandra or Neo4J will have one view per API service.
If this is true, then does this mean that if I have a Spark application that fills my no-SQL database, what team in the project should in theory be responsible for Cassandra or Neo4J ? By responsible I mean: creating the tables, defining the table creation standards, delivering the database and the tables to the client... Should the Spark team take care of that because it is the ine filling the table, hence owning the data, or is it the API team because the schemes are designed to feat their application? I guess they will have to communicate, but who would perform these tasks ?