Why Build Your Own Cloud Native Drupal Platform?

Why or rather "when" should you consider building your own cloud native Drupal platform?

Is a container-based infrastructure a viable solution for you? For your business needs?

How do you know if your specific use case calls for a cloud-native Drupal development environment?

And, assuming that you've run your own evaluation and that your use case does demand a switch from your current VM to a... multi-cloud Drupal hosting architecture:

How do you make Drupal... cloud native friendly?

So that you can build, deploy, scale and manage fast and resilient Drupal apps in the cloud?

In this post, we commit to answering all your key cloud-native and Drupal-related questions:

"What does cloud-native mean exactly?"
"What is cloud-native with respect to Drupal?"
"Why do I need a cloud native Drupal platform anyway?"
"What are the biggest advantages and their... flip sides?"

1. What Does Cloud Native Mean Exactly?

What is a cloud-native application?

It's a holistic approach to designing, building, and running applications that make the most of cloud-native concepts.

Or, if you wish:

Cloud-native application development is a methodology — covering all stages of an app's lifecycle: design, deployment... operations — for developing apps that run in the cloud.

Applications that use the cloud computing model to its full potential.

DevOps, agile, microservices and other modern software architectures all fall under the umbrella of a cloud-native methodology.

Therefore, it's fast, resilient, highly scalable and easily maintainable applications that you get to run in a cloud-native infrastructure.

2. And What Is Cloud Native with Respect to Drupal?

In other words: where does Drupal fit in this revolution in how we develop and deploy our applications?

Overall, taking full advantage of a cloud native Drupal development environment means:

Finding the best solution for handling decentralized storage, auto-scaling, auto-provisioning and multi-region fault tolerance.

Getting the most of cloud-native and Drupal comes down to:

minimizing the use of long-running servers
relying more on purpose-built services and elastic computing
setting up a development environment where you can easily test your new themes and modules, fix bugs, build, and deploy resilient enterprise Drupal apps

3. Why Build Your Own Cloud Native Drupal Platform? And When?

For there are cases (is this your case, too?) when such a powerful, yet... challenging architecture is not justified by the company's business needs.

So, let's answer your "when" question first.

You're better off with a cloud-native infrastructure, where you deploy Kubernetes and containers, if:

you're dealing with high traffic, high volume applications and polyglot architecture
you already have an Ops team
you've already made at least some sort of investments in the private or public cloud
your current requirements in terms of costs and control justify setting up a multi-cloud architecture
you're running and maintaining an entire ecosystem of Drupal sites

"OK, so it looks like I "qualify" for it. But still: what would be the biggest advantages of building my own cloud-native platform compared to opting for a cloud vendor's services?"

Here are the 2 most obvious advantages:

you'd avoid getting locked-in to a cloud provider
you'd avoid growing dependant of your PaaS provider for hosting, scaling, and managing your own Drupal apps

4. Why Would You Want to Containerize Your Drupal Apps in the First Place?

What would be your major wins if you ran Drupal in containers?

Here are the 3 most significant ones:

repeatability and consistency: you get the same predictable and specific result with each container that you run
less maintenance work
an easier way to run PHP upgrades compared to a conventional VM stack where you depend on your host for that and where there's a whole cluster of sites that needs to get PHP upgraded simultaneously

5. 3 Pillers of a Container-Based Infrastructure: Drupal, Kubernetes, Docker

What goes into a cloud-native Drupal platform? There are 3 key players involved:

5.1. Drupal

The robust content management system which, beginning with its 8th major version, grew into a Symfony-based content management framework.

Backed by a huge (100K+) and active community of contributors and a rich plugin ecosystem, Drupal powers a wide variety of web applications: media and entertainment apps, non-profit, gov, education...

5.2. Kubernetes

It's the standard container orchestration technology.

In the context of your future cloud-native infrastructure, you'll be using it to manage:

your containers' lifecycle
command and control
distribution
scheduling

5.3. Docker

It's the standard... tool that you will be using for creating your containers.

6. 4 Cloud-Native Platform Features to Put on Your Wishlist

What feature requirements should you have with respect to your Drupal development environment?

Here's how a... decent wishlist should look like:

it should provide a layer of abstraction over IaaS
it should handle cross-cutting concerns
it should be easily scalable and secure
it should provide an efficient developer experience (and agile operator experience, as well)

7. Deploying Your Drupal Apps on the Cloud: Requests & Constraints

What's the proper set-up for a container-based Drupal architecture?

"What are the key requirements that my future cloud-native Drupal platform should meet?" you might legitimately ask yourself.

