Script to generate rate limited (msg/sec) load
Continuation of T/dT, U/dU reasoning
Describing charging dimensions
Rename Billing to Computational aspects and move after Architecture
Finishing (for now) the description of events
Add events modeling.
AquariumEvent and ResourceEvent.
Start describing events
Slight reorg (Implementation -> Domain Modeling).
1. Added terminology2. Moved stuff from the DSL description to the basic terminology3. Started using term `charging` instead of `billing`
More on architecture
Initial architecture blurb
Start describing billing-related stuff.
Split arhitecture in another file to avoid conflicts
More on billing
Bit of text rearrangement, billing descriptions
A great contribution to the paper.
Implementation experience
Some text on Aquarium requirements and benchmarking
Skeleton for the Aquarium architectural description