No

Running Head: Cloud computing
Cloud computing
Topic: Cloud computing
Student Name:
University Name:
Unit Name:
Date:
Contents
Introduction    4
Cloud Architectures    4
Service Oriented Architecture    8
Cloud Bursting Architecture    10
Bursting out to the Public cloud    11
Burst out architecture    11
Burst in Architecture    12
Degree of the Independence    13
Technology Stack    14
Operational Complexity    14
The benefits against implementing the architecture are:    15
Service Oriented Architecture    15
Cloud Bursting Architecture    16
Bursting out to the Public cloud    16
Burst out architecture    16
Burst in Architecture    17
Risks regarding MicroService approach planning    17
The general securities and controls of IS for securing MicroService approaches    21
Integrating the present enterprise systems    22
Addressing the necessities of connectivity    22
Developing governance policies and service agreements    22
Resolving and Assessing the security and privacy related challenges:    22
Proposed Information Security controls    23
Recommends included in the “VideoDev Engineering’s” BCP :    24
Analysis of requirements:    27
Remote Server Administration Tools    27
Requirements of resource management    27
SLA Management    27
Description of the steps included in plan asked    28
The critical issues checked include:    30
Conclusion    30
References    32
Introduction
"Cloud computing" has become the practice of hosting remote server networks. This is done over an Internet. It may help to store, manage, and process information. This is different from what is done on a personal computer or on a local server. VideoDev Ltd is a video or production development business serving customers in New Zealand and Australia (Botta, de Donato, Persico & Pescapé, 2016). The business is considering to migrating a few of its computer infrastructures to the cloud. Information technology has been spreading throughout all areas of the business to promote business functions and enhance operational activities by providing better and enhanced services. Cloud computing is a revolutionary technology that enables businesses and organizations to manage all operational activities more accurately and advanced. The exchange and preservation of data in the cloud enables organizations to efficiently perform operational activities. VideoDev Garden has always been a garden company that has been providing gardens and plants related services to the local community. The function of this report is to propose the theoretical aspects of implementing cloud computing in VideoDev's existing systems and to co
elate them with features and operations that can benefit the organization. The purpose of this report is to present a hy
id structure for VideoDev Gardens, to reflect on implementation-related risks, and to propose information safety controls SLA management, BCP changes, as well as SharePoint migration plans (Buyya, 2013). MicroServices has been recommended as the best way for organizations to drive operational activities to get better the overall performances and output of the organization. The following report is prepared on VideoDev, discussing its various aspects of cloud computing.
Cloud Architectures
 Microservices are known as microservice architectures. It’s an architectural style, a software growth method in which the large applications are built as the set of a modular service. Small, stand-alone versioned as well as scalable, consumer-centric services with particular business objectives that communicate with each other through standard protocols with a well-define interfaces (Chen, Zhang, Hu, Taleb & Sheng, 2015). Because they can be deployed and scaled independently, each service provides solid module boundaries, even allowing different service to be written in a different programming language, or managed by other or different teams. Because of the scalability, when you have to enable support for multiple platforms and devices, such as the Web, wearables, mobile, IoT, and when you not are sure which type of device, the architectural approach is it considered to be a particularly ideal method (Choi, Choi & Kim, 2013). The major idea behind the micro services architecture is that it's easier to build and maintain certain types of applications into smaller, combinable parts that work together. In the other words, every part is developed very separately, and then application is just the total of its basic parts. This do not provides a development team with more decentralized approaches to software building, but it allows for independent deployment, rebuild, redeployment, and management of each service. Services may run in the similar process, nevertheless they must be self-contained and simple to replace, and can be also implemented utilizing different programming language, software, and databases (Fehling, Leymann & Retter, 2014). These services are detailed and small and can perform function that includes deployment and testing automation, continuous delivery of software development processes, failures and failures (similar to the anti-fragile system), each service being resilient, resilient, combinable, minimal or complete. The container is designed to reduce everything that needs to be done to run the container to the smallest possible part, rather than packaging multiple functions into the same machine (Froberg, 2013). VideoDev has decided to transfer its services to the MicroServices policy. Cloud computing includes a variety of important architectural models. The main architectural model of cloud computing is Infrastructure as a Service or IaaS, Platform as a Service PaaS and Software as a Service or SaaS. The main explanation for choosing one of the ideas identified with the proposed MicroServicesis is because it joins both the general population cloud and the private cloud (Gai, Qiu, Zhao, Tao & Zong, 2016). MicroServicesco's implementation can be combined into various structures, for example, it can be implemented as a private cloud that can be implemented inside the association, and then can be implemented again as an open cloud-pair component that directly contains external people or third parties (or vendors). Visit (Frankenberger et al., 2013). A portion of a private cloud can be considered extraordinary compared to other related options. This is because there are some unique ideas that can be realized from this idea (Henze et al., 2016). The rationale for consideration in the concept of a private cloud is that the security of information is implemented in this concept, which directly protects information and data related to the operational activities of the enterprise.
