AWS Architecture Blog

Piyali Kamra

Author: Piyali Kamra

Piyali Kamra is a seasoned enterprise architect and a hands-on technologist who has over 21 years of experience building and executing large scale enterprise IT projects across geographies.She believes that building large scale enterprise systems is not an exact science but more like an art, where you can’t always choose the best technology that comes to one’s mind but rather tools and technologies must be carefully selected based on the team’s culture , strengths , weaknesses and risks , in tandem with having a futuristic vision as to how you want to shape your product a few years down the road.

Dimensions for operational visibility

A multi-dimensional approach helps you proactively prepare for failures, Part 3: Operations and process resiliency

In Part 1 and Part 2 of this series, we discussed how to build application layer and infrastructure layer resiliency. In Part 3, we explore how to develop resilient applications, and the need to test and break our operational processes and run books. Processes are needed to capture baseline metrics and boundary conditions. Detecting deviations […]

AWS managed services help in building resilient infrastructures (click the image to enlarge)

A multi-dimensional approach helps you proactively prepare for failures, Part 2: Infrastructure layer

Distributed applications resiliency is a cumulative resiliency of applications, infrastructure, and operational processes. Part 1 of this series explored application layer resiliency. In Part 2, we discuss how using Amazon Web Services (AWS) managed services, redundancy, high availability, and infrastructure failover patterns based on recovery time and point objectives (RTO and RPO, respectively) can help in […]

Decision criteria for event-driven architecture pattern

A multi-dimensional approach helps you proactively prepare for failures, Part 1: Application layer

Resiliency of applications surpasses everything else in building customer trust. Because of this, it cannot be an afterthought. Instead of simply reacting to a failure, why not be proactive? As your system expands, you’ll likely encounter issues that can hinder your ability to scale, like security and cost. So, it’s necessary to think about the […]