your Drupal application should be turned into a containerized stack
minimal Ops (or not Ops at all)
it should run properly on any cloud
your public/private file should be externalized
it should scale up, out, and down
it should make the most of PaaS services: for gateways, databases, load balances, cache stores, queues
it should tap into an operational model: new app provisioning-routing-monitoring...
your development team should be able to get high fidelity local environments up and running in no time

"And what challenges should I expect?" you'll further wonder:

your developers are faced with a steep learning curve: they should have some sort of understanding of what's happening under the hood when deploying Kubernetes
CI & Delivery Pipeline
logical architecture
monitoring and management
Dev & Build Tools
local development

The END!

What do you think:

Is a cloud native Drupal development environment a viable solution for you?

Are the advantages highlighted here relevant enough for your use case and business needs? Or are the outlined challenges too discouraging for you?

Feel free to share with us any thoughts and concerns that you might have regarding the idea of building your own cloud native Drupal platform.

Photo by C Dustin on Unsplash

We do Web development

Go to our Web development page!

Visit page!

Recommended Stories

Drupal Drupal 8 Tips

5 Steps to Migrate Your Drupal Website to Another Host

At some point in their business journey, every website owner can encounter the need to migrate their web host. As more lucrative hosting options are making their way in the industry–VPS, shared, or dedicated hosting—it's no surprise that many website managers choose to perform host migration. This article provides support in handling one of the most popular DevOps services, hosting server migration, by outlining five essential steps that help you complete a successful migration. When is the time to move your Drupal website to a new hosting server? The decision to switch web hosts is not an easy one to take. The good news is that there are multiple signs that can make it clear that your website requires hosting updates if you know where to look. It won't be comfortable to acknowledge them, but as soon as you start on this journey, you are transforming your website for the better. Let's have a look at how you can spot these signs on your Drupal website. Downtime has become a recurrent issue. Your customers demand availability and speed, so every time your website is down and unavailable for users, you risk building a bad reputation of unreliable and low-quality services. Your server can impact your site's availability if your hosting equipment’s quality is low or your host's security features and plugins provide poor protection capabilities, as cyber-attacks can often lead to downtime. Your host is hard to reach. As a website owner, you want to ensure that the communication with your web host is fast and streamlined. There may be times when your server crashes or you a server error, and you need to get in touch with your host as soon as possible to provide troubleshooting guidance and get your site up and running. An unreliable host may not only affect the functionality of your website but can also cost you customers. Getting the support you need when it comes to your hosting account is paramount to provide high-quality user experiences. That's why making sure that you have a solid customer service team at your side at any time is good for the business. Your current host costs you too much. Web hosting can sometimes be the most significant investment when running a website. It's a recurring expense, so you want to ensure that you choose the best option. However, expensive web hosts aren't always necessary. You have to figure out if the features and the amount of server space that your host provides are a good fit for your site. You don't need to break the bank for hosting servers that don't serve your current needs. You can always review your needs and upgrade to a more expensive plan. You don't get the security you need. As far as investments are concerned, paying extra for a secure web host is worth it. A host that takes security seriously will bring significant benefits to your website. By investing in a secure hosting server, you'll avoid losing data and parts of your website, having user data compromised, and losing credibility in front of your audience. When choosing your web host, watch out for features and plugins like Secure Sockets Layer certificates, malware scanning, or server firewalls. How to switch to a new hosting provider Migrating your Drupal site to a new host is a process that involves contacting your current host, performing database backups, connecting to a new server, and uploading your files. It's not uncommon for issues like corrupted backups to appear during the migration process. Consider this when planning your migration, and think if you can save some resources by hiring a professional agency like Optasy to complete this process for you. There are a few essential steps to follow when migrating to another web hosting server. Let's explore some of them. 1. Turn Drupal caching off. This is the first step to take in order to avoid potential disruptions. Go to your Drupal admin dashboard and: Click Configuration - Performance - Caching - Select "No Caching.” Uncheck "Aggregate CSS files" and "Aggregate JavaScript files" in "bandwidth optimization" and click "Clear all caches.” 2. Backup your Drupal files. Connect to your remote server - Enter the connection details - Hit "QuickConnect" and connect to the remote server that hosts your website. In your main site's folder, download the content on your local device, and you've done backing up your Drupal files. 3. Export your Drupal database. Go to the phpMyAdmin on your server's control panel in the Database section. Click "Check all" on your Drupal site database, then "Export method and the SQL.” 4. Migrate your Drupal database to the new host. Create a new MySQL database on your target server. Click "Import" at the top of your database, then "Choose File,” and press "Go.” You've now restored your site on the new hosting from the backup. 5. Turn on Drupal caching. Go to Configuration - Performance - Enable Drupal caching. Kudos to you! You've officially migrated your Drupal site to another host. Conclusion Building and managing a Drupal website is a complex process, and hosting is one element that can be pretty challenging to handle. There are plenty of hosting options available on the market, and you might find it difficult to decide which one is the best fit for your website needs. If you're considering server migration or just need some professional advice on how to handle your hosting server successfully, our team of Drupal experts at Optasy is glad to help. Photo credit: bsdrouin on Pixabay. ... Read more

