CloudScale Knowledge Wiki

From CloudScale
Revision as of 16:29, 15 January 2015 by Sebastian.lehrig (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
Welcome to the CloudScale Knowledge Wiki!
You can follow results on scalability knowledge of the project from this wiki site.
Learn more about CloudScale at the project's web site

CloudScale is a Framework Programme Seven (FP7) European Commission funding technological project, aiming to aid service providers in analysing, predicting and resolving scalability issues, i.e., support scalable service engineering.

The project extends existing and develops new solutions that support the handling of scalability problems of software-based services.

CloudScale's HowTos provide best practices for designing and analyzing scalable SaaS applications. In the following table, we list and describe the collected HowTos.

Name/Link Context* ATs
Loadbalancing An architecture utilizing load balancers. 2
Dynamic Horizontal Scaling An architecture utilizing horizontal scaling. 2
Dynamic Vertical Scaling An architecture utilizing vertical scaling. 1
Simplified SPOSAD A 3-layer architecture that requires scalable middle and data layers. 1
SPOSAD A 3-layer architecture that requires scalable middle, data layers, and multi-tenancy. 1
Static Content Specific purpose deployment to handle static content 0
Sharding Separating data into storage partitions. 0
MapReduce Process large data sets by distributing processing nodes 0

Our common ontology for topics related to performance, scalability, elasticity, and efficiency of software architectures.

Date Title*
2013-08 Palladio Workshop
2014-04 Quality Analysis Lab
2014-10 ScaleDL Overview - 2nd Draft

While patterns provide proven solutions with positive effects, anti-patterns record those solutions with negative consequences. Anti-patterns show software engineers what to avoid as well as solutions. In the following table, we list the anti-patterns we collect.

Name/Link Context*
One-Lane Bridge A One Lane Bridge occurs, if a passive resource limits the concurrency in an application. Passive resources can be for instance mutexes, connection pools, or database locks.
The Blob The Blob occurs when one class performs most of the system work relegating other classes to minor, supporting roles.
The Stifle The Stifle occurs if single datatabse statemens changing the data are executed for the same table in a loop instead in a batch.