Platform as a Service (PaaS) by diva-e
From planning to support
diva-e not only offers technical expertise, but also cutting-edge IT facilities. Our in-house datacentre in Frankfurt am Main is the perfect home for your data. We offer e-commerce and content platforms using corporate or bespoke software and 24/7 support throughout the entire lifecycle.
Our service: IT applications for digitisation
Your business' digital transformation is complex and mission critical. It places high demands on your internal resources. Diva-e allows you to focus on important key areas. We develop digitally-driven business transformation strategies for marketing, sales and service and help you adapt your legacy IT landscape to the new digital applications.
Diva-e takes over the operation of your new IT applications for digitisation. On-premise, in our own, cutting-edge diva-e datacentre in Frankfurt am Main. Vertically integrated: Application Management and IT Operations Management from a single source.
Some of the services we offer:
Operation of CMS platforms
Operation of Intershop platforms
Operation of SAP Commerce Cloud
Our tools: in-house datacentre
diva-e offers highly available, standardised (ITIL based) operations with SLAs covering the entire lifecycle of its e-commerce and content platforms. This includes rollout and migration as well as DevOps deployments.
With years of experience, our operations team use our own datacentre. Connected directly to international carriers and the world's largest internet nodes, we offer colocation, managed hosting services and DDoS protection with the highest standards of availability, scalability and security.
PaaS as a link between IaaS and SaaS.
The three layers of cloud computing are IaaS, PaaS and SaaS. They assume different roles. Platform as a Service is built on a scalable infrastructure (IaaS). Software as a Service (SaaS), in turn, can be developed on a scalable infrastructure (IaaS). While PaaS takes care of building a development environment and provides runtime solutions, Infrastructure as a Service provides resources for the network, computing power computers, storage, hosting and other infrastructure. With IaasS, the user still has control over the operating system. PaaS thus represents the middle layer in the cloud stack, so to speak, and is an important element of Everything-as-a-Service (XaaS). Providers of cloud solutions are often also operators of large data centers.
If you think about this scenario further, that not only an e-commerce application is offered as a PaaS solution, but also a supporting CMS and possibly other systems, it quickly becomes clear that an overarching error analysis, in which each of the providers only knows its own landscape, becomes practically impossible.
Advantages of PaaS
Developers, development teams and programmers in particular benefit from Platform as a Service, because they can create new applications and apps without much effort. The cloud-based service provides the corresponding infrastructure. The customer does not have to procure software for the development of necessary solutions and applications. So, as a user, you bypass the costs and work involved in buying and managing licenses. Developers can therefore concentrate on their development work. so that development ideally progresses faster. In addition, the cloud service is scalable, so you can add or reduce capacity as needed. In addition, PaaS offers numerous functions for application lifecycle management (ALM).
However, the fact that users don't have to worry about the software or the infrastructure can also be a disadvantage. This is because you do not have unrestricted access and features can also be used that are provided by the provider. Use diva-e's expertise to get detailed advice on the advantages and disadvantages of providers such as AWS, Microsoft Azure, Google Cloud and Co.
The PaaS SLA dilemma
In the event of an incident, of course, PaaS offerings are limited. A software provider that has thousands of customers cannot know every customer system so well that it immediately knows where to start troubleshooting in the event of a failure or malfunction. A so-called SLA dilemma becomes apparent when the operation of a business-critical application is scrutinized in detail along all layers.
First of all, there is the cloud infrastructure on which the store or CMS system runs. If it is a public cloud, the hyperscaler only provides reliable SLAs for around 15% of the services. This means that without special knowledge and the necessary experience in the operation of such cloud infrastructures, SLA gaps already arise here, which must lead purely mathematically to a deterioration in availability as well as poorer response and recovery times.
The next layer is the standard product of the software provider, which is usually provided in a default installation. SLAs are given in that, at best, a response time is given for the infrastructure included in the PaaS offering and managed by the software provider, as well as for the basic availability of the application. Here, providers refer only to the functionalities of the standard product. Some vendors are still learning how PaaS offerings actually need to be operated and managed, and often the available expertise at product vendors is very thin. Beware: product vendors have only had to worry about product development for years, so they don't always have the best expertise for efficient and service-oriented operation.
The PaaS offerings of standard products often have another disadvantage. They are software systems that contain large, monolithic pieces, and many components and modules have not been optimized for cloud operation or have yet to be appropriately re-implemented as micro-services. As a result, some of the promise of cloud infrastructure cannot be exploited at all.
When it comes to the individual project, the custom code, in the next layer, the SLA gap arises. This is where the software provider takes the customer or their system integrator to task. The same applies to connected third-party systems such as ERP, CMS, PIM and the like. It can happen that performance issues occur where the PaaS provider only sees in its monitoring that resources are being used to capacity - but it does not see the reason for this. The reason may lie in the custom code or in interfaces to third-party systems. None of this is in the scope of the PaaS provider. The same applies to incidents, which usually first have to be analyzed to determine the exact cause.
diva-e takes on all tasks as a reliable partner
To avoid this SLA dilemma, you therefore need an institution that has precisely this overview of the entire system landscape and its interaction. With our diva-e team of experts, we are therefore at your disposal and take on all tasks at hand. We have the know-how and also the authorization to approach the providers involved if necessary and to accompany, drive and lead the resolution of an incident to its conclusion.#
PaaS or better AMS?
Application management can close this gap in communication. diva-e has extensive expertise in application management and managed cloud services. We thus offer customers comprehensive support for their cloud-based projects. The primary goal of the AMS (Application Management System) is to minimize problems and guarantee fail-safety. For this purpose, the application managers deal intensively with your web applications and technologies and are responsible for the entire life cycle of your services.
Our services include comprehensive consulting, in which we analyze which type of data center is advantageous for you as a customer. Our goal is to ensure that we handle your computing satisfactorily and get the most out of your data. We focus on fail-safety and effortless migration. Regardless of whether you need a hybrid solution or other set-up for this.
Important questions to ask your cloud provider
If you have a quote from a software vendor to run the application, ask yourself the following questions:
Who has the expertise on the application and supporting systems in question?
Who controls the incident management?
What SLA does the PaaS provider give?
Which (public) cloud is the PaaS offering based on?
What is the backup strategy?
Who monitors the backups, who performs recovery tests and recovery in case of emergency?
Who carries out the deployments?
What options are there for connecting or implementing your own monitoring?
Is service level reporting provided?
How does the PaaS provider charge for its services; is everything done on a flat-rate basis or is there also a time & material (T&M) component?
If these questions are not answered or not answered sufficiently, then talk to us. We will be happy to evaluate these offers and compare them with the industry standard.