‘The cloud architectures are demonstrated below:
    Cloud Architecture
    Descriptions
    Reasons for deploying it
    “Workload Distribution Architecture”
 
    It has also been reducing the excessive use of the IT resources. In addition to this, the use is also considered (Hu, Hao & Bao, 2014). It has to some extent relied on the power of the runtime logic moreover "load balancing" algorithm
    The Cloud Usage Monitor is integrated here. These are done for run time work load tracking. It’s also helpful in information processing.
 
     
 
“Resource Pooling Architecture”
     
It is based on the use of the resource pools. Here, same resources of theIT are grouped. At the same time, the system has also completed control (Jula, Sundararajan & Othman, 2014). It has also been making sure that they are synchronized in an automated manner. 
     
At runtime, there are many "cloud usage monitors" here. This helps to track and synchronize the elements needed for IT resources in the pool. Other basic management system is also considered here.
 
    “Dynamic Scalability Architecture”
    The model is based on the logic of a predefined scaling system. These are dynamically triggering the portion of the IT resources. It’s done from resource pool.
 
    Specific monitors for usage of cloud have also been capable to track runtime utilization. This is due to the dynamic fluctuations caused by the architecture.
 
    “Elastic Resource Capacity Architecture”
    It is related to configuring virtual server dynamically. It has always been using systems that allocate and recycle RAM with CPU (Kalloniatis et al., 2014).
    Data usage resources for IT have been collected prior to cloud usage monitoring and then collected during and after the expansion.
 
Service Oriented Architecture
It is a software design style that allows organizations to take advantage of the services provided to components by accessing the application components available on the network that are transported over the communication protocol (Katyal & Mishra, 2014). The principle of this architecture can be defined because it is completely independent of the technology, product and vendor services.
The following description can be helpful in describing the SOA architecture:
Based on the latest overview of Trend Micro, an organization that already works in various parts of cloud security, the organization stated that management provided by the general population cloud specifically ignored the need to meet IT associations (Li, Li, Chen, Lee & Lou, 2015). They then infe
ed again that MicroServicescan's ideas were particularly useful for the association's management of operational activities and the exchange of data and information related to it. The main vantage point that can be determined by using any idea of ​​distributed computing is that it directly provides an area that accommodates the work of VideoDev, which can work both inward and outward. In this idea, it can be expressed that part of the information capacity in the cloud idea is particularly useful for association. In most cases, you can see that the security of the information can be seen as the best among the most critical parts (Younas, Awan & Pescape, 2016). There are many uses in the unique idea of ​​the semi-variety cloud, which is especially important for the work of the association. It can be said here that the viewpoint identified according to the application or request is accessible. The installation of management devices within the angular range is based on the benefits utilized (Taylor, Fritsch & Liede
ach, 2014). In this case, it can be indicated that the service pool can be enhanced for the case where the workload is increased, and the management can be restricted by the necessity of association for the case where the demand is small (Botta, de Donato, Persico & Pescapé, 2016).
Cloud Bursting Architecture
The use of on-premises or private cloud service A is being monitored by the auto-expanding listener and has redirected client C's request to the instance in the instance (in use, the user's redundant implementation of service A in the cloud) the threshold of service a reaches the maximum value (Buyya, 2013). In order to synchronize the state management database, a resource replication system can be utilized.
Bursting out to the Public cloud
It can be described as a dedicated architecture that helps allow IT resources to extend private clouds to public cloud environments. The principle of this architecture is based on predefined usage triggers.
Burst out architecture
Following are the processes involved in this architecture:
· Increment in traffic Trigger point can be triggered throughout the automated listener scaling
· Resource replications can be activated
· Initiation of automation engine
· Activation of quick provision program
· The cloud services provisioned and come online
Burst in Architecture
It happens when Cloud IT resources are no longer needed and the auto-expanding listener encounters a low-utilization trigger event (Chen, Zhang, Hu, Taleb & Sheng, 2015). The shutdown of the message initiation is done by the intelligent automation system, which sends the message to the quick configuration program and the cloud resources are closed.
Whenever your team develops new applications from scratch, don't inherit technical debt and fall into the outdated decision made many years ago, which is great (Choi, Choi & Kim, 2013). Today, most teams developing new applications may choose to containerize them with Docker as well as adopt microservices architecture to increase speed moreover agility. Nevertheless, before you begin, you need to consider the following:
Degree of the Independence
The primary decision is - how independent do you need your service to be? You can choose the following options:
· Every service is totally independent of its individual database as well as UI. This is reliable with the extreme micro service architecture, in which the service does not actually share anything and is completely separate (Fehling, Leymann & Retter, 2014). The good news is that every micro services team can choose the databases that best meet their needs. But, this approach makes it more difficult to make sure that all the data stores are consistent and synchronized. Such as, you require to confirming that the similar user ID exists in all the data stores and that there are no missing. In addition, each team needs to replicate database management tasks (such as backups).
· You can select to share certain components, generally a database (Froberg, 2013). This also makes it easy to implement standard across all groups and ensures data consistency across all the services. Nevertheless, this means that your service is not fully decoupled, or other services may be affected if someone updates the table or schema.
Technology Stack
Determining the technical stack of a single-chip application is very difficult, but it is now necessary to make this decision for each microservice. If your service is too heterogeneous, something that looks theoretically attractive may become a problem in practice. Standardization...