APDN
Table of Contents
What's APDN ? APDN mean App Python Distributed Network, APDN is a new way for run Python applications into a middleware. APDN is strong inspired with old grid middlewares architectures, like maui or openpbs. You can see APDN how a global python job queue.
The main characteristics of APDN are :
- With APDN you can run hundred Python application into tens of computer nodes.
- You can choose different scheduler algorithms for load balancing.
- APDN has a small and easy framework for write applications. With this framework is possible describe a deterministic input/output variable.
- APDN has a data model based on users, nodes, applications and namespaces for build different situations.
- You will can use a php or python API for use APDN in anyplace, may be a webserver environment.
- .. and a lot of more.
Main tool for users and developers is mail list, you can use for talk about your experience or ask for any question. Bugs, milestones and other issues about project environment can be follow in trac system.
APDN has a two milestones, the first and more important it's called stable release and second it's called future release.
Stable release is expected for end of this year - 2008 - and it is based into two different goals : make a bug free version and implement some new characteristics. You can visit all tickets related with this milestone.
Future release is a group of advanced characteristics and now are in brainstorm moment.
- Lua or scripting support for performance paral.lel instances with input/output connected. For example with script a
,b=c APDN will run a and c instances at the same time, and then will be connect output of c into input of b
- Master/Slave or Multi Maters architecture for improve APDND fail over.
- Semi decentralized architecture for improve bottleneck of APDND, like GFS. User tools first will connect to
APDND, and this will redirect talk to APDNN.
- Distributed file system for instances
- ... and more
A little architecture description
APDN has a "two side client/server architecture" with three components. One side for communication user with middleware and other side for communication middleware for all nodes. With this architecture user only will see a one entry point but APDN can run any Python application to any node applying some balancing algorithm.

Other papers
End project degree presentation [Cat]
End project degree full paper [Cat]
You can access to subversion repository and checkout all source code
user@localhost:~$ svn co http://apdn.milnou.net/svn apdn