Skip to main content

delivery models and services

Cloud computing services for application and infrastructure needs are widely being adopted by big and small organisations.
In contrast to the traditional IT setup where a huge capital investment was required for the purchase of software and hardware, cloud computing services enables organisations to align costs to actual usage.
They make businesses highly agile, operationally efficient and remarkably flexible.
Cloud computing services range from satisfying a single functional need of an organisation to delivering the entire data center through networks. With cloud computing, innovation is accelerated and the opportunity to focus entirely on the core business operations are enhanced. 

Delivery models that can be broadly classified into three services-

•Software as a Service (SaaS)

Software as a Service (SaaS) allows an organisation to access the desired software applications through the cloud on a subscription basis. The SaaS vendor offers access to the software applications with no upfront investment and takes care of all upgrades.
SaaS is popularly referred in the industry as “on-demand” software. Users access SaaS-based applications using their smartphones, tablets, laptops or desktops through a web browser. SaaS model neither requires any physical distribution of software or its upgrades nor does it require painful download of applications from the website. The user on subscribing to the application automatically gets a login id and password information to his email. Using this login id and password, the application and its features can be accessed through the browser.
The SaaS model is widely used these days as a service delivery model for applications such as ERP (Enterprise Resource Planning), CRM (Customer Relationship Management), Accounting and HRM (Human Resources Management).With the growth of technology, the cost of conducting a business has also increased. Gartner, Inc. is an American marketing, market research and advisory firm has revealed that organisations spend almost 75% of IT costs on procuring and managing their software applications and infrastructure.
  

•Platform as a Service (PaaS)

While the SaaS model of Cloud Computing offers access to software hosted on remote servers, PaaS provides the platform that is required to build and deploy a software application. Platform as a Service can be defined as the cloud delivery model that offers the tools needed to rapidly develop and manage software applications.
PaaS is the best fit for organisations that are committed to the delivery of web and mobile applications within a stipulated time and budget. A PaaS provider offers the toolkit to build an application and the virtual machine to run it. Application developers can design the functionalities as well as the interface based on their particular needs.
 The PaaS delivery model allows organisations to leverage the investment made by a vendor to build complex business applications efficiently.

•Infrastructure as a Service (IaaS)

  Infrastructure as a Service forms the base of the Cloud Computing stacks. The service offers the ability to provision server, storage, networking and other basic computing infrastructure resources through the internet and as required. Since the IaaS cloud delivery model eliminates the need to invest in hardware, it is a perfect solution for startups and for organisations that deal with extreme spikes and troughs in usage.
With scalability as an unbeatable advantage, the key lies in choosing an IaaS vendor that promises the highest availability of resources and complete adherence to all regulatory measures while handling sensitive data.
In recent times, there seems to be a diminishing line of distinction between the IaaS and PaaS services as more and more cloud service providers move towards rendering deployment tools as a part of their IaaS offering. Examples include Amazon (AWS), Microsoft Azure and IBM. Amazon bundles its PaaS (ES2) and IaaS (S3) services and IBM bundles BlueMix(PaaS) and SoftLayer (IaaS) services on a packaged model.


Comments

Post a Comment

thank you for visiting :)

Popular posts from this blog

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

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

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_native_string   File "/usr/lib/python2.
Post a Comment
Read more

tag