An Overview of Mobile Cloud Computing and SaaS Schemes Discussion

This essay provides a detailed discussion on mobile cloud computing and SaaS schemes, highlighting the benefits and architectural features of these technologies. It explores the use of SaaS and MBaaS in mobile applications, focusing on how these schemes enhance application performance and accessibility. The essay also delves into the Microsoft Azure Platform-as-a-Service (PaaS) architecture, explaining how its components, such as Service Bus Queues and Storage Queues, facilitate inter-communication between applications running on the same cloud. Furthermore, the paper touches on the importance of software patching and updates in maintaining security and improving device performance, referencing scholarly articles to support its arguments and provide a comprehensive overview of the subject matter.

Running head: MOBILE CLOUD COMPUTING AND SaaS SCHEMES 1
Mobile Cloud Computing and SaaS Schemes
Name
Institution
Course
Date

MOBILE CLOUD COMPUTING AND SaaS SCHEMES 2
Change in technology in the current world has led to a far-reaching development in the areas of
mobile internet and cloud computing. A mobile cloud can be accessed through the tablets, laptop
computers, and the smartphone and other portable devices as an internet-based data and
application. Rather than the native apps, the mobile cloud computing runs on a cloud-based web
app. The cloud services allow for subscription which enables the users to access any remote data
over the internet. The SaaS is most popular in cloud computing and it is preferred as the best
type of cloud computing (Buxmann, Hess and Lehmann 2017 p.501). To link different
applications into the cloud storage backend the web and mobile app developers use the Mobile
Backend as a Service (MBaaS).
According to Marinescu and Cadar (2013 p.242) a patch is a mobile software that provides
updates to the devices. The newer version encompasses a more advanced feature as compared to
the previous one. Updating the final software is only made possible with the invention of a newer
software with better features and functionalities. The quality of the software to perform the task
is enhanced by the architectural features such as the patch manager plus server, the central patch
repository and the external patch crawler. Each of the features has special functions for the
updates. Most common targeted applications for patching include the Adobe Reader, Adobe
Flash Player, campus VPN, Firefox, Chrome, Java, Microsoft Office, and iTunes among others.
The main three steps for the software update include:
Step 1. The software patches request the updates
Step 2. If the updates are available, the updated files are downloaded.
Step 3. The current files are replaced with the newly downloaded files.

MOBILE CLOUD COMPUTING AND SaaS SCHEMES 3
The mobile updating software plays a vital role for the current businesses and the world in
general. It reduces the workload of frequent device updating to the IT teams. The automated
updating is considered shorter in its implementation compared to the IT solution developed in-
house. System updating provides security from any attack and also enhances the performance of
the devices.
According to Copeland et al. (2015 p.17) Microsoft Azure is a cloud computing services for
deploying, testing, building, and managing services and applications. It is created by Microsoft
through the Microsoft managed data center. There are various components in the Microsoft
Azure Platform-as-a-Service that allows the inter-communication of different applications
running on the same cloud. An example of the features is the Service Bus Queues and the
Storage Queues. The features focus on the cloud services such as the messaging and the inter-
communication between applications or services which use the PaaS model. According to
Marston et al. (2014 p.185) the Storage queue provides a reliable and persistent messaging
between services running on the same cloud while the Service Bus queues support queuing and
more advanced integration patterns. While a message is written in a queue, other applications
also continue processing messages. However, if the processing is terminated, all the messages
accumulate in the queues until the process is restored. The direct dependency between the
message processor and the front-end sender can cause bottlenecks. However, this is mitigated by
ensuring there is no direct dependency which eliminates the synchronous service calls.

MOBILE CLOUD COMPUTING AND SaaS SCHEMES 4
References
Buxmann, P., Hess, T. and Lehmann, S. (2017) Software as a
Service. Wirtschaftsinformatik, 50(6), pp.500-503.
Marston, S., Li, Z., Bandyopadhyay, S., Zhang, J. and Ghalsasi, A. (2014) Cloud computing—
The business perspective. Decision support systems, 51(1), pp.176-189.
Copeland, M., Soh, J., Puca, A., Manning, M. and Gollob, D. (2015) Microsoft azure and cloud
computing. In Microsoft Azure (pp. 3-26). Apress, Berkeley, CA.
Marinescu, P.D. and Cadar, C. (2013) August. KATCH: high-coverage testing of software
patches. In Proceedings of the 2013 9th Joint Meeting on Foundations of Software
Engineering (pp. 235-245). ACM.