Thursday 16 February 2017

Optimizing Elastic IoT Application Deployments

This paper is quite perfect.
It has a layered, modular approach to building 
it's framework for the dynamic generation of optimized deployment topologies for IoT cloud based on a declarative, constraint-based model.

Motivations & Strengths:
1. It suites the pay-as-you-go pricing model perfectly. 

2. The cost benefit tradeoff using edge infrastructure adds on to huge savings for organizations.
3. For their design choices, modularity. The whole design is multi-layered so much so that pieces of it like Diane, TU and DU, Leonore can be utilized by organizations separately.
4. The paper is extremely detailed with specifics about implementation, this makes it easy to modify and customize as per our requirements. 
5. Flexible Approach. The paper makes way for a dynamic edge-environment, resource pooling, pool requests etc-
6. Optimizations on top: Like a final icing on cake, there are run-time adaptive optimizations [Elastic Application Deployment] and TU DU Optimization Units which utilise run time information to take decisions based on multiple metrics.
7. Other Strong optimizations to user api, server extensions with white box and black box modes. 
8. It handles fault tolerance well since it follows an "N+1" approach for assigning Leonores. 
9. There are no security concerns which I could identify in this paper either. All information to be passed needs secure channels which is left upon the organization to ensure. 
10. The even have an Optimization registry.
11. Keeping Options in optimizations.

Discussion:
1) How can we make anything better than this? Is there an improvement possible for this paper?

2) Is it worth the effort from an organization's point of view? How much extra cost is this infrastructure going to cost to an organization?

Weaknesses:
1. Despite of the modular approach, the modules seem to be tightly coupled together. They give the notion of modularity, which would be complex in practice. 

2. IoT Application Execution - They only talk about the Execution time and Bandwidth consumption. However, a cost function might have been in order since the motivation is cost.
3. Edge devices often have power constraints, this paper does not take them into consideration - or does not speak about it.

2 comments:

  1. What is the research contribution of the paper? There is some nice engineering. Is the evaluation convincing?

    ReplyDelete
  2. The evaluation is not convincing. They have not shown the base case Vs Black Box Case. Moreover, specifics have been omitted.
    Qualitatively this seems to be a nice paper which many optimizations implemented and running in one system. There is possibly a lot to learn in bits and pieces even if the system is never adopted as a whole, especially the concept of TU/DU and White Box optimizations.
    Research contribution: From research stand point, the contribution may not be much because the evaluation was not convincing and improvements were less. However, making a modular system working upon many concepts such as Diane, TU and DU, Leonore and White Box optional optimizations might have something to learn from.

    ReplyDelete

Note: only a member of this blog may post a comment.