Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

AWS Storage Solutions for Enterprise Scale Joomla Deployments

DZone's Guide to

AWS Storage Solutions for Enterprise Scale Joomla Deployments

Using Joomla for web deployments? Consider bringing AWS into your enterprise solution with this sample architecture that covers storage and security.

· Cloud Zone ·
Free Resource

See why enterprise app developers love Cloud Foundry. Download the 2018 User Survey for a snapshot of Cloud Foundry users’ deployments and productivity.

Joomla CMS has its strengths for web deployment, where you get the guided installer for basic deployments. However, setting up Joomla for enterprises requires additional measures to be dealt with. Enterprises requires the deployment to be highly secure, reliable, fault tolerant, efficient and compliant with the standards. Using Amazon Web Services (AWS) for Joomla deployments, provides the necessary services and storage options to achieve the enterprise objectives. However, designing a deployment solution for an enterprise, can become a challenge. This article will take you though the insight on how to set up Joomla CMS for Enterprises.

Image title

Joomla CMS Webserver

Selecting Web Servers for Joomla has two possible options, either to use Virtual Machines (AWS EC2) or Containers (Docker). Both approaches have their own mechanics to achieve enterprise objectives. This article focuses on using EC2 for Joomla CMS deployment. When using EC2 for Joomla Web Server, it is important to understand the differences in using it only for execution on the Joomla Web Server externalizing the state to other storage services. There are Amazon native services such as AWS S3, Elastic File System, and EBS, and additional options based on popular databases in RDS with Redis allowing the Web Server to scale horizontally creating more instances while avoiding a single point of failure. One of the most common deployment patterns, involves setting up AWS Auto Scaling and Load Balancing with Launch Configurations (With instructions on how to start Joomla inside an EC2).

Tip: If this, sounds like too complex, you can automate the major configurations for Auto Scaling, and Load Balancing using AWS Elastic Beanstalk to provision an environment for your deployment where you can upload the compressed Joomla directory archive.

For the launch configuration, you can either use an Amazon Machine Image (AMI) which is a virtual machine image snapshot with Joomla CMS or provide instructions in scripts to install Joomla upon server boot. It is mostly recommended to use these two approaches in combination where the AMI has the basic installation while using scripts to customize the server upon boot.

File Storage

Since Joomla CMS instances will be stateless, using EC2 with Instance Store Volumes will give the price advantage in comparison to EBS though the cost difference is small. However, it is still required to use stateful storage for media and other uploads which can be shared across the running EC2 instances of Joomla CMS. For the shared storage of media, there are two options, we can consider in AWS.

If we plan to set up Joomla CMS with bare minimum knowledge about the media storage, then we can setup AWS Elastic File System which acts as a part of the storage, that can be mounted to multiple servers at once. For this setup, we need to provision an Elastic File System and mount to the media upload directory of each EC2 instance in its Launch Configuration.

On the other hand using S3 requires using extensions for media manager to upload file's content directly to AWS S3.

Cache Storage

When deploying Joomla for enterprise deployments, it is important to utilize caching to improve performance. For Cache storage, there are multiple options available.

AWS CloudFront can be used in conjunction with S3 to improve media loading performance by caching the content at AWS Edge Locations (Content Delivery Network Endpoints) and alternative approaches is to cache the entire Joomla site putting it behind CloudFront. With the second option, we can cache both content pages as well as the media resources altogether.

Apart from that, it is also possible to reduce the page load time using Radis In Memory Caching with the newer versions of Joomla.

Database Storage

Database storage setup is on of the most important decisions to make for Joomla enterprise deployments. It is important, not only to create the a database instance but also to look at backing up and restore of the database which is tightly bound with Recovery Point Objective (RPO) and Recovery Time Objective (RTO) of the deployment. It is also important to provide High Availability by creating synchronous replication.

The most ideal database solution in AWS is to use RDS service selecting Aurora, MySQL or PostgreSQL Engines. This will allow push button scaling, database replication with backup and restore, fully managed by the AWS RDS service.

Cloud Foundry saves app developers $100K and 10 weeks on average per development cycle. Download the 2018 User Survey for a snapshot of Cloud Foundry users’ deployments and productivity. Find out what people love about the industry standard cloud application platform.

Topics:
aws ,joomla ,storage optimization ,server storage ,tutorial ,cloud

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}