Harsh reality: It will take you 10 years to realize how great our college curriculum is and how critical the core Computer Science subjects are.

Do not get misguided by these "EdTech cum SalesTech" startups and influencers. Everything at scale just boils down to

👇
- Operating system concepts: Mutex, Semaphores, Critical Sections, Thread, Sockets, etc
- Database Internals: Query optimization of Database
- Distributed Systems: Need I say anything here

👇
- Computer Architecture: To understand why vertical scaling has a limit, page faults, cache lines
- Networking: Securing infra, optimizing routing, BGP, CDN, TCP, UDP, etc.
- Multimedia Processing: video encoding, codec conversions, image processing, RTMP, etc

👇
Core CS subjects are more important in the real world. DSA might be there for interviews, but the core CS subjects are mighty critical while at work.

Never neglect them. It will take you a decade to realize ki ya sab to college me hi padha tha.

#ComputerScience #AsliEngineering

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Arpit Bhayani | #AsliEngineering

Arpit Bhayani | #AsliEngineering Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @arpit_bhayani

Apr 7
Implementing Distributed Transactions ⚡ [in a gist]

Distributed Transactions are not theoretical; they are very well used in many systems. An example of it is 10-min food/grocery delivery.

👇
✨ The UX we want is: Users should see orders placed only when we have one food item and a delivery agent available to deliver.

A key feature we want from our databases is atomicity. Our storage layer can choose to provide it through atomic operations or transactions.

👇
We will have 3 microservices: Order, Store, and Delivery.

Important decision: Store services have food, and every food has packets that can be purchased and assigned.

Hence, instead of just playing with the count, we will play with the granular food packets while ordering.

👇
Read 14 tweets
Mar 20
Harsh reality: It will take you 10 years to realize how great our college curriculum is and how critical the core Computer Science subjects are.

Do not get misguided by these "EdTech cum SalesTech" startups and influencers. Everything at scale just boils down to
- Operating system concepts: Mutex, Semaphores, Critical Sections, Thread, Sockets, etc

- Database Internals: Query optimization of Database

- Distributed Systems: Need I say anything here

- Computer Architecture: To understand why vertical scaling has a limit
- Networking: Securing infra, optimizing routing, BGP protocol, CDN, TCP, UDP, etc.

- Multimedia Processing: If you get to build a live streaming platform

to just name a few
Read 4 tweets
Aug 15, 2021
Ever wonder how replication happens between Master and Replica? How changes on Master propagates to Replica?

This is a short thread of how it happens

#systemdesign #distributedsystems

🧵
Any write operation happening on the Master is logged in the Replication log file as an event. The format in which these events are logged in the Log file is called Replication Format.

The two common Replication formats:

- Statement-based format
- Row-based format
✨ Statement-based Format

The Master records the operation as an event in its log, and when the Replica reads this log, it executes the same operation on its copy of data.

This way, the operation on the Master is executed on the Replica, which keeps it in sync with the Master.
Read 11 tweets
Aug 12, 2021
Just wrapped up my 1:1 call with one of my cohort-ian and we ended up building an infinitely scalable Distributed Task Scheduler, AWS CloudWatch Events, DKron, and Quartz Scheduler, in under 30 minutes.

When foundations are clear, no system is harder to design 💪

#systemdesign
The features we discussed and designed were:

- Infinite task ingestion
- 30 second SLA of execution
- Execution Framework that supports Binaries, Scripts, Remote Executions
- Fault tolerance of Scheduler Nodes
- Repeatability of tasks
- Exactly-once schedule and execution
The design we discussed did not just have random boxes of high-funda components but rather the actual tools and techs that we would be using, along with their pros and limitations. 💪
Read 7 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us on Twitter!

:(