Potato London | Python / Django Engineer | ONSITE or REMOTE but must be UK based

Potato London is a digital product development agency.

We're currently on the lookout for a talented Python/Django Engineer based in or around London.

So if think you’ve got what it takes to build digital products and services that break new ground for some of the biggest brands on the planet, we can’t wait to hear from you.

For more information, and to apply, head over here: https://p.ota.to/jobs/python-django-engineer-london

1.6 is supported in the alpha, we're aiming for 1.7 support before beta. From that point on we intend to support the two most recent stable Django releases.

We structured the Djangae database connector to be as de-coupled from Django as possible (everything happens at the cursor level) so hopefully keeping up with Django releases should be fairly easy (hopefully!).

There are many benefits, depending on your situation. If your website is expected to get a high QPS, or you have a lot of data (e.g. millions of rows) then using the datastore can be much more suitable (you don't have to deal with schema migrations or connection limits etc.)

You, of course, have to put much more thought into the model design on the datastore and your design should play to the strengths of a non-relational store but once you have that right your site will seamlessly scale.

But CloudSQL is also more suitable in many situations, there are no aggregates or joins on the datastore. You need to to pick and choose the right technology for what you are doing.

Djangae is awesome here, because you use a consistent API for both CloudSQL and the Datastore, which makes switching between the two much easier.

Yeah, we used Django-nonrel and Djangoappengine for a long time, and Djangae is heavily inspired by it. However the advantage that Djangae has is that it works with normal Django - it doesn't require a patched fork like djangoappengine.

As for performance, it depends what you are doing. Obviously the datastore is non-relational so it scales much better with a lot of data, and you don't have to deal with things like migrations or connection limits. But then you can't do complex queries and aggregates etc. the good thing about using Djangae is you can make use of Django's multiple database connections to store your data in whichever form makes sense (datastore or CloudSQL).