170 likes | 328 Views
Disclaimer. I'm not working on something that's really new, state-of-the-art invention but rather I offer an alternative approach to solving an existing problem. Agenda. OverviewA Common Problem in Content DeliveryRevisiting SOAProposed ApproachThe solution flowMeeting the standardsExperime
E N D
1. A Model for QoS-enabled Service Oriented Architecture in the Realm of Content Delivery By Mikael Fernandus Simalango
WISE Research Lab
2. Disclaimer
3. Agenda Overview
A Common Problem in Content Delivery
Revisiting SOA
Proposed Approach
The solution flow
Meeting the standards
Experimental Setup
Immediate Future Work
Conclusion
4. Overview This term paper addresses content delivery problem, that is differentiating service level, using SOA approach and standards like WSRM and WSRMP
However, I havent drawn the final conclusion of the implementation
5. A Common Problem in Content Delivery In todays internet, we are flooded with information
User-generated and provider-generated
Several providers for same or very similar content
Imagine a portal offering services
Lets say its PDF file service (static) and/or video on demand (streaming)
It may host all the files on its own infrastructure or collaborate with other providers, e.g. using commission scheme
6. A Common Problem in Content Delivery Lets see our simple network diagram
7. A Common Problem in Content Delivery Problem defined:
Assume there are N subscribers to a service in a portal. There exists p number of paid subscribers and q number of non-paid subscribers so that p+q = N and Q = {Qp,Qq}N where set Q denotes different QoSes imposed on the subscribers.
We define several parameters U = {availability, reliability, latency, } elem. Q so that for each subscriber using the service, the system is able to evaluate and satisfy QoS provisioning based on subscribers level of significance
8. Revisiting SOA Plain-vanilla SOA interaction pattern
9. Revisiting SOA Partial ESB for enhanced SOA
10. Proposed Approach I try to approach the problem by using SOA through web service hence using SOAP for exchanging messages between requester and provider and WSDL for defining the service
The QoS provisioning is stipulated using emerging standards from OASIS, namely, WS Reliable Messaging (WSRM) and WS Reliable Messaging Policy (WSRMP)
11. Proposed Approach Solution Flow Provider registration to portal
12. Proposed Approach Solution Flow Client requesting service and getting response
13. Proposed Approach Meeting The Standards WS Reliable Messaging:
An interoperable protocol that enables a Reliable Messaging (RM) source to accurately determine the disposition of each message it transmits as perceived by RM Destination
Enables the implementation of a broad range of reliability features which include ordered Delivery, duplicate elimination, and guaranteed receipt
14. Proposed Approach Meeting The Standards WS Reliable Messaging Policy:
Defines a framework, model, and grammar for expressing the requirements and general characteristics of entities in an XML Web services-based system
This framework asserts policy for reliable messaging between RM Source and RM Destination for a given Sequence
15. Experimental Setup Physical infrastructure
A server functioning as the portal
At least two servers functioning as service providers.
Each is installed with glassfish server that supports WS Reliable Messaging
A client utilizing desktop
Experiments
Getting the reliability and latency results for service requesting static content and streaming content
Assess the flexibility of WSRM and WSRMP
16. Future Work Define initial number of service providers x and expanded number of service providers X where x << X.
If t is latency of finding appropriate provider and it is minimum when the number of providers is x, it will be challenging to design a process P that minimizes the latency to t where the number of providers scales to X