Murat Balkan

CORE

Distinguished Engineer at Capital One

Toronto, CA

Joined Nov 2014

https://muratbalkan.net

Stats

Reputation:	396
Pageviews:	120.9K
Articles:	6
Comments:	2

Articles
Comments

Articles

The Right ETL Architecture for Multi-Source Data Integration

Dedicated ETL pipelines are easy to set up but hard to scale, while common pipelines offer efficiency at the cost of complexity. Know which one to choose.

February 12, 2025

· 3,930 Views · 1 Like

Shared Platforms Explained: Navigating the Enterprise Ecosystem

Exploring the benefits of shared platforms and best practices from the perspectives of both application and platform owners.

December 15, 2023

· 5,185 Views · 10 Likes

Using AWS Step Functions For Offloading Exponential Backoffs

This tutorial demonstrates how you can apply AWS Step Functions to offload exponential backoffs as well as the technical challenges that entails.

Updated February 6, 2020

· 8,418 Views · 2 Likes

Protecting Multi-Tenant RabbitMQ Instances From Queue Backlogs

Let's take a look at how to protect multi-tenant RabbitMQ instances from queue backlogs and also explore the topology.

Updated October 16, 2018

· 14,945 Views · 4 Likes

Asynchronous Retries With AWS SQS

In this article, I will explain asynchronous retry mechanisms and demonstrate how to achieve retries by using the native functions of a broker using AWS SQS.

February 6, 2018

· 46,361 Views · 4 Likes

Asynchronous Communication — Methods and Strategies

Asynchronous communication might be one way to consider to free up some of those sweet, sweet CPU cycles and increase overall performance.

January 11, 2018

· 22,906 Views · 9 Likes

Comments

Asynchronous Retries With AWS SQS

Apr 06, 2018 · Murat Balkan

You can also do sharding between multiple queue sets (main + DL). Implementation classes will be shared so no additional coding would be necessary. The client can determine the queue set by a simple round robin at the initial publish.

Asynchronous Retries With AWS SQS

Apr 04, 2018 · Murat Balkan

Gabor, thanks a lot for pointing out this limitation. To me, "serverless" means, there should not be these kinds of limitations developers need to take care of. It seems that AWS is not following this approach. I just used AWS SQS as an example broker to explain the mechanism but this limitation can be a showstopper for some organizations using only AWS technologies.