NoSQL screwing up
This post is regarding my current (previous in case I quit before you see this) company. The company has been using RDBMS since years, which is trusted. Architects here started using Couchbase just because NoSQL gives options to scale big time. But the user permissions of each control is in RDBMS, which is pulled while Login and saved in access token in Couchbase. Another problem arise that the admins can grant and revoke permissions of any user or user group on any content or any specific collection of contents, let's call it document X. To use triggers there were about 25 tables which were needed to be applied. Syncing with RDBMS for every query was a big problem. They decided to keep a copy of the permissions into Couchbase and sync only the permission documents. It was also too much effort to sync using the triggers or a scheduled job. This was the most unfeasible option to take, when the database structure is already too big. Let's see other architectura...