Skip to main content

Cloud Computing architecture

Cloud computing architecture refers to all components and sub-components that together form the structure of the cloud computing system.
This architecture can be divided into three parts for better understanding – front end, back end and middleware.
Each part of the cloud architecture has its own set of functionalities and protocols that work together to deliver on-demand services to user-facing hardware as well as software. In general, the architecture is evolved out of large distributed network applications over the last two decades. Hence it supports any system where resources can be pooled and partitioned as required.
The general cloud architecture is capable of running multiple software applications running on multiple virtual hardware in multiple locations to efficiently render on-demand services to the users. The users could be using these software applications from their desktop or laptop or mobile or tablets. Usually, whatever the user is looking at – through the browser (or) mobile app – is the front end. This is also called as Service Value net – as a single front end can be available across devices having multiple screen resolutions (like desktop having large screen size, mobile having small screen size and tablets having medium screen size). This front end is connected with the middleware (or) the logical layer which runs all the business services and IT service code.
This middleware is responsible for all the encryptions and information processing using the backend.
The backend in short, is usually the infrastructure layer containing physical (or) virtual servers. More details about these three layers is provided in further sections.

This architecture can be commissioned within an organisation by assembling required hardware and software components (or) can be provided by a third party.  The communication between layers in the architecture happens through standard internet protocols.
Front End
The front end of the cloud architecture refers to the client side of the system.
 It includes the network, applications or programs that are used to access the cloud.
For instance, while accessing a web-based email application, the web browser acts as the front end.
Middleware
For the smooth communication between the front and the back end of the cloud computing architecture, certain protocols must be followed.
The part of the system that connects the networked computers and facilitates the proper functioning between the front and the back end is called the middleware.
It is the special software used by the central server to administer the system.
Back End
The back end of the cloud architecture refers to the hardware section which includes the servers, deployment models, security mechanisms, storage and the computing systems.
Based on the requirements, a specific hardware configuration is setup initially to get the organisation into the cloud. As the requirements increase, additional servers and storage modules are deployed from time to time. 

Comments

Post a Comment

thank you for visiting :)

Popular posts from this blog

The Seven-Step Model of Migration

Irrespective of the migration approach adopted, the Seven-step Model of Cloud Migration creates a more rational point of view towards the migration process and offers the ability to imbibe several best practices throughout the journey Step 1: Assess Cloud migration assessments are conducted to understand the complexities in the migration process at the code, design and architectural levels. The investment and the recurring costs are also evaluated along with gauging the tools, test cases, functionalities and other features related to the configuration. Step 2: Isolate The applications to be migrated to the cloud from the internal data center are freed of dependencies pertaining to the environment and the existing system. This step cuts a clearer picture about the complexity of the migration process. Step 3: Map Most organisations hold a detailed mapping of their environment with all the systems and applications. This information can be used to distinguish between the ...
Post a Comment
Read more

Special Permissions in linux

The setuid permission on an executable file means that the command will run as the user owning the file, not as the user that ran the command. One example is the passwd command: [student@desktopX ~]$ ls -l /usr/bin/passwd -rw s r-xr-x. 1 root root 35504 Jul 16 2010 /usr/bin/passwd In a long listing, you can spot the setuid permissions by a lowercase s where you would normally expect the x (owner execute permissions) to be. If the owner does not have execute permissions, this will be replaced by an uppercase S . The special permission setgid on a directory means that files created in the directory will inherit their group ownership from the directory, rather than inheriting it from the creating user. This is commonly used on group collaborative directories to automatically change a file from the default private group to the shared group, or if files in a directory should be...
Post a Comment
Read more

RequestsDependencyWarning: urllib3 (1.24.1) or chardet (3.0.4) doesn't match a supported version

import tweepy /usr/lib/python2.7/dist-packages/requests/__init__.py:80: RequestsDependencyWarning: urllib3 (1.24.1) or chardet (3.0.4) doesn't match a supported version!   RequestsDependencyWarning) Traceback (most recent call last):   File "<stdin>", line 1, in <module>   File "/usr/local/lib/python2.7/dist-packages/tweepy/__init__.py", line 14, in <module>     from tweepy.api import API   File "/usr/local/lib/python2.7/dist-packages/tweepy/api.py", line 12, in <module>     from tweepy.binder import bind_api   File "/usr/local/lib/python2.7/dist-packages/tweepy/binder.py", line 11, in <module>     import requests   File "/usr/lib/python2.7/dist-packages/requests/__init__.py", line 97, in <module>     from . import utils   File "/usr/lib/python2.7/dist-packages/requests/utils.py", line 26, in <module>     from ._internal_utils import to...
Post a Comment
Read more

tag