Difference between revisions of "CloudScale Knowledge Wiki"

From CloudScale
Jump to: navigation, search
Line 4: Line 4:
 
{| style="text-align: center; width: 100%; padding: 2px; vertical-align:top; background: #FAFAFA"
 
{| style="text-align: center; width: 100%; padding: 2px; vertical-align:top; background: #FAFAFA"
 
|-
 
|-
| style="width: 100%; padding-top:2px; font-size:100%" | Welcome to the '''CloudScale Knowledge Wiki'''!<br>You can follow the improvements and results of the project from this wiki site.<br>Learn more about the CloudScale at the [http://www.cloudscale-project.eu project's web site]
+
| style="width: 100%; padding-top:2px; font-size:100%" | Welcome to the '''CloudScale Knowledge Wiki'''!<br>You can follow results on scalability knowledge of the project from this wiki site.<br>Learn more about CloudScale at the [http://www.cloudscale-project.eu project's web site]
   
 
{| style="padding: 2px; width: 100%; vertical-align:top;"
 
{| style="padding: 2px; width: 100%; vertical-align:top;"

Revision as of 16:27, 5 November 2013

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.png

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
Simplified SPOSAD A 3-tier architecture that requires a scalable middle tier.
SPOSAD A 3-tier architecture that requires multi-tenancy and/or scalability.

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

HowNotTos: List of performance anti-patterns.

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.