Our Blog

Welcome to the second post in a series of “Implementing Microservices on AWS with the Twelve-factor App”. In the first post, we covered the areas around the codebase, configuration, code packaging, code builds, and stateless processes.  This article will go through the remaining areas for best practices in microservices.  Let’s start the discussion with Port mapping!

Morgan Perry

Co-founder

When collecting information on how to write GRPC or Websocket servers for our Qovery infrastructure, I came across a lot of resources. But while many guides provided an in-depth insight into futures, they sorely lacked information on how the Stream API works in Rust. And, more importantly, on how to use it properly. Sadly, you can't turn a blind eye on streams. As soon as you go beyond the simple request/response protocol of our beloved REST APIs, the notions of flow, async generator, and so on, inevitably arise. This is especially true when it comes to Rust. When you decide to use tonic for your GRPC or tokio tungstenite for your Websocket, the only usable interfaces with those libraries revolve around streams. This is why this article focuses on introducing streams in the context of Rust.

Romain Gérard

Staff Software Engineer

The Twelve-Factor methodology is a set of best practices for developing microservices applications. These practices are segregated into twelve different areas of application development. Twelve-factor is the standard architectural pattern to develop SaaS-based modern and scalable cloud applications. It is highly recommended by AWS if you are building containerized microservices. In this article, we will guide you on how to develop applications that will use microservices deployed on containers in AWS. We will discuss the first six areas today. And in the next article (part 2), we will discuss best practices for the remaining six areas.

Morgan Perry

Co-founder

While meetings are part of today's organizations, they can also bring some frustration preventing one from scratching its TODO list. It can be a good idea to try to promote asynchronous mediums such as Notion pages, Slack channels, etc. This page aims to bring some insights regarding WHEN / WHY holding or not a meeting.

Alessandro Carrano

Head of Product

Hi, fellow Qovery readers, Albane here! 👋🏻 To give you a bit of background, I joined Qovery in August 2021, initially as a Product Owner, then moved to a Product Marketing Manager position in March 2022. So yes, I’m all about our product. However, I also spend much time learning about our partner’s products, and that’s why, on April 27, 2022, I spent the day at the ExCel Centre in London to attend the annual AWS Summit. While I did spend a reasonable amount of time enjoying the several activities such as the AWS Deepracer, the educational sessions (and the free smoothies 🥤), I was mainly there to attend sessions, and I made you a shortlist of my top three sessions of the day.

Albane Tonnellier

Product Marketing Manager

We are in 2023, and hundreds of startups have built their infrastructure on AWS using Qovery's DevOps automation tool. This article will share the 10 best (and fancy) AWS architectures our customers have made. From the most classic architecture to the craziest 🤪 It can give you some ideas. Let's go 🚀

Romaric Philogène

CEO & Co-founder

AWS ELB (Elastic load balancer) automatically distributes incoming application traffic across multiple targets and virtual appliances in one or more Availability Zones (AZs). That helps you achieve high availability and fault tolerance. In this article, we will share with you some tips that will help you best utilize AWS load balancer. We will also provide insights on the best use cases of ALB and NLB, which are the two most commonly used load balancers.

Morgan Perry

Co-founder

In 2020, my co-founders and I had this crazy idea of bringing a better Developer Experience on top of AWS. As developers often start on a path with a simple React app or a JS tool, they need a platform that would support them throughout the process of building robust applications. You know, the one that any developer can build and deploy their next successful product in seconds using their preferred tools. Somehow, AWS lacked this offering 😅. This is where Netlify, especially Netlify functions, came in as an inspiration, especially with its ease of settings configuration. The Developer Experience on Netlify, where deploying an application is as easy as pushing code to Git, attracted many. But while many use Netlify for frontend, it doesn’t run on your AWS account :(. In 2 years, 20,000+ developers and hundreds of companies have transitioned from Netlify to AWS with Qovery, leveraging the unique settings and Developer Experience.

Romaric Philogène

CEO & Co-founder

Using containers for microservices has gained a lot of popularity in the last decade or so. Developing the application through microservices across multiple containers results in the best of both worlds. It provides resilience as well as agility through scaling and improvements. Before we dwell on how containers and microservices form an ideal combination, let’s start with a basic understanding of microservices and containers.

Morgan Perry

Co-founder