Multi-tenancy in the NoSQL world

Giving more control and autonomy to client organizations may be necessary for your data warehouse. It leads to the complexities of a multi-tenant implementation. Each database technology has inherent constraints, as well as certain advantages. Based on our recent projects, we explore:

Multi-tenancy requirements on the infrastructure, the database itself, and ETL processes
Infrastructure components required
Design alternatives
Compare implementations in relational row-based, columnar, and NoSQL databases

Alex Friedgan builds and promotes data practice at Roundarch Isobar. Alex has worked in multiple roles, including: research engineer, developer, analyst, college professor, database administrator, and data architect. He succeeded in solving problems of statistical analysis, data warehousing, distributed data architecture, enterprise data management, meta-data repository and meta-data stand-alone solutions. He can be reached at alex.friedgan@gmail.com.