- We are using terraform for creating infrastructure as code and take our time to describe the infrastructure one time that gives us an ability to run a copy of environment in different regions, accounts etc. We deployed different environments: from the easiest one-server deployment with 3-5 containers using Ansible to environments with scaling groups on AWS with 10-20 microservices using Terraform.
- We are familiar with segment/stack – it is an external module for terraform to manage AWS resources. In our project we use only native AWS terraform provider, but we have also experience to develop own modules for Terraform like that.
Our experience
Laravel applications often contain a large number of files that need to be interpreted with each server request. In my project, the number of files reached 20,000, causing significant disk load and affecting page load speed. The solution to this problem was using PHP OPcache, which significantly reduced IOPS and doubled the speed of request […]
Our experience
Challenge: We deployed an AWS ECS Cluster using Terraform, with multiple application components communicating via AWS Network Load Balancer (NLB). The NLB was chosen because the application used a custom protocol (AKKA Cluster Discovery Protocol over TCP), which AWS ALB does not support. Initially, everything worked fine with an external-facing NLB, but the client requested […]
Our experience
The provided diagram illustrates three similar environments: development, staging, and production. Development and staging are hosted in the same AWS region, while production can optionally be deployed in a region of choice. The infrastructure includes the following components: AWS ECS (or optionally AWS Elastic Beanstalk) for application orchestration. AWS RDS for relational database management. AWS […]