Raluca Olariu / Apr 12'2021

Drupal Drupal 8 PHP Tips

Drupal Commerce vs. Magento - Who Wins the Battle for eCommerce?

In 2021, it is expected that about 27.2% of the world population will shop online at least once. A lot of potential customers out there, right? As eCommerce is becoming the new norm, digital businesses seek out ways to thrive in this competitive landscape and position themselves as leading trend-setters. To do that, companies need to realize the power of digital transformation and how they can embrace it in order to support the modern demands of speed and accessibility that customers require today. This starts with leveraging the right tools for building robust digital assets. One of these tools is represented by eCommerce platforms, which are getting increasingly popular for businesses that seek to deploy an eCommerce system. Drupal Commerce and Magento are two of the leading eCommerce solutions on the market and are often seen as direct competitors in the industry. This article provides a side-by-side comparison of these two platforms in regards to technical capabilities, development, costs, scalability, security, and mobile responsiveness. Hopefully, this information will help you narrow down your choice in order to ensure that you choose the best fit for your business needs. Key eCommerce Capabilities Enabled by Drupal and Magento Drupal Commerce was released in 2011 and offers an open-source application framework that supports retailers in building and managing inventory, track orders, or handle payments. Magento's initial release was in 2008. This PHP-based eCommerce site provides high levels of PayPal protocol integration and supports 12 worldwide payment gateways. Both platforms offer, through native features or third-party add-ons, the following benefits: Intuitive, easy-to-use user interface and control panels. No technical knowledge is required to customize and edit basic features. Full-featured CMS that supports social sharing. Business-centric structure for online stores. Native integration of inventory-driven advertising material Integration capabilities with third-party analytics, invoicing, or quoting solutions One thing to keep in mind is that neither of these eCommerce platforms is a "plug and play" solution and making the most out of their potential may require further expertise. Headless eCommerce The headless version of Drupal Commerce has been in the spotlight in the last few years. This new initiative is an eCommerce solution that stores and delivers content without a front-end delivery layer. It's an API-driven implementation that transforms eCommerce functionality, making it available across a wide range of potential host environments. A headless eCommerce model inclines towards a more SaaS-oriented, platform-agnostic solution that allows for better employee adoption and considerable time savings across IT departments. When it comes to Magento, the open-source eCommerce platform, headless eCommerce is equally prioritized. Both Drupal Commerce and Magento are supporting headless models as the future of eCommerce. Pricing Drupal eCommerce's technical cost of entry is free. However, depending on scope and scale, the costs of developing and maintaining performant and secure eCommerce servers might reach tens of thousands of dollars. Drupal Commerce project costs are directly proportional with a business needs for specific development architecture, module integrations, custom theme styling, or particular feature integrations. Magento's newer modules are not offered as open-source and upgrading from Magento Open Source to Magento Commerce might be challenging. From this financial point of view, Drupal Commerce seems to be a clear winner. Scalability Drupal Commerce has relevant capabilities of staying highly performant at scale. However, this CMS platform does not provide out-of-the-box database sharding and it can only be implemented on a third-party basis. Drupal Commerce has lower requirements than Magento Commerce when it comes to the web server—the minimum required RAM for PHP is 64 MB and production systems usually require 128 or 256 MB. Drupal Commerce-based implementation splits the eCommerce experience across three related Drupal domains. As a result, scaling is better, bottlenecks are eliminated, and the content and purchasing experiences are efficiently separated. On the other hand, Magento's cloud hosting solves a large number of scalability issues, although at a higher price. The minimum RAM requirement of 2 GB will probably not scale well and distributed networks or caching may need to be deployed with greater care to keep up with the heavy load. Security Drupal is proven to be the most secure CMS and Magento's infection rate is much higher than Drupal's. From the point of view of security, Drupal Commerce is a winner for businesses that want to prioritize secure platforms. Source: Sucuri.net Mobile Responsiveness As most websites transition to a mobile-first approach, eCommerce platforms that prioritize mobile responsiveness are a must. Fortunately, both Magento Commerce and Drupal Commerce provide robust mobile capabilities to satisfy the need for accessibility and performance. Drupal Commerce's themes allow building a fully responsive design for eCommerce websites and offer screen flexibility for creating versatile experiences. The most popular themes like Corolla or eStore provide: Multi-level responsive header menus Custom layouts and color options Box shadow and background textures Custom field additions Magento Commerce is close to Drupal when it comes to mobile optimization capabilities. Its responsive web design features help users create optimal viewing experiences for multiple devices. Magento Blank or Luma are out-of-the-box themes that deliver a fully responsive design. Who's the winner for eCommerce? While both Drupal Commerce and Magento Commerce are reliable options for a digital company that wants to thrive in the eCommerce market, every business has its own unique needs and requirements. Choosing the software that best supports these needs is a process that involves a lot of research and planning. If you want to speed up this process and ensure that you reach the right decision, don't hesitate to contact Optasy for professional advice and support. Discover which platform is most suited to provide a robust eCommerce experience for you and your customers. Photo credit: Mark Konig on Unsplash. ... Read more

