Hi folks.

Long time no see! Frankly speaking, I've had good reasons for my absence. There have been a lot of changes in my life, but let's start at the beginning.

A new opportunity

First and foremost, I've taken on a new role at MyLette as a software engineer. The company recently acquired a new FinTech application and was in search of developers for a new team. Not only was I the first person to join the team, but I also brought my experience with AWS.

My initial significant task involved migrating the application from one customer to another, setting up all the necessary environments and connecting third parties. I'd be lying if I said the developers who worked on this application before didn't assist me. They were quite helpful, especially with the DEV environment, and to a lesser extent, the TST environment.

When all environments were set up and the team was complete, we had a couple of brainstorming sessions. Not only to evaluate the application but also to outline the next steps.

1. The first step was to create some integration tests and cover the core functionality. We chose the playwright framework for it, and I was responsible for setting it up. I'll share the results in my next articles.

2. The second one was to improve the deployment process. These findings were discovered during application deployment. I have a few words to say about the application. The application follows a multi-service architecture, and there were around 10 services. Most of the AWS resources were created by AWS CDK, but some resources were created manually. In addition to that, every service has its own configuration folder with files for each environment (dev, tst, acc, and prd). As part of this task, I created a config-gen CLI, and I'll share it in my next articles.

3. The third task was to address the findings from the AWS Well-Architected Framework. This framework consists of six pillars: operational excellence, security, reliability, performance efficiency, cost optimization, and sustainability. Each pillar includes several recommendations. One of the key recommendations was to eliminate direct lambda function invocations. Cross-service requests were previously implemented using the direct invocation approach, and I'll share it in my next articles.

There were many other interesting decisions and features implemented. I'll also share the most intriguing ones in my next articles.

Stay tuned.