Archive of stories published by Towards Polyglot Architecture

Homepage

Open in app

All

2022

2023

Nitin Khaitan in Towards Polyglot Architecture

Jan 5, 2023

Comparison between SQS, SNS & EventBridge for the attributes A2A, A2P, Supports Scheduling, Push, Email & SMS Support, Messaging pattern, Subscribers, Delivery of messages, Ordered delivery of messages (FIFO), Event Filtering, Event Transformation, Payload — Persistence, Scheme Registry, Encryption (at Rest), Encryption (in Motion), Throughput, Latency in communication, Can retry in case of failure, Dead Letter Queue (DLQ), Event Archival, Event Replay, Batch

AWS SQS, SNS & Event Bridge — When to use what?

Nitin Khaitan in Towards Polyglot Architecture

Sep 10, 2022

Design patterns for the database layer

It describes a generic approach to common design problems that…

3 responses

Nitin Khaitan in Towards Polyglot Architecture

Dec 10, 2022

In the case of Synchronous communication, REST and gRPC are two widely adopted protocols. They both are required and are an important component in case of inter-service communication between microservices.

gRPC vs REST — Comparing API architecture

One-size-fits-all does not hold anymore in the world of microservice. In the…

2 responses

Nitin Khaitan in Towards Polyglot Architecture

Aug 27, 2022

Designing the Data Layer in an Application

The data layer is a key layer in the overall architecture…

Nitin Khaitan in Towards Polyglot Architecture

Jan 7, 2023

Adaptive resilience is the key to having healthy inter-service communication between the microservices. If it is handled with care and planning, it can keep the system healthy, not just with the daily load but also will be able to handle the spike in a better way.

Resilient and high availability in microservices

Nitin Khaitan in Towards Polyglot Architecture

Aug 14, 2022

Why is Software Architecture Important?

A good quality code can’t be achieved with a compromised timeline/cost in delivery. It’s the key to good Software Architecture.

Software architecture reflects the internal quality of the product compared to the user…

Nitin Khaitan in Towards Polyglot Architecture

Nov 15, 2022

A few associated gains with microservices are Customer experience, Time-to-market, Fast development cycle, Room for Experiment, Independent Deployment, A/B Testing, Localised failure, 24x7 deployment, Highly scalable, Easy to build and enhance, Less coupling, Independent Release Cycle, Code Reusability, New Technology Adoption, Accessible to Maintain & Troubleshoot, Fewer changes of failure, Team Productivity, High Ownership, Task Breakdown and Improved cross-team coordination

Why Use Microservices — Breaking the Monolith

25 reasons why an organisation should use Microservice…

Nitin Khaitan in Towards Polyglot Architecture

Oct 23, 2022

Design data layer perspective from schema, design, query, performance, scalability, load and security perspectives

45+ best data layer principles

These were the top 10 stories published by Towards Polyglot Architecture; you can also dive into yearly archives: 2022, 2023.

About

Towards Polyglot Architecture

We publish tutorials, case studies, how-tos, inspiration, writing advice, industry trends, and tips from industry experts. We support independent authors in publishing their work, sharing their knowledge and expertise, and expertise, and engage a wide audience on Medium.

More information

AWS SQS, SNS & Event Bridge — When to use what?

Design patterns for the database layer

It describes a generic approach to common design problems that…

gRPC vs REST — Comparing API architecture

Designing the Data Layer in an Application

The data layer is a key layer in the overall architecture…

Resilient and high availability in microservices

Why is Software Architecture Important?

Why Use Microservices — Breaking the Monolith

25 reasons why an organisation should use Microservice…

45+ best data layer principles

The data layer is one of the crucial layers of an application.

The Power of Polyglot Architecture: A Guide for Modern Organisations

Design thinking toward Data-Driven Organisation