AboutPapersTech BitesPhotography
GitHubLinkedInX (Twitter)InstagramYouTube
Interests
Data Structures and AlgorithmsDistributed SystemsSystem DesignArtificial IntelligenceWeb DevelopmentDevOpsFinance
Work
Designing
Upskill
System Design
Fitness
Training
Travelling
Photography
Abhishek Vaishnav

Abhishek Vaishnav

Building atOracleCloud
I got to know..
You can't have exactly once delivery
In distributed systems, you can't have exactly once delivery. You can have at most once delivery or at least once delivery with weighing more towards at least once delivery. This is because of the CAP theorem.
29th June, 2025
View All →
Last whitepaper I've read..
Using Set Cover to Optimize a Large-Scale Low Latency Distributed Graph
It talks about how LinkedIn optimized the feature of showing 1st,2nd,3rd+ degrees on any profile we search on application. In their distributed graph DB, to solve this problem efficiently, they're doing online computation to calculate 2nd degree connections for each member and storing in cache(NCS). But in case of millions of active users, low latency is much needed, hence to keep it, they used NP-Hard greedy set cover algorithm to only make calls to minimal no. of nodes to compute result faster.
8th June, 2025
View All →
placeholder
Abhishek Vaishnav

Abhishek Vaishnav

Building atOracleCloud
Work
Designing
Upskill
System Design
Fitness
Training
Travelling
Photography
Interests
Data Structures and AlgorithmsDistributed SystemsSystem DesignArtificial IntelligenceWeb DevelopmentDevOpsFinance
I got to know..
You can't have exactly once delivery
In distributed systems, you can't have exactly once delivery. You can have at most once delivery or at least once delivery with weighing more towards at least once delivery. This is because of the CAP theorem.
29th June, 2025
View All →
Last whitepaper I've read..
Using Set Cover to Optimize a Large-Scale Low Latency Distributed Graph
It talks about how LinkedIn optimized the feature of showing 1st,2nd,3rd+ degrees on any profile we search on application. In their distributed graph DB, to solve this problem efficiently, they're doing online computation to calculate 2nd degree connections for each member and storing in cache(NCS). But in case of millions of active users, low latency is much needed, hence to keep it, they used NP-Hard greedy set cover algorithm to only make calls to minimal no. of nodes to compute result faster.
8th June, 2025
View All →
placeholder

© 2025 Abhishek Vaishnav. All rights reserved.

GitHubLinkedInX (Twitter)InstagramYouTube