Summary

Instances

The first Beetrack's Architecture was created in AWS Opsworks. It is a service to manage instances using Chef (our choice) or Puppet. We have left these services because now Beetrack runs with Containers.

Containers

In our new architecture we are using Containers (Docker), Fargate with AWS and Kubernetes with GCP as Container Service Manager for our different services. For developing sometimes we used to use,docker-compose but in some cases, some applications are too big and have a lot of services, for that reason are mounted directly in the machine.

Continuos Integration and Deployment (CI/CD)

We use CircleCI to automatize continuous Integration and deployment. CircleCI has a lot of features that makes easier our work.

Example One beetrack's service pipeline

IaC

Terraform is our application for managing and provisioning the infrastructure. In words of Hashicorp:

Terraform enables you to safely and predictably create, change, and improve infrastructure. It is an open source tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.

Container Registry

Docker images are saved in ECR, GCR, and some un Dockerhub. With the last, is a good approach because now it allows the trigger to auto-build and webhooks.

Lambda Functions

A lot of AWS lambda functions, some functionalities that are not necessary to build a big application or need to extend.

Last updated

Was this helpful?