If these circumstances do not arise, however, PaaS is the default. Very specific technical needs of application e.g, heavily customized features, and specific network needs.While you may be seeing PaaS as an obvious choice, some circumstances warrant your tending toward an On-Premise approach for your application. The solutions it provides are also carefully crafted based on many years of experience.

With purpose-built solutions for deploying custom, scalable web applications such as Drupal, Acquia is one of the best cloud solutions out there. Platform-as-a-Service also provides a great deal of customization without the need for a large, knowledgeable team to build infrastructure.Īcquia is an example of the Platform-as-a-Service model. Your team of developers and site administrators can focus on more significant tasks on the web application. These technicalities are managed by PaaS providers. PaaS model removes a great deal of the complexity involved in web application hosting, such as hardware maintenance and so on. Its advantage is the extent of customization and flexibility it offers. The model requires significant resources to operate and involves the input of a large team of developers, administrators, and technicians to utilize and manage. If you’re thinking, “Man, how tasking must that be!”, you’re very justified. On-Premises refers to self-hosted and managed hardware – you manage the entire stack from hardware and networking to the web application itself. This article will examine two hosting models available to Drupal, namely Platform-as-a-Service (which Acquia is an example of) and On-Premise, to help you decide which route would be best for you. Without careful guidance, picking the route to go can be the beginning of a chain of arduous time-wasting maintenance efforts. Hosting a website or web application can be a costly, and challenging endeavor.

Acquia drupal hosting