In the previous part, we explored the low-level components of a distributed system, including how they communicate and the topologies they can form. Until now, we did not care how a component was designed, and we simply put some logic around a socket. The component itself looked like a small script connecting to other components via something like Mangos or NATS. We will now shift focus to how a component should be designed and what good practices and architectural patterns we should use.