Pedro Arnal Puente

As a substitute for ActiveMQ, we have built a new message bus with Amazon SNS and Amazon SQS. For the local dev env we'll use LocalStack.

Our base infrastructure is composed of Debian based servers running in Amazon EC2 , asset storage with Amazon S3 , and Amazon RDS for Aurora and Redis under Amazon ElastiCache for data storage.

We are starting to work in automated provisioning and management with Terraform.

When we started working on the core of our main webapp, written in PHP , there weren't mature deployment tools in that language.

So we adopted Capistrano from the 1st deployment.

All deployments have been done with the tool. Deploying as often as needed, often many times daily, that means a LOT of deployments.

For every new service we'll aim for deployable artifacts, instead of application deployment.

Our command and event buses uses stomp as protocol, over RabbitMQ in development, and Amazon MQ in production.

Currently bus communicates Ruby and PHP based clients.

We currently use Docker to simplify our Vagrant based development environment. As we learn more about it, and how to manage it in production environments, we'll decide about expanding our use.

Anyway, every new service will be designed with maximum "containerizability" in mind.

We are phasing out jQuery and jQuery UI in favour or Vue.js and @Vue-cli so we can support building a modern, well-architectured frontend.

The JavaScript build pipeline is supported by Webpack , and includes tools like ESLint and Babel , so we can properly support the latest ES/JS versions, with ES6 as the minimum baseline.

The older parts of our core are still using Zend Framework 1. We've added events, dependency injection, and other modernities with Laravel and Symfony components.

We will migrate towards simpler framework agnostic controllers with 3rd party components.