This document discusses cloud scaling using Azure. It defines scalability as a system's ability to handle increased workloads gracefully. Performance and scalability are different - scalability is about how a system responds to increased demand rather than raw speed. Azure Cloud Services and Service Bus provide scalable solutions. Service Bus uses queues to allow loosely coupled messaging between apps, offering reliable delivery through protocols like REST and AMQP. It was demonstrated how Service Bus queues can pull messages using techniques like receive and delete or peek lock to improve scalability.

1. Easy cloud scaling with Azure
Bogdan Mustață, Team Leader, Levi9

2. Agenda
Scalability
Performance
Azure Cloud Service
Azure Service Bus
Demo
Q&A

3. What we want for Web App?
High Scalability
High Availability
Performance
Low Cost
Features

4. Scalability
What is scalability ?
Scalability is the ability of a system, network, or process to
handle a growing amount of work in a graceful manner or its
ability to be enlarged as demands increase.
What scalability is not :
Raw speed or performance (2 GHz vs 3 GHz)
About the operating system
About a particular software technology (Java vs .Net)
About optimized code

5. Performance and
Scalability are NOT the
same …

6. Performance

7. Scalability

8. More Scalability

9. Azure Cloud Service

10. What Cloud Service?
n n

11. Why Cloud Service?

12. Scaling strategies
Don’t re-invent the wheel, copy someone
else CQRS – Command Query Responsibility
Segregation
Architecture Simplicity
Caching, Database partitioning, Queues
Think horizontal … not vertical … on
everything
(How many ? Vs How Fast ?)

13. Azure Service Bus

14. Azure Service Bus
Service Bus is messaging infrastructure that sits between
applications allowing them to exchange messages in a
loosely coupled way for improved scale and resiliency.
Service Bus Queues offer simple first in, first out
guaranteed message delivery and supports a range of
standard protocols (REST, AMQP, WS*) and API’s to
put/pull messages on/off a queue.

15. Service Bus - Ways to Pull
Receive and Delete
Fastest. Message lost if receiver
crashes or transmission fails.
Peek Lock
Message is locked when retrieved.
Reappears on broker when not
deleted within lock timeout.
Transactional
Local model

16. Service Bus - Messages
Properties are
key/value pairs that
may very well carry
payloads
Message bodies are
useful for a single
opaque payload not
exposed to the
broker (e.g.
encrypted content)

17. Queues

18. Topics

19. Demo

20. Q&A
Contact
Mustață Bogdan, Team Leader, Levi9
bmustata@yahoo.com
http://www.linkedin.com/in/bogdanmustata
Links
http://www.windowsazure.com/
http://www.windowsazure.com/en-us/develop/net/
http://www.levi9.com/