This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
teaching:mfe:is [2017/04/19 11:01] svsummer |
teaching:mfe:is [2017/10/25 11:46] msakr [Assessing Existing Communication Protocols In The Context Of DaaS] |
||
|---|---|---|---|
| Line 130: | Line 130: | ||
| **Status**: available | **Status**: available | ||
| - | =====Assessing Existing Communication Protocols In The Context Of DaaS ===== | ||
| - | Data-as-a-Service (DaaS) is an emerging cloud model. The main offering of DaaS is to allow data producers/owners to publish data services on the cloud. The idea of publishing data via a service interface is not new. SOA protocols have enabled this long ago. Yet, these protocols were not developed with the cloud and the big data in mind. This is probably why the term DaaS has emerged. It marks the need for protocols and tools that enable big data exchange. | ||
| - | DaaS services need to exchange large amounts of data. Large here refers to large message size, large message count, or a combination of both. RESTful services, for instance, communicate over HTTP, which is not a good choice for communicating large messages/files. SOAP services are not bound to HTTP, but they introduce another overhead of requiring messages to be strictly formatted in XML. This is why researchers started to reconsider older protocols like the BitTorrent, and suggesting extension to existing protocols like the SOAP with Attachments. | ||
| - | |||
| - | The topic of this thesis is to perform a comprehensive survey on the protocols data exchange, and assess their suitability for DaaS. A quantitative comparison of protocols need to be done, considering at least these two dimensions: (1) the protocol: SOAP, REST, BitTorrent, etc, and (2) the message: short inline, long inline, file. The assessment should be in terms of reliability, performance, and security. | ||
| - | |||
| - | **Deliverables** of the master thesis project | ||
| - | * A report that reviews the state of art communication protocols. | ||
| - | * Propose a tool for DaaS developers to choose the best protocol/s based on their application needs. Such a tool might also provide means of automatically switching between protocols on certain thresholds. | ||
| - | * Experiments to assess the suitability of protocols for DaaS, and to compare between them. These experiments need to be repeatable, so that others can use them on their own datasets and configurations. | ||
| - | |||
| - | **Interested?** | ||
| - | * Contact : [[ezimanyi@ulb.ac.be|Esteban Zimanyi]] | ||
| - | |||
| - | **Status**: available | ||