Difference between revisions of "CloudScale Knowledge Wiki"

From CloudScale
Jump to: navigation, search
Line 14: Line 14:
 
{| class="wikitable sortable"
 
{| class="wikitable sortable"
 
! Name/Link !! Context
 
! Name/Link !! Context
  +
|-
  +
| [[3-Layer Architecture with Stateless Middle Layer CAT | 3-Layer Architecture with Stateless Middle Layer]]
  +
| A 3-layer architecture that requires a scalable middle layer.
 
|-
 
|-
 
| [[Simplified SPOSAD CAT | Simplified SPOSAD]]
 
| [[Simplified SPOSAD CAT | Simplified SPOSAD]]
| A 3-tier architecture that requires a scalable middle tier.
+
| A 3-layer architecture that requires scalable middle and data layers.
 
|-
 
|-
 
| [[SPOSAD CAT | SPOSAD]]
 
| [[SPOSAD CAT | SPOSAD]]
| A 3-tier architecture that requires multi-tenancy and/or scalability.
+
| A 3-layer architecture that requires scalable middle, data layers, and multi-tenancy.
 
|-
 
|-
 
| [[Static Content CAT | Static Content]]
 
| [[Static Content CAT | Static Content]]

Revision as of 08:35, 15 October 2014

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
3-Layer Architecture with Stateless Middle Layer A 3-layer architecture that requires a scalable middle layer.
Simplified SPOSAD A 3-layer architecture that requires scalable middle and data layers.
SPOSAD A 3-layer architecture that requires scalable middle, data layers, and multi-tenancy.
Static Content Specific purpose deployment to handle static content

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

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.