EQS: An Elastic and Scalable Message Queue for the Cloud

Elasticidade em cloud computing: conceito, estado da arte e novos desafios

“…Com base na Tabela 2, é possível montar uma análise detalhada das iniciativas da academia para a gerência da elasticidade por nichos. Entre eles, é possível destacar: (i) foco em computação paralela e de alto desempenho [20,30,7,28,8,12,35,21]; (ii) análise do custo financeiro da elasticidade [8,15]; (iii) computação em nuvem de forma federada [44,7,29,25]; (iv) modelo preditivo para detecção de padrões de comportamento de serviços em nuvem [8,22,15,32,31,23]; (v) foco na economia de energia e na superlotação de máquinas virtuais sobre físicas [28,22]; (vi) computação em tempo real e tratamento de deadlines na nuvem [8,22,21,45]; (vii) elasticidade em middlewares orientados a mensagens (MOM) [45]; (viii) cargas de trabalho e aplicações web voltadas para negócios ou área transacional [6,26,12,27,31,46].…”

Brokel: Towards enabling multi-level cloud elasticity on publish/subscribe brokers

“…A common strategy present in the literature to transform a non-elastic application in an elastic one requires changes in the application source code or development of additional scripts. 5,15,[21][22][23]26 It makes the adoption of resource reorganization of cloud-based Pub/Sub applications more difficult, since developers/administrators must have a deep knowledge about both system environment and application code. Moreover, we perceive that elasticity is mainly addressed by solutions employing threshold-based reactive techniques, combining horizontal and replication techniques.…”

“…Moreover, we perceive that elasticity is mainly addressed by solutions employing threshold-based reactive techniques, combining horizontal and replication techniques. 5,15,[21][22][23] Such strategy requires user experience in configuring specific parameters and deploying cloud resources. However, the use of load threshold to guide resource reorganization can cause the problem of VM thrashing, where sporadic peaks exceeding one of the thresholds can result in an undesired elasticity action, being interpreted as a false-positive action.…”

“…However, if the number of publish messages grows quickly, all the solution will be overloaded since all messages are sent to all operations for matching purposes. Elastic Queue Service (EQS) 15 is a message queuing architecture classified as topic-based Pub/Sub, designed to allow elastic scalability, performance, and high availability. Its project concerns the deployment of a Cloud Computing infrastructure using Infrastructure as a Service (IaaS).…”

“…11,[15][16][17] Exploring (5), we perceive that cloud elasticity is widely explored on Web systems, where a unique entry point acts as load balancer and elasticity manager. But, a research question arises: what happens whether the own entry point becomes overloaded?…”