Hivemind

_images/logo_flat_medium.png

The python micro service prototyping sandbox on a budget!

The What

_images/basic_diagram.svg

A fast, effective, way to generate independent process that can communicate through a centralized control without requiring the entire network to be up at once.

The paradigm for service/subscription processes is not new. In fact, it’s become quite common in utilities like RabbitMQ, ROS (Robot Operating System) and others.

hivemind seeks to add a few features to that paradigm.

  1. Insanely fast development throughput with little to know need to understand the “under-the-hood” components

  2. Lean-and-mean data layer(s) to help organize your data without any concrete overhead

  3. (Most importantly) - we want to make it nearly impossible to take down in production environments.

The Why

_images/scale_diagram.svg

In the modern app arena, we often have use for very atomic level operations that need to communicate with other such atomic services. This often leads to large waterfall code, promises, or some form of chain-reactive system when instead we want these operations to be self sufficient when perhaps the network isn’t running as smooth as it should. In order to create a highly independent system, we turn to service/subscription models (also known as pub-sub models) in order to keep the low level “nodes” from needing anything but themselves and a connection to a sort-of central nervous system.

This approach can take many forms and doesn’t fit all use cases but it’s a powerful tool for horizontally scaling your software.

Indices and tables