- Technology, Media & Telecom
- Pricing Analysis
- Data Science and Quantitative Modeling
- Europe and Central Asia
- Burkina Faso
- Congo, Dem. Rep.
- Ivory Coast
- South Africa
- Middle East
- Saudi Arabia
- West Bank and Gaza
- North and Latin America
- Asia- Pacific
- Hong Kong
- New Zealand
- South Korea
- Sri Lanka
The worldwide total revenue of Cloud system grew to 76 USD billion in 2015, an increase of 24% from 61 USD billion in 2014. The 2015 results showed a worldwide increase in the adoption of cloud system very similar to that in 2014.
According to Quantum-Web forecasts, Cloud system revenue poised to growth at 13 CAGR approaching 270 USD billion revenue by 2025.
In terms of cloud application and services, Software as a Service (SaaS), represent the largest cloud market and will growing quickly. SaaS revenue expects to reach 178 USD billion by 2025 followed by 65 USD billion generating by Cloud infrastructure services, known as Infrastructure as a Service (IaaS) and 26 USD billion of Cloud platform services, or Platform as a Service (PaaS).
The global trend of Cloud revenue is progressing stably without any noticeable sign of either slowing down or accelerating, commented Qmars Safikhani, Principal Analyst at Quantum-Web.
SAAS: SOFTWARE AS A SERVICE
Cloud application services, or Software as a Service (SaaS), represent the largest cloud market and are still growing quickly. SaaS uses the web to deliver applications that are managed by a third-party vendor and whose interface is accessed on the clients’ side. Most SaaS applications can be run directly from a web browser without any downloads or installations required, although some require plugins.
Because of the web delivery model, SaaS eliminates the need to install and run applications on individual computers. With SaaS, it’s easy for enterprises to streamline their maintenance and support, because everything can be managed by vendors: applications, runtime, data, middleware, OSes, virtualization, servers, storage and networking.
Popular SaaS offering types include email and collaboration, customer relationship management, and healthcare-related applications. Some large enterprises that are not traditionally thought of as software vendors have started building SaaS as an additional source of revenue to gain a competitive advantage.
SaaS Examples: Google Apps, Salesforce, Workday, Concur, Citrix GoToMeeting, Cisco WebEx
PAAS: PLATFORM AS A SERVICE
Cloud platform services, or Platform as a Service (PaaS), are used for applications, and other development, while providing cloud components to software. What developers gain with PaaS is a framework they can build upon to develop or customize applications. PaaS makes the development, testing, and deployment of applications quick, simple, and cost-effective. With this technology, enterprise operations, or a third-party provider, can manage OSes, virtualization, servers, storage, networking, and the PaaS software itself. Developers, however, manage the applications.
Enterprise PaaS provides line-of-business software developers a self-service portal for managing computing infrastructure from centralized IT operations and the platforms that are installed on top of the hardware. The enterprise PaaS can be delivered through a hybrid model that uses both public IaaS and on premise infrastructure or as a pure private PaaS that only uses the latter.
Like the way in which you might create macros in Excel, PaaS allows you to create applications using software components that are built into the PaaS (middleware). Applications using PaaS inherit cloud characteristic such as scalability, high-availability, multi-tenancy, SaaS enablement, and more. Enterprises benefit from PaaS because it reduces the amount of coding necessary, automates business policy, and helps migrate apps to hybrid model.
Enterprise PaaS Examples: Windows Azure Cloud Services, Amazon AWS, Google App Engine.
IAAS: INFRASTRUCTURE AS A SERVICE
Cloud infrastructure services, known as Infrastructure as a Service (IaaS), are self-service models for accessing, monitoring, and managing remote datacentre infrastructures, such as compute (virtualized or bare metal), storage, networking, and networking services (e.g. firewalls). Instead of having to purchase hardware outright, users can purchase IaaS based on consumption, like electricity or another utility billing.
Compared to SaaS and PaaS, IaaS users are responsible for managing applications, data, runtime, middleware, and OSes. Providers still manage virtualization, servers, hard drives, storage, and networking. Many IaaS providers now offer databases, messaging queues, and other services above the virtualization layer as well. Some tech analysts draw a distinction here and use the IaaS+ moniker for these other options. What users gain with IaaS is infrastructure on top of which they can install any required platform. Users are responsible for updating these if new versions are released.
IaaS Examples: Amazon Web Services (AWS), Cisco Metapod, Microsoft Azure, Google Compute Engine (GCE), Joyent
Common IaaS Use-Case: Extends current data centre infrastructure for temporary workloads (e.g. increased Christmas holiday site traffic)
Private Cloud, Public Cloud and Hybrid Cloud
It’s important to know the difference between the three.
A private cloud hosting solution, also known as an internal or enterprise cloud, resides on company’s intranet or hosted data centre where all your data is protected behind a firewall. This can be a great option for companies who already have expensive data centres because they can use their current infrastructure. However, the main drawback people see with a private cloud is that all management, maintenance and updating of data centres is the responsibility of the company. Over time, it’s expected that your servers will need to be replaced, which can get very expensive. On the other hand, private clouds offer an increased level of security and they share very few, if any, resources with other organizations.
The main differentiator between public and private clouds is that you aren’t responsible for any of the management of a public cloud hosting solution. Your data is stored in the provider’s data centre and the provider is responsible for the management and maintenance of the data centre. This type of cloud environment is appealing to many companies because it reduces lead times in testing and deploying new products. However, the drawback is that many companies feel security could be lacking with a public cloud. Even though you don’t control the security of a public cloud, all your data remains separate from others and security breaches of public clouds are rare.
Hybrid architectures are especially attractive for large organisations that want to explore the flexibility and scalability of the public cloud. An audit will not always reveal how an application will perform in the public cloud, so enterprises choose to test a single tier in the public cloud while maintaining key infrastructure on their private cloud or dedicated infrastructure.
A hybrid system is also a good solution if there is institutional hesitancy about the security of the public cloud for sensitive data
An important thing to understand about hybrid environments is that they are only as strong as the integrations that unite them. Performance monitoring, regular testing, and data ingress and egress procedures will reveal future areas of difficulty as well as signal when and how to further evolve the application. The team orchestrating the infrastructure is almost always more important than the specific type of cloud solution you chose.
A large company may choose a private cloud, while a smaller business might choose a public cloud.
Quantum-Web can help organisations reach their strategic goals faster than competitors. We can assist you to identify the opportunities in your sector by gathering, analysing and forecasting market data. We are committed to build collaborative partnerships to assist in developing your vision and achieve your goals.
For more information about our services please contact us at email@example.com or fill in this form.