If you've ever seen a NullPointerException in a log, you know how frustrating it can be. You basically have no idea what happened and why. The stack trace is completely useless and you're left debugging an application that you didn't necessarily write. What is this and why does it happen? How do you avoid it?
Quite by accident, I've stumbled upon a rather interesting technology called IPFS. It promises to replace HTTP as a transport protocol for websites and scale to interplanetary levels. Even though the claims sound just tiny bit far fetched, the technology behind it got me quite excited.
So you've been programming for a while, and you are still stumped with what object-oriented programming actually is? Then this may be the guide for you. We'll take a departure from traditional explanations and look at a new way of explaining OOP.
When building larger computer systems, the database soon becomes a bottleneck. Scaling out to more than one machine is an option, but scaling comes at a cost. And that's where the CAP theorem comes into play: it describes how data storage systems behave when run on multiple computers.