Michael Luca

Software 👨‍💻 Jiu-Jitsu 🥋 and Guitar 🎸

[Michael Luca @M_GLuca]

@Matt_Pinner

[Programmer Humor @PR0GRAMMERHUM0R]

theCosmicMysteryOfProgramming https://t.co/TcyEokcIAv

[Programmer Humor @PR0GRAMMERHUM0R]

stillJunior https://t.co/GjxLZcVZ7P

[Alex Xu @alexxubyte]

The Open Source AI Stack

What did we miss?

[TRÄW🤟 @thatstraw]

This is cute! Inside the Linux Kernel🐧

[sysxplore @sysxplore]

SQL JOINS Cheat Sheet

[Michael Luca @M_GLuca]

What debugging on Xcode feels like!

[Bytebytego @bytebytego]

How to scale a website to support millions of users? We will explain this step-by-step.

The diagram below illustrates the evolution of a simplified eCommerce website. It goes from a monolithic design on one single server, to a service-oriented/microservice architecture.

Suppose we have two services: inventory service (handles product descriptions and inventory management) and user service (handles user information, registration, login, etc.).

Step 1 - With the growth of the user base, one single application server cannot handle the traffic anymore. We put the application server and the database server into two separate servers.

Step 2 - The business continues to grow, and a single application server is no longer enough. So we deploy a cluster of application servers.

Step 3 - Now the incoming requests have to be routed to multiple application servers, how can we ensure each application server gets an even load? The load balancer handles this nicely.

Step 4 - With the business continuing to grow, the database might become the bottleneck. To mitigate this, we separate reads and writes in a way that frequent read queries go to read replicas. With this setup, the throughput for the database writes can be greatly increased.

Step 5 - Suppose the business continues to grow. One single database cannot handle the load on both the inventory table and user table. We have a few options:

1. Vertical partition. Adding more power (CPU, RAM, etc.) to the database server. It has a hard limit.
2. Horizontal partition by adding more database servers.
3. Adding a caching layer to offload read requests.

Step 6 - Now we can modularize the functions into different services. The architecture becomes service-oriented / microservice.

Question: what else do we need to support an e-commerce website at Amazon’s scale?

--
Subscribe to our weekly newsletter to get a Free System Design PDF (158 pages): https://t.co/eVEdOFSYPY

[tetsuo @tetsuoai]

14 Sorting Algorithms in 1 Minute.

[Michael Luca @M_GLuca]

I scored 16/20 on MIST-20, better than 73% of the UK population. Test your misinformation susceptibility now! What is #YourMIST? 🧐 https://t.co/fUkqrdx725 #misinformation #fakenews

[GitHub Projects Community @GithubProjects]

That moment when:

[Nature is Amazing ☘️ @AMAZlNGNATURE]

If you pet a seal there’s a chance it will pet you back

[Ben Dicken @BenjDicken]

You asked for it, so here it is.

Visualizing CPU cache speeds relative to RAM.

Cache optimization is important too!

[HackerRank @hackerrank]

Skills Over Pedigree 💪🏼

[HackerRank @hackerrank]

Happy Monday everyone! ✨

[Michael Luca @M_GLuca]

@harshleenchawl2 Arch, by the way!

[Michael Luca @M_GLuca]

@shahzadahmad246 Switch to Fedora

[Michael Luca @M_GLuca]

@historyrock_ The Warrior - Orphaned Land (at 03:05)

[Massimo @Rainmaker1973]

IT acronyms deciphered
https://t.co/c4D9Pi2Gql

[Massimo @Rainmaker1973]

This is how the binary system works, explained with an ingenious wooden counter.
https://t.co/Pjjw06FJmM