backends

Both Synapse and Nerve support custom backends using whatever system you want (zookeeper, etcd, DNS, etc).

For example, nowadays you have a lot of those stateless redundant S3 compatible storage backends.

For people who are more comfortable on backends, learn React, which will take you through a nice swathe of modern front-end tools and practices.

As you may know, getting matplotlib to work properly with backends like TkAgg can be quite a chore when installing using pip (non-python libraries are needed).

Looking to expand it to shopify and other ecommerce backends.

I would rather see something like Ubuntu Touch tries where they write the frontend with QML and you can have backends in C++ for speed.

It supports a wide range of backends such as PDF, SVG, PNG and a range of GUIs like Qt, so it is easy to use both for static and interactive graphs.

Convox is a little more reliant on AWS, whereas Empire was designed to be able to work with other backends like Kubernetes for example (not implemented yet).

I wrote a basic VSXu plugin for both Amarok and Tomahawk media players but had to put them on a pause because of the bad state of Phonon Backends back then.

* Real world experience with django/python backends.

Since the focus seems to be on web backends (given the section following this one), I'd imagine that trying to use C or C++ for such a thing would not be one of the obvious choices.

We (Django) had a rather frustrating mailing-list exchange with IBM folks who wanted to build a DB2 driver for Django; they claimed their corporate policies wouldn't allow them to look at the existing Django DB backends, or anything BSD-licensed, to gather information on the API.

Lately I am trying to "dockerize" my backends, so in the case my workspace project needs a mongoDB or an other backend from my architecture, I should be pulling those containers up on converging.