mimicry

Design and implementation of distributed systems is typically done in at least two phases: 1. Design and verify algorithm and architecture 1. Implement distributed system accordingly In the first one the actual algorithm and architecture is designed. To verify that the algorithm and architecture of the system scales well you might use network simulators such as ns-2. Those simulators typically require you to write a prototype using a special API. Due to the use of this specialized API and the implied architecture constraints it"s often not feasible to reuse the prototype"s code. After the system has been design and verified to scale the actual production code needs to be written. Finally the built system needs to be tested again. Using integration-tests at this point is often not sufficient since you don"t have fine grained control of the environment and exceptional behaviour that might occur. This is the point where Mimicry

Mimicry_v.0.0.1
bin
lib
bridge
bridge-0.0.1-SNAPSHOT.jar
examples
example-OpenChord.zip
Mimicry.pdf
README
bin
logback.xml
mimicry.sh
mimicry.properties
lib
mimicry-standalone-0.0.1-SNAPSHOT.jar
soot-2.5.0.jar
guava-14.0-rc2.jar
cglib-3.0.jar
asm-4.0.jar
asm-util-4.0.jar
asm-tree-4.0.jar
netty-3.2.6.Final.jar
groovy-all-2.1.3.jar
aspectjtools-1.7.2.jar
aspectjrt-1.7.2.jar
slf4j-api-1.7.5.jar
jul-to-slf4j-1.7.5.jar
log4j-over-slf4j-1.7.5.jar
osgi-over-slf4j-1.7.5.jar
jcommander-1.30.jar
logback-classic-1.0.13.jar
logback-core-1.0.13.jar
core
core-0.0.1-SNAPSHOT.jar