ADOPTING CLOUD PLATFORMS

Name

University
Part I:

i. Write down justifications as to why adopting Cloud Platforms would be beneficial to

Kwaya’s business. Make specific reference to Kwaya and the music streaming
industry. (3 marks)
Answer:
In comparison to hosting on a server at home, the cloud may provide Kwaya's firm
with greater general adaptability. Furthermore, if you require additional connectivity,
a service that uses the cloud may satisfy that demand immediately rather than
requiring a sophisticated (and costly) upgrade to the IT system (NELSON, 2009).
This increased autonomy and adaptability can have a substantial impact on your
organization's overall productivity. Considering the current situation of the
environment, it is not anymore sufficient for Kwaya's company to set up a recycling
container in the breakroom and declare that their actions are helping the earth. True
sustainability necessitates solutions to tackle inefficiency at all tiers of a company.
The cloud-based system has also aided the music business, notably Kwala, in terms of
streaming services that play music. Cloud audio transmission refers to the delivery of
audio, which includes music, via the web. Kwala's clients may access music via the
internet and play to them anytime they're interested with cloud musical providers. It
enables them to instantly transfer audio files or capture them using an audio internet
player. Spotify is a perfect instance of a cloud-based audio streaming platform that
enables users to listen to songs across the web using a sound cloud player.

ii. Provide a brief writeup to the management of how they would go about their cloud
adoption journey. (4 marks)
Answer:
Management needs to start by assessing the company's ramifications of implementing
a cloud-based platform. Decision-makers have to know how the cloud stands out
from conventional IT systems. They have to be prepared to examine the company's
overall and IT-specific advantages, risks, and regulation, safety, and data
management concerns. For maximum productivity and management must carefully
review the architecture and its degree of complexity, and figure out if it's possible to
entirely shift toward the cloud or merely whether it would be more affordable to
migrate a handful of apps onto the cloud and leave the remainder on-premises
(Golightly et al., 2022). It will be time for management to select the cloud as their
platform after they have examined and identified the conditions within it. There are
numerous vendors of cloud services, all having their own design and set of capacity,
authorization, and assistance.
iii. Given that Kwaya elect to move to the cloud, what are 5 antipatterns that they should
avoid in their Cloud Adoption Strategy. Explain how these antipatterns are relevant to
Kwaya. (2 marks)
Answer:

Here are the lsits of 5 antipatterns that should avoid:

1: Scaling, i.e. local optimization is hampered by rebuilding the mechanism.
This fosters both a thorough awareness of Kwaya's business issues and a strong desire
to see them through. Nevertheless, one unintended consequence is that each team
prefers to develop its own build and deployment report of their marketing and sales
weekly, as well as tracking equipment. Furthermore, numerous teams at Kwala end
up handling similar challenges in a variety of ways using a variety of technologies.
2: System capabilities that are too focused on the present are not fit for the
future.
The typical enterprise's perspective of evaluating a platform based on its current
requirements, rather than how it will change in the order in order to satisfy Kwala's
business requirements throughout the near and long future, is a key barrier when
developing systems. 'Buy and integrate' represents a viable technique for retaining
the management of future developments for such elements. If required it aids in
aligning with the for a long time IT plan and developing future-perfect competencies. 
  3: Monolithic structures for data do not match the needs for innovation and
scalability.
The sources of failure of data systems constructed around the information sheet
architecture are prevalent, resulting in disappointments in scalability. To overcome
these types of failures, we must abandon the idea of a centralized data warehouse. As
a result, Kwala should adopt a framework based on modern networked architecture,
such as addressing domains as first-class concerns, employing platform design to
construct self-service data facilities and approaching data as a business.
4: Connectivity and misaligned teams were exacerbated by fuzzy service limits.
Kwala is unable to create a distributed platform while thinking in terms of monoliths.
If properly developed, a distributed system has the advantages of progressively
releasing and scaling independent portions.
5: Being isolated from the environment slows and lowers the quality of innovation.
Businesses have traditionally owned (built or purchased) whatever capability given to
their clients. It is critical to foster an ecosystem view of Kwala's business, in which
we harness others' strengths while also exposing their own capability to others. This
assists the firm in maintaining its inventiveness.
Part II:
i. Extract attachments from your email and store them in Azure Blob Storage using this
scheme. (5 marks)
Answer:

I have created the storage in the logic app and launch the Microsoft Azure Storage
Explorer where we could create the attachment storage in the environment and show
below:

ii. Send you an email at the end of the day with the total number of tracks that have
been submitted for that day. (5 marks) With screenshots show how you would set
these up in Microsoft Azure. Emphasise and justify any custom configurations that
you are making.

Answer:
I setup this workflow by first creating a blank Logic App as shown below:

Next is adding a trigger to check incoming email:

Next is checking my attachments created:
Then here is my code view after the creation:

Next step I have done is testing my conditions, I start it by running the trigger and we
got successful results below:
Next step I have done is formulating “Call RemoveHTMLFunction” as shown
below:

Next is creating “blob email body:

Next is creating email attachment:

Final configuration is reviewing the email:

Hence, here is the final Logic App designer created for Kwala’s business:
 For the data, we stored it in the form of
<Year>/<Month>/<WeekNumber>/<Day>/<FileName>.csv.
I used the array actions of “Create CSV table”.
Utilize the Compose action to create an one output, including a JSON item, from
numerous inputs. The output is able to be employed in actions that accompany the
Compose action. The Compose action additionally stops you from inputting identical
inputs over and over while creating the workflow for the logic within the app. The
Compose action with the preceding instance receives the subsequent inputs:

<Year>/<Month>/<WeekNumber>/<Day>/<FileName>. Hence, after executing

everything, I got input and output link below:

Inputs link

https://prod-54.eastus.logic.azure.com:443/workflows/
93c8e3ff026b4aff9ca3d0bbd4f047c6/triggers/When_a_new_email_arrives_(V3)/
histories/08585204391640535932989292382CU84/contents/TriggerInputs?api-
version=2016-10-01&se=2023-04-11T03%3A00%3A00.0000000Z&sp=%2Ftriggers
 %2FWhen_a_new_email_arrives_%28V3%29%2Fhistories
%2F08585204391640535932989292382CU84%2Fcontents%2FTriggerInputs
%2Fread&sv=1.0&sig=T_F0cIopPEymUBtz99lk-YumxPO95uAfiP7JRFHH-sM

Outputs link

https://prod-54.eastus.logic.azure.com:443/workflows/
93c8e3ff026b4aff9ca3d0bbd4f047c6/triggers/When_a_new_email_arrives_(V3)/
histories/08585204391640535932989292382CU84/contents/TriggerOutputs?api-
version=2016-10-01&se=2023-04-11T03%3A00%3A00.0000000Z&sp=%2Ftriggers
%2FWhen_a_new_email_arrives_%28V3%29%2Fhistories
%2F08585204391640535932989292382CU84%2Fcontents%2FTriggerOutputs
%2Fread&sv=1.0&sig=UHF2y5LXhIo6Rd6grkAl8a0rVBMSwJkOU4-vlQP_dIY

References
Golightly, L., Chang, V., Xu, Q. A., Gao, X., & Liu, B. S. (2022). Adoption of cloud computing
as innovation in the organization. International Journal of Engineering Business Management,
14, 184797902210939. sagepub. https://doi.org/10.1177/18479790221093992

NELSON, M. R. (2009). The Cloud, the Crowd, and Public Policy. Issues in Science and
Technology, 25(4), 71–76. https://www.jstor.org/stable/43314918