Digests » 325
Vettery is an online hiring marketplace that's changing the way people hire and get hired. Ready for a bold career move? Make a free profile, name your salary, and connect with hiring managers from top employers today.
This is my second write-up on Facebook architecture. In the first, I covered the databases, the persistence tech used @Facebook. In this write-up, I will talk about the real-time chat architecture of Facebook which scales with over multi-billion messages sent every single day.
This article aims to be a primer focusing on systems design interview preparation, but can also be used to simply get better at systems design (a required skill) as a working developer.
One of the more interesting things I’ve had the opportunity to hack on is the Tesla Model 3. It has a built in web browser, free premium LTE, and over-the-air software updates. It’s a network connected computer on wheels that drives really fast.
Developers often use high-end computers to work. Because they need to build, test, and rebuild their projects, they have high-end CPUs. Because they need everything to go fast, they have SSDs or NVMe drives. And because they need to keep tons of tabs open in their browser, they have 16GB or 32GB of RAM. That kind of hardware costs a lot—developers rarely work on a computer priced less than $1,500. But what if we were to tell you that it’s more advantageous to work directly in the cloud. Do you want to know why? Read on!
As a developer, you'll hear a lot of crazy, unbelievable theories about what "lines of code" signify. Believe none of them. Lines of code is a ridiculous metric to base decisions on. In very rare cases it tells you something, in all the other cases, it tells you nothing. Using lines of code to make decisions is like rating book quality by number of pages.