Fortaleza, Ceará, Brazil
In short, I'm up to any challenge; my specialty is solving problems. I’ve been working with many cloud computing challenges for more than a decade, solving many problems related to logistics and microservices architectures. I also have much experience related to DevOps and SRE. I've helped scale solutions that reached billions of requests per month.
* Kubernetes cluster management with Flux and Terraform * CI/CD platform - with ephemeral self-hosted GitHub Actions runners * Observability stack deployment and evolution * Jaeger * OpenTelemetry * Victoria Metrics
I led a platform team during the Kubernetes migration. We were moving the whole system from ECS to Kubernetes on AWS. Tech stack/technologies: Kubernetes, Terraform, Kafka, Flux (GitOps), Grafana, Prometheus, Keda, Java, Kotlin, Golang.
As a member of the Marketplace Platform Squad, whose primary goal was to automate the deployment process and improve the resilience of the entire marketplace platform. We're working closely with other teams on building new services and moving the existing ones from the on-premise infrastructure to Azure. During this journey, we're using Kafka, Jenkins (pipeline as code using Groovy and shared libraries), Kubernetes AKS, Prometheus (and its ecosystem), and Kotlin for the new services. More recently, we've created a Kubernetes Operator to register services in Netflix Eureka using CRDs and Kubebuilder to help us during the transition to Azure.
I consider that my main accomplishment here was the deliver of a new and redesigned invoice (NF-e) service. I took the leadership of this project and, trying to make it simple we fast delivered an extensible invoice (NF-e) service that made much easier to integrate with more and more cities. This microservice was created using Spring Boot and PostgreSQL running on GCP. (GKE and Cloud SQL).
Back-End development team leader, responsible for building and implementing complex, performant and scalable solutions. As a real time monitoring system of delivery routes, GreenMile needs to be able to receive a huge amount of data and process it with a high performance. My last challenge with the team I was leading was to smoothly migrate GreenMile platform from a monolithic to a microservices-based architecture. I worked with a lot of technologies, including: JEE, JSON, REST, Swagger, MongoDB, Memcached, Redis, Spring frameworks beyond the core (including Spring Boot, Cloud, MVC, Data and Security), Hibernate, Apache Kafka, Unit test for backend, Maven, Web Services, Graphhopper, OpenStreetMaps data, Mapnik, Nginx. GreenMile uses Amazon Web Services cloud and I'm very familiar with: ECS, EC2, AutoScaling Groups, SNS, SQS, SES, Elastic Beanstalk, Lambda, Route 53, S3, VPC, RDS, ElastiCache, CloudFront and more. I also have experience with Docker containers orchestration.
I joined the platform team to automate the company's deployment process and improve the resilience of the entire solution (SRE). About the CI thing, basically we started to use tools like Docker, ECS, Fabric, Ansible, Hubot and other ChatOps tools to automate our deployment process. I was also part of the team that designed and developed a new microservices architecture to the solution also including a set of monitoring tools that we started to use as Prometheus and Grafana to list some.
Responsible to develop, together with my team, the back-end of the SaaS solution for GreenMile. At the time the software was created using a monolith architecture using Spring Framework, Hibernate, Memcached, Oracle, PostgreSQL and PostGIS (for GIS data) and MongoDB.