The Journey To Front-End Performance  —  Assessing Current Performance

Our Application Framework team was tasked with assessing and improving application performance. Analyzing performance across the globe is challenging. The architectural layout of Meltwater’s application, as well as the way we organize our teams, lead to various challenges.

This is the first post in a series about front-end performance. We will share how our Application Framework team went about assessing the current performance of our app. Continual monitoring and relative metrics are a cornerstone to build from when focusing on performance. Here is how we laid our cornerstone.

Cheaper Logging from AWS Lambdas

To provide structured data from the Web to our customers, our team maintains a web crawler. The system downloads and processes 600K URLs per hour, resulting in huge amounts of logs. That costs a lot!

In this blog post, Róbert from our Crawler team explains how we modified our architecture to save 40k USD/year on logging.

First Commits at Meltwater Engineering

When you start at a new company, the first weeks are a turmoil of new things. The Meltwater Product & Engineering team is no different. When new colleagues join us, they go through an onboarding phase with parts that are standardized across the company, and other elements custom to their team. Still due to the different backgrounds, and expectations, everybody will have a slightly different experience.

You cannot generalize personal experiences. It is best to hear those experiences from the individuals directly. In this post five new colleagues share how their first couple of weeks at Meltwater went.

Dynamic Route53 records for AWS Auto Scaling Groups with Terraform

AWS Auto Scaling Groups may seem outdated in a world dominated by Serverless and Kubernetes, but they still have their place in Meltwater’s AWS infrastructure.

One thing we felt was missing in Auto Scaling Groups are unique instance names. EC2 instances launched in the ASG are given the same Name tag, with no internal Route53 DNS entry. We have addressed this issue with an easy-to-use Terraform module called asg-dns-handler.

Introduction to the AWS Cloud Development Kit (CDK)

Meltwater takes pride in having autonomous devops-enabled teams. This includes decisions on how to deploy their infrastructure. In this post Andy Desmarais is sharing an introduction to the newest deployment method that his team is experimenting with, the AWS Cloud Development Kit.

You also find more articles like these on Andy’s blog terodox.tech.