Presentation

THE µSOA PLATFORM

Since google disabled the addition of new downloads
the latest build can be found here: http://rupy.se/rupy.zip rupy.zip or https://github.com/tinspin/rupy github.

NEW - Async [https://code.google.com/p/rupy/wiki/Fuse FUSE] and [https://code.google.com/p/rupy/wiki/Persistence ROOT] cloud database.

NEW - Version [http://rupy.googlecode.com/files/rupy-1.1.zip 1.1] with real-time [https://code.google.com/p/rupy/wiki/CometStream cometstream]^1^.

NEW - Perfect^2^ for distributed raspberry pi 2 cluster.

NEW - Try our [http://en.wikipedia.org/wiki/Platform_as_a_service PaaS]^3^ solution: [http://host.rupy.se host.rupy.se], now with [http://code.google.com/p/rupy/wiki/Tutorial#remote tutorial].

Weighing 94KB, rupy is probably the smallest, fastest and most

energy efficient HTTP application server in the world.

With rupy you get a similar simplicity to interpreted development

(like php, ruby or node) but with high performance and seamless

complete product hot-deployment, potentially across a cluster!

This enables you to work against some remote server with external

integrations and other team members at zero turnaround and

downtime!

rupy is inherently non-blocking asynchronous, which makes it the

ideal candidate for high concurrency real-time applications pushing

dynamic data.

Tested with [http://jakarta.apache.org/jmeter/ jmeter], rupy performs ~1.000 messages per second

on a raspberry pi 1 (try the competition for that). If you want a real-

world example of rupy in action head over to [http://sprout.googlecode.com sprout]; a simple

blogger.

|| Features || Status Codes || Headers ||
|| Non-Blocking IO || 200 OK || X-Forwarded-For ||
|| Asynchronous Push || 302 Found || Cache-Control ||
|| Chunked Transfer || 304 Not Modified || Set-Cookie ||
|| Session Timeout || 400 Bad Request || Cookie ||
|| True^4^ Hot-Deploy || 404 Not Found || ||
|| Filter Chain || 500 Internal Server Error || ||
|| || 505 Not Supported || ||

^1^ Not as overengineered as websockets.

^2^ It only consumes ~0.015mJ per request, but the biggest gain

is that idle power is around 1W (which is equivalent to other

processors sleep) and since web servers are mostly underutilized

this is where you save the majority of energy.

^3^ Our cluster is made up of raspberry pi's. We enable cluster hot

deployment and low latency multicast messaging between local

applications in the cluster.

^4^ With rupy you can deploy a completely new release without the

users being logged out. This is very convenient during development

too.

[http://rupy.se ]http://host.rupy.se/powered.png
[http://bitcoinbankbook.com ]http://host.rupy.se/btc.png
[http://raspberrypi.org ]http://host.rupy.se/rpi.png