Pythomnic is an application development platform, its architecture affects the applications design, but the opposite is also true. The architecture of the platform itself develops so as to make development of the applications easier. It is therefore important to begin explaining platform architecture with what kind of applications are supposed to be built on top of it.

First, Pythomnic is oriented to building network services - systems which process separate requests arriving from clients over various network protocols. The actual processing such network services perform may be isolated and self sufficient or be middleware "passing the buck" style.

Second, Pythomnic is a platform for developing distributed applications. This means that parts of the application can be run on separate machines, in separate processes, communicating as necessary. Pythomnic also makes it very easy to extract a piece of code from an existing process and turn it into a separate process.

Third, Pythomnic suggests ongoing development. You start with running an empty application, then you just keep adding or modifying code upon a live application. There is no need to shut it down for upgrades or anything.

One area where such applications emerge is integration middleware, where a crowd of independent systems each play by its own ever-changing rules. If the following looks familiar, Pythomnic may be well worth investigating.

The problems to consider in such environment, which really explain the need for Pythomnic are the following:

Integration is difficult, because none of the 3rd party systems deployed in the enterprise are really interested in integration with any other.

Integration capabilities of various systems are very limited. They support different protocols and offer proprietary APIs. Even when a standard protocol compliance is declared, the implementation is often incomplete or broken.

You cannot modify 3rd party systems by yourself. Pushing the vendor to make modifications is often impossible or at least lengthy or expensive.

At the same time, a vendor can modify his system at his own convenience at any time.

Once integrated, the value of the systems increases, the integration middleware becomes more and more important over time, the business is depending on it and its failures are very undesirable.