1. Francesco Masci Suns Solution for Designing Dynamic Service-Optimized Network Architecture: The Service Delivery Network (SDN)

2. SDN Goal

Service delivery at any time, from anywhere, to any device

Approach:consists of basic network building blocks, common network design patterns, integrated network components, and industry best practices

Provide:a set of network connectivity, routing, load balancing, and advanced security mechanisms

Purpose:flexible network infrastructure designs that provide high performance, scalability, availability, security, flexibility, and manageability

3. Services... (in SOA context)

Def : is an implementation of well-defined business functionality

Characteristics

• self-contained (perform predetermined tasks)

• loosely coupled (for independence)

• can be dynamically discovered

• have well defined interfaces and functions (for modularity)

• can be aggregated to build composite services

4. SDN Type of services

End-User Services(Presentation Tier)

• Provided directly to end-users

• Web, e-commerce, e-mail, collaboration

Supporting Services(Integration and Resource Tier)

• Directly support end-user services but are not visible

• Web or Application container,

Infrastructure Services (Management Tier)

• Ease internal operation and support

• internal DHCP, DNS, security or directory services

5. SDN core design components represent the smallest, irreducible component within the pattern or architecture.These building blocks are assembled to provide systemic functionality. is defined as a generalized, reusable design solution to a recurrent network architecture design problem. An instance of a microarchitecture is the network design that results from applying the SDN methodology to a specific organizations stated business and technical requirements 6. SDN Microarchitecture components 7. Phases in SDN Methodology

Select Products

Select Building Blocks

Select Patterns

Design the Logical Architecture

Define the Business Requirements

Define the Functional Requirements

Define the Service-Level Objectives

8. SDN Methodology Messaging infrastructure Case Study 9. Phase 1: Context

Business Requirements

• The e-mail service must use protocols, such as SMTP, IMAP, POP3, HTTP

• Users must be able to use an e-mail client or a WebBrowser to access their e-mail

Functional Requirements (components)

• Messaging mail proxies

• Messaging server

• Directory servers

• Mailbox store

Service-Level Objectives (SLO) -> SLA

• Availability: 99,99%

• Scalability: 2000 total subscriber

• Latency: no greater than 5 second response time for e-mail access

10. Phase 3 Strategies

Product selection and relations

11. Phase 3 Building Blocks

Define the Service Component Types

12. Phase 3 Building Blocks

Mapping Service Components to Service Domains

13. Phase 3- Select Pattern

Service Module Design Pattern or Logical Service Domain

14. Phase 3 Logical Architecture

diagram shows the relationships among the service domains, Intelligent Service Routing (which provides the network path between the service domains), service delivery interface, and secondary access networks (used for integration)

15. Phase 4 Mail Solution design L4-7 16. Phase 4 Mail Solution design L3 17. Phase 4 JES Solution design 18. Phase 4 JES Solution design 19. Francesco Masci [email_address]