Web app outgrowing current framework

Question

I have quite a bit of experience with using Django for websites and so when I started a new project I naturally chose to use Django for it. Everything went well for a time but now the application is really starting to rub up against what Django can comfortably cope with and I fighting all the time to ensure that things work as intended.

I've been considering moving the site over to Java EE 7 now that it has been released. It certainly seems to provide the features I require as well as also being less forceful in the way that a project is laid out and maintained. I guess now that I have a good idea of how the application should be structured, development should be much faster.

Have you felt the need to change the web framework you are using simply because it doesn't lend itself well to the type of project you are trying to produce?

Answer 1

You say:

The problem I'm currently facing is mixing a website frontend with a distributed backend written in differnet languages (there is some C++, Erlang and Haskell stuff to consider). Tasks need to be dispatched from the web frontend to the many backends asynchronously and reliably as well as also having certain tasks run regularly like a cron script but spread amongst these different systems. I'm striggling to find a clean and elegant solution for all these requirements in Django.

Reading this I am not sure that this is a Django problem, or even a web framework problem, but more that you should be looking at using some kind of message queue to send messages back and forth.

Something like RabbitMQ and Celery might be what you are looking for. These will let you dispatch tasks to the backends and also schedule tasks as you need them.