Last active
June 25, 2017 05:19
-
-
Save neerajgoel82/70de7a34ca6eb0381ddc80fbf0d7d6a2 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Bloom Filters (https://www.youtube.com/watch?v=-SuTGoFYjZs&index=10&list=PLmVb1OknmNJuC5POdcDv5oCS7_OUkDgpj) | |
- Consistent Hashing (https://www.youtube.com/watch?v=jznJKL0CrxM&index=13&list=PLmVb1OknmNJuC5POdcDv5oCS7_OUkDgpj) | |
- String Interning (https://www.youtube.com/watch?v=2C71YTKklT8&index=15&list=PLmVb1OknmNJuC5POdcDv5oCS7_OUkDgpj) | |
- Cryptographic Hash Functions (https://www.youtube.com/watch?v=D65JQ0qQwZk&index=12&list=PLmVb1OknmNJuC5POdcDv5oCS7_OUkDgpj) | |
- Pre-Image Resistant (Output => input should be difficult) | |
- Second Pre-Image Resistant (nearby strings should have different hash values) | |
- Collision Resistant (No two inputs have same output | |
- Video on Dynamo (Dynamo : paper that changed databases) | |
- PAC-ELC theorem + CAP theorem | |
- Consistent Hashing | |
- P2P system | |
- Martin Fowler Talk on NoSQL (https://www.youtube.com/watch?v=qI_g07C_Q5I) | |
- Impedance mismatch with relational DB | |
- Consistency vs Availability | |
- Consistency vs Latency | |
- Consistency are of two kinds (Logical and due to replication) | |
- NoSQL (other than Graph) - Aggregate Oriented DBs | |
- Aggregate Oriented DBs by their semantics generally don’t require logical consistency guarantees | |
- Drivers of NoSQL DBs | |
- Large Scale Data | |
- Easier development (Solves impedance mismatch) | |
- Analytics use cases | |
- Polyglot Persistence | |
- Martin Fowler talk on Technically excellent organization (https://www.youtube.com/watch?v=Avs70dZ3Vlk) | |
- Continuous Delivery (Less cycle time for features) | |
- Small, business oriented, autonomous teams - Should be customer facing | |
- Trust within teams | |
- Teams should be technology led | |
- Strategy (Speed,Inventiveness is important) vs Utility(Ensure lower cost and avoid disaster) | |
LRU/LFU policies | |
-Traffic? | |
-Kinds of values? | |
-Cache invalidation/update? | |
-In memory vs persistent | |
-Response time? — Expected response time | |
-Load? - QPS? Read vs Write? | |
-Volume? - Both per request … Total data to be processed | |
-Language support? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment