Architecture
A summary of the AWS hosted environment of Naviga Web.
Last updated
Was this helpful?
A summary of the AWS hosted environment of Naviga Web.
Last updated
Was this helpful?
The environment is setup as an Elastic Beanstalk environment and includes EC2, RDS, Elasticache and more. Naviga services like Imengine, Open Content and CCT are not included in this overview.
Used to route end users to the application.
As a part of the deployment of application code we upload static files such as .js, .css and image assets to an S3 bucket, these are then fetched through CloudFront and cached. Every deploy will set the git commit version as a environment variable that can be used to ensure that all static files are refreshed after deploy.
Automatically distributes incoming traffic to the different EC2 instances.
This is where the actual application runs. The Docker containers are separated and one runs Nginx extended with Lua (OpenResty) and another container with PHP-FPM.
A typical Everyware environment includes two Elasticache redis instances, one for the "front-cache" and one for the "object-cache".
The "front-cache" will store generated HTML and supply it to the users directly through nginx without executing any PHP/Wordpress code if applicable.
The "object-cache" stores JSON data retrieved from Open Content and protects the Wordpress database from traffic overload.
The Wordpress database instance.
The Open Content that Everyware connects to, this is where we fetch articles, concepts, images and more.
The Open Content Notifier will post events to the Everyware servers, these events are used to update the object cache and more.
