Here are the most recent articles I wrote. They grow up so fast.
Posted Friday February 12, 2021
Words of notice: This is an article has been written by Antoine Cavaillé. Many thanks for their consent to sharing this story here. Before we begin, check out the first part of the series in case you missed it. It presents the backbone, the base layer of our infrastructure. This second part concentrates on the different components needed by our application to run on Huawei Cloud. Part 1: Docker Repository To deploy our application on Kubernetes, we will be using Docker containers. Those containers will need an image to run and we chose to store the images on a Huawei...
Posted Friday February 05, 2021
Words of notice: This is an article has been written by Antoine Cavaillé. Many thanks for their consent to sharing this story here. Some elements of context As a Cloud Engineer at Gekko Part of Accenture, I am comfortable running complex infrastructure on AWS which provides datacenters all over the world. But in one project, a customer wished to replicate their infrastructure on a different Cloud provider, Huawei Cloud! I was only aware of the existence of Huawei hardware such as smartphones, computers and IT oriented products but not as a Cloud provider so I decided to share my experience...
Posted Friday December 18, 2020
Words of notice: This is an article I wrote for Gekko. Many thanks for their consent to sharing this story here. Throughout their services, AWS uses a special type of sharding called “Shuffle sharding” to virtually isolate each customer while colocating their resources. The most visible example, the one mentioned in the Amazon Builders’ Library, concerns Route 53 and how each DNS zone gets assigned four of the 2048 virtual shards created by AWS for the service. There are 700B+ possible combinations of those shards and the number of combinations grows exponentially with the number of virtual shards and the...
Posted Sunday December 13, 2020
Words of notice: This is an article I wrote for Gekko. Many thanks for their consent to sharing this story here. There are many different storage types in the wild and they each have specifics that make them suitable for defined sets of use cases. Regardless of the scale, storage poses challenging issues. For instance Brewer’s theorem, also known as the CAP theorem, states that designing distributed data stores requires trade-offs. Simply put, in case of a write failure on a storage system due to internal network conditions, would it be preferable to drop the operation or to attempt to...
Posted Wednesday December 02, 2020
Words of notice: This is an article I wrote for Gekko. Many thanks for their consent to sharing this story here. The right architecture for the right need Over the last few years, we have observed a steady growth of compute-layer services that natively integrate cost-efficiency, operational excellence, performance, security and reliability. These services are the same that development teams leverage in order to spend more time on their products and less time tweaking infrastructure and connecting pipes. Among these services are AWS Lambda, AWS Fargate and its companion services AWS ECS and AWS EKS.
Developed with ❤