I have a requirement to perform some security checks during the request response cycle. these security checks are based on user profiles. Since these checks have to be done during the request-response cycle and the amount of time to do security checks also needs to be considered.
With all this into consideration, i have designed my schema accordingly, the tables designed are doing lookup based on partition_key all the time, but for some scenarios i may have to do multiple queries (again based on partition_key)
- it's a read heavy application, and anyway writes are cheaper so that is working fine, getting < 20ms for writes
- i don't have any clustering column for any of the table, so partitions are small in size
- using Cassandra for this solution as the user base is global and Cassandra takes care of replication and syncing user profiles across clusters
Ques: Is 40ms with possibly 2-3 queries in single request-response possible at all?
Is there any better way to do this?