Andreas Wolke: TwoSpot. A Cloud Platform for Scaling out Web Applications dynamically
•
0 likes•1,157 views
Andreas Wolke: TwoSpot. A Cloud Platform for Scaling out Web Applications dynamically
Recommended
Recommended
More Related Content
Similar to Andreas Wolke: TwoSpot. A Cloud Platform for Scaling out Web Applications dynamically
Similar to Andreas Wolke: TwoSpot. A Cloud Platform for Scaling out Web Applications dynamically (20)
More from ServiceWave 2010
More from ServiceWave 2010 (20)
Andreas Wolke: TwoSpot. A Cloud Platform for Scaling out Web Applications dynamically
- 1. TwoSpot A Cloud Platform for Scaling out Web Applications dynamically Andreas Wolke andreas.wolke@live.com 14.12.2010 ServiceWave 2010 - TwoSpot (http://goo.gl/JnAxV) 1
- 2. Cloud Computing Stack Platform as a Service 14.12.2010 ServiceWave 2010 - TwoSpot (http://goo.gl/JnAxV) 2
- 3. TwoSpot Web Applications Automated Horizontal Application Scaling Small Resource Footprint Existing Software Standards Multiple Programming Languages 14.12.2010 ServiceWave 2010 - TwoSpot (http://goo.gl/JnAxV) Objectives 3
- 4. TwoSpot 14.12.2010 ServiceWave 2010 - TwoSpot (http://goo.gl/JnAxV) Architecture 4
- 5. TwoSpot 14.12.2010 ServiceWave 2010 - TwoSpot (http://goo.gl/JnAxV) Worker Server 5
- 6. TwoSpot 14.12.2010 ServiceWave 2010 - TwoSpot (http://goo.gl/JnAxV) Starting Application Instances 6
- 7. TwoSpot 14.12.2010 ServiceWave 2010 - TwoSpot (http://goo.gl/JnAxV) Load Distribution 7
- 8. TwoSpot 14.12.2010 ServiceWave 2010 - TwoSpot (http://goo.gl/JnAxV) Scaling Out 8
- 9. TwoSpot 14.12.2010 ServiceWave 2010 - TwoSpot (http://goo.gl/JnAxV) Scaling In 9
- 10. TwoSpot 14.12.2010 ServiceWave 2010 - TwoSpot (http://goo.gl/JnAxV) AppServer Software Stack 10
- 11. TwoSpot Token is passed as a program argument Piggyback Token on each RPC 14.12.2010 ServiceWave 2010 - TwoSpot (http://goo.gl/JnAxV) Platform Services 11
- 12. TwoSpot 14.12.2010 ServiceWave 2010 - TwoSpot (http://goo.gl/JnAxV) Scalability 12
- 13. TwoSpot 14.12.2010 ServiceWave 2010 - TwoSpot (http://goo.gl/JnAxV) 13 TwoSpot http://code.google.com/p/twospot
Editor's Notes
- IaaS only examplesPaaS describe what PaaS providesSaaS only examples
- Controller uses the AppId to determine where to send the request. (to what AppServer to send the request)
- Basically every Worker-Server can process requests for every application. Worker-Server automatically starts AppServers and applications as necessary.
- Worst Case: Frontend distributes request uniformly over all Controllers -> Each Controller is running every application. Frontend should send requests to Controllers which are already running the corresponding application. Frontend needs information where to send Requests. Master receives monitoring data and builds a picture about the platform configuration. Master also does load balancing.
- Worst Case: Frontend distributes request uniformly over all Controllers -> Each Controller is running every application. Frontend should send requests to Controllers which are already running the corresponding application. Frontend needs information where to send Requests. Master receives monitoring data and builds a picture about the platform configuration. Master also does load balancing.
- If an AppServerisrunningwith a lowload check ifotherapplicationinstancesareavailable. Apache ZooKeeper: CentralConfiguration and Synchronization Service