Building a dynamic staging platform

1

Ruby on Rails

Like many Ruby on Rails apps, we use background jobs in Aha! To help provide a robust and responsive user interface. We use Resque backed by Redis for queuing up these jobs in the web app for subsequent processing by worker processes.

#Developer Tools #Web Frameworks #Frameworks (Full Stack) 119 social mentions

2

Redis

Since we use AWS Elastic Container Service (ECS) for our container orchestration, our dynamic stagings would also run under ECS. Rather than create a whole new set of infrastructure for each new dynamic staging, we selected one of our existing staging environments to serve as the dynamic staging host environment. This allows dynamic stagings to share certain resources that are owned by the host environment — in particular, the database instance, Redis/ElastiCache instance, and certain other Aha! Compute resources. This approach further helps achieve the goal of being able to quickly create and destroy dynamic stagings.

#Key-Value Database #NoSQL Databases #Databases 185 social mentions

3

Resque

Background jobs are another limitation. Since only the Aha! Web service runs in a dynamic staging, the host environment's workers would process any Resque jobs that were sent to the shared Redis instance. If your branch hadn't updated any background-able methods, this would be no big deal. But if you were hoping to test changes to these methods, you would be out of luck.

#Data Integration #Stream Processing #Web Service Automation 5 social mentions

4

Amazon ElastiCache

Since we use AWS Elastic Container Service (ECS) for our container orchestration, our dynamic stagings would also run under ECS. Rather than create a whole new set of infrastructure for each new dynamic staging, we selected one of our existing staging environments to serve as the dynamic staging host environment. This allows dynamic stagings to share certain resources that are owned by the host environment — in particular, the database instance, Redis/ElastiCache instance, and certain other Aha! Compute resources. This approach further helps achieve the goal of being able to quickly create and destroy dynamic stagings.

#Databases #NoSQL Databases #Key-Value Database 12 social mentions

5

Amazon ECS

Since we use AWS Elastic Container Service (ECS) for our container orchestration, our dynamic stagings would also run under ECS. Rather than create a whole new set of infrastructure for each new dynamic staging, we selected one of our existing staging environments to serve as the dynamic staging host environment. This allows dynamic stagings to share certain resources that are owned by the host environment — in particular, the database instance, Redis/ElastiCache instance, and certain other Aha! Compute resources. This approach further helps achieve the goal of being able to quickly create and destroy dynamic stagings.

#Developer Tools #Containers As A Service #Cloud Computing 46 social mentions

6

Amazon EC2

For dynamic stagings, we updated our DNS to point all "dynamic" subdomains at a new EC2 application load balancer. Then when new dynamic stagings are created, a listener rule is added to this load balancer to direct traffic to the new ECS service.

#Cloud Computing #Cloud Infrastructure #VPS 63 social mentions