Web applications are growing increasinly more complex, and to speed up development, it makes sense to use pipelined development. This is one of the benefits afforded to the development team using decoupling as an architecture best practice. This deck contains a quick overview of decoupled apps, and how we can use AppFabric to handle decoupling.

1. Decoupled applications with
AppFabric
Anže Vodovnik
(anze@studiopesec.com)

2. Who am I?
• Software Architect @ Studio Pešec
• 10+ years of experience (C#, Java...)
• Highly scalable, distributed applications
• Microsoft Certified Technology Specialist
• http://www.linkedin.com/in/avodovnik
• @avodovnik
• http://lab.studiopesec.com

3. Agenda
• Coupled vs. Decoupled
• AppFabric
• When and where
• Discussion & QA

4. Coupled vs. Decoupled
Business
UI DAL Database
Logic

5. Coupled vs. Decoupled
Business
UI DAL Database
Logic

6. How to communicate through boundaries?
• We know that already: interfaces
• To exchange information we define contracts
• Implementation changes

7. Benefits of decoupling
• Pipelined development
• Different languages/technologies
• Different timelines
• Change agnostic!

8. Scalability
Browser
Decoupling!
Web Server
(ASP.NET, PHP,
(ASP.NET, PHP,
Ruby, …)
Ruby, …)
Sessions
DB
(SQL Server,
MySQL, NoSQL)

9. BUT WAIT A MOMENT
ARE SCALABLE (DISTRIBUTED) APPS
REALLY *THIS* EASY?

10. Apps Browser
AuthN/Z
Web Server
(ASP.NET, PHP,
Ruby, …)
Sessions
AuthN/Z
Services
(WCF, WF, …)
Sessions / State
DB
LOB (SQL Server,
MySQL, NoSQL)
Systems

11. Windows Azure AppFabric
Prog. Models Prog. Models Prog. Models Prog. Models Prog. Models
& Tools & Tools & Tools & Tools & Tools
Introducing AppFabric
Management Management Management Management Management

12. EXAMPLE
TAX RETURN SUBMISSION
APPLICATION

13. High-level architecture

14. Scalability, revisited
• Time-based load, e.g. Tax-return submission

15. AppFabric Queues & Topics
• Load Leveling
• Loose coupling (no consumer?)
• Load balancing
P C
P Queue C
P C

16. AppFabric Queues & Topics
• Microsoft‘s Publish/Subscribe
S C
P Topic S C
S C

17. Why?

18. What‘s better?

19. When & where?
• Potentially scalable application
• Different technologies
• Separate development teams
– Different paces of development
– Different release cadence
• Load leveling & balancing

20. http://lab.studiopesec.com/
SAMPLE OF APPFABRIC QUEUES