bingeHacking

When you study databases, you wonder why some people always seem to get it right, while the majority just doesn't seem to get it right. I will tell you in the next 10 minutes how to get it right - or you get your money back. So, the secret is storytelling. When I think of a database, I think of my friend John who works in front of a big file cabinet like this here: John's job is to keep his boss happy. His boss comes in every now and then and wants to have some information from the file cabinet, like "how many blue cars have we sold in 2021". Sometimes, the boss also tells John some information that he is supposed to write into the files. This takes a lot of time because every folder has an index that needs to be updated (one index is for "car salesmen", the other for "car types" and many more). Plus, there are " aggregates " (how many cars are still in stock) that need to be updated whenever a car sale goes into the folders. And much mor...

I prepare for being certified as Network Engineer. This means you have to digest a lot of complicated topics... or you make it fun by using analogies. I bet I will teach you BGP , Interconnects and VPN in the next 10 minutes so that you won't forget it or you get your money back. Let's start like this: Imagine the internet is the highway network connecting towns (datacenters). Then, the cars are network packets driving over it. If highways are the internet, network packets are cars The cars deliver pizza. There are routes where you can drive fast and there are slow routes. Some have four lanes, others are just narrow alleys. That's latency and bandwidth aka throughput . Now I tell you, if I want a pizza, I want it in 10 minutes. Having 5 pizzas after 50 minutes just isn't the same experience although throughput would be the same.  Next time you wait for a pizza - think of this blog and agree: nothing beats latency ;) Do you know Lombard street? That's the curviest...