Nitin Khaitan – Medium

Nitin Khaitan

Pinned

Published in
Towards Polyglot Architecture

Resilient and high availability in microservices

Microservices should be designed for resilience and can expect partial, intermittent failures. It should be designed to recover from…

Jan 8, 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.

Jan 8, 2023

Pinned

Published in
Towards Polyglot Architecture

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

Breaking the extensive monolith system into smaller microservices is advisable as the system grows. It helps keep the system resilient…

Feb 2, 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

Feb 2, 2023

Pinned

Published in
Towards Polyglot Architecture

gRPC vs REST — Comparing API architecture

One-size-fits-all does not hold anymore in the world of microservice. In the microservice arena, we divide an extensive monolith system…

Dec 11, 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.

Dec 11, 2022

Pinned

Published in
Towards Polyglot Architecture

Design thinking toward Data-Driven Organisation

We generate roughly 2.5 quintillion bytes of data worldwide every day. In this data-centric environment, every organisation wants to be…

Aug 20, 2022

Every day, we roughly generate 2.5 quintillion bytes of data worldwide. The path moving from just an organisation that generates a lot of data to an organisation that creates and relies upon a centralised data lake and can maintain data sanctity satisfying current as well as future vision is not that easy. It requires a lot of design thinking, architectural building blocks, design principles and good practices to be in place. By — Nitin Khaitan

Aug 20, 2022

Pinned

Published in
Towards Polyglot Architecture

Why is Software Architecture Important?

Software architecture reflects the internal quality of the product compared to the user interface, which reflects the external marker.

Aug 15, 2022

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

Aug 15, 2022

Published in
Towards Polyglot Architecture

Mastering Cloud Cost Optimisation: 21 Strategies for Maximising Cloud Investments

A Comprehensive Guide to Controlling Cloud Costs and Boosting Performance

Jun 26, 2023

Optimise the cloud costs for the dynamic infrastructure via cost-saving gears such as Compute Optimisation, Cautious Selection of Services, Storage Optimisation, Database Cleanup, Application Code Optimisation, Network Optimisation, Regular Cleanup & Disaster Recovery Strategy

Jun 26, 2023

Published in
Towards Polyglot Architecture

The Power of Polyglot Architecture: A Guide for Modern Organisations

Discover the benefits and challenges of adopting a Polyglot Architecture and how to successfully implement it in your organisation.

Feb 1, 2023

A visual representation of the concept of Polyglot Architecture, showcasing the diversity of technology stacks and programming languages used in modern organisations

Feb 1, 2023

Published in
Towards Polyglot Architecture

Why Use Microservices — Breaking the Monolith

25 reasons why an organisation should use Microservice. It is a practice not just for technology but it enables business and consumers…

Feb 2, 2023

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

Feb 2, 2023

Published in
Towards Polyglot Architecture

twelve-factor and data layer

Twelve-factor is a methodology for building software-as-a-service. It helps achieve clean code, maximum portability, highly automated…

Oct 31, 2022

twelve-factor and the data layer

Oct 31, 2022

Published in
Towards Polyglot Architecture

45+ best data layer principles

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

Oct 24, 2022

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

Oct 24, 2022

Nitin Khaitan

Nitin Khaitan

Strategic thinker, a technically astute developer/architect with 15+ years of experience owning engineering, backend, and frontend from infancy to success

Following

Help
Status
About
Careers
Press
Blog
Privacy
Terms
Text to speech
Teams