Raluca Olariu / Apr 06'2021

Drupal Drupal 8 Tips

Drupal DevOps Best Practices for 2021

Today, businesses interact with their customers in many forms of digital services on all kinds of devices. As the digital world is more and more present in our lives, delivering streamlined experiences at the tip of your customers' fingers is the key to success. A vital role in delivering rapid, accessible IT services is played by DevOps, a set of practices that brings software development and IT operations together. And when it comes to Drupal web development, DevOps represents a valuable instrument that can maximize the potential of Drupal-delivered projects. How does DevOps work and what benefits does a DevOps model deliver? DevOps, the culture that encompasses most digital businesses today, uses automation and advanced tech stacks to add a new layer of velocity to a company's infrastructure. “DevOps represents a change in IT culture, focusing on rapid IT service delivery through the adoption of agile, lean practices in the context of a system-oriented approach. DevOps emphasizes people (and culture) and seeks to improve collaboration between operations and development teams. DevOps implementations utilize technology — especially automation tools that can leverage an increasingly programmable and dynamic infrastructure from a life cycle perspective”. - Gartner, Inc. Businesses that incorporate a DevOps model into their workflows see benefits like: Scalability. Fundamental processes like infrastructure and development are operated at scale, which allows for a more efficient approach to developing, testing, and producing environments in a repeatable and streamlined way. Faster and more reliable delivery. The modern customer's need for speed is real, and DevOps can support organizations in their quest to speeding up feature releases, bug fixes, and other types of upgrades. Continuous integration and delivery are two critical practices that can automate the release process. High velocity. Adopting an efficient DevOps model allows professionals to build digital innovations faster and keep up with the trends imposed by ever-changing markets. Security. When adopting DevOps, you don't have to compromise on safety as DevOps models provide automated compliance policies and configuration management mechanisms. DevOps best practices To make the most out of DevOps, there are some key practices to follow when implementing your model: Leverage microservices architecture, which allows breaking down large systems into more specific, independent projects. As a result, developers and architects have more flexibility over managing these projects, and applications are more pliable and allow faster innovation. Install minor updates on a regular basis to solve issues and fix bugs quicker. The DevOps model aids companies in deploying updates more often and constantly optimizing their ongoing processes. Use continuous integration and continuous delivery to overcome operational challenges in complex development workflows. Don't forget about infrastructure as a code, as automating your infrastructure provides better computing resources and higher responsiveness to possible alterations. DevOps for Drupal development Implementing a DevOps model into your Drupal development workflow will not only accelerate your development cycle and delivery but will also contribute to better user experiences and business outcomes. As more companies are adopting DevOps models (according to a recent report, 60% of businesses are using or are considering DevOps for their organization), it is expected that DevOps will gradually become even more essential for any digital business. With this growth will come better opportunities for building future-ready Drupal deployments and web experiences suited for the modern customer’s complex needs. Wrapping Up DevOps continues to grow in new industries, opening possibilities for enhancing security, product monitoring, development, and cluster computing. As it will become the new norm, DevOps will continue to integrate more departments, improve solutions and designs. As we've seen, DevOps models can also support a Drupal development team that focuses on improving project timelines and delivery. Optasy is the right partner for fostering digital innovation and can help you create customized Drupal digital experiences. What do you need support with? Photo credit: PCB-Tech on Pixabay. ... Read more

Raluca Olariu / Apr 02'2021

Why Would You Build Your Own Cloud Native Drupal Platform? The Main Benefits and Challenges to Consider

1. What Does Cloud Native Mean Exactly?

2. And What Is Cloud Native with Respect to Drupal?

3. Why Build Your Own Cloud Native Drupal Platform? And When?

4. Why Would You Want to Containerize Your Drupal Apps in the First Place?