How would you choose which architecture you must implement in AWS? Which factors are chosen and which ones shouldn’t? What data is needed to have a wide decision?

455 viewscircle icon2 Comments
Sort by:
Director of IT in Healthcare and Biotech2 years ago

Because of the scale enterprises and the software portfolio consisting of hundreds if not thousands of applications, most companies usually end up deploying every imaginable architecture. Ideally everything will be SaaS/cloud-native/microservices-based, and enterprises that are "cloudy" have a preference tree of application architectures, with lift'n'shifted monolithic systems being the least desired. But companies have to deal with a lot of apps in the middle, e.g. partially refactored, and also vendor applications that are only half-way cloudy. 

More important than any one architecture is the organizational structure supporting cloud/AWS. A centralized team (aka Cloud COE) can work with many application teams and guide each to a more optimized solution or architecture. They'll also handle the cloud vendor(s), assist with training, EA, etc. 

Lightbulb on2
Global Chief Cybersecurity Strategist & CISO in Healthcare and Biotech2 years ago

What data will be stored? What data is running through? Etc. For example healthcare l, government, financial have different criteria and may need private cloud. Get with AWS professional services for support and look at the blueprints but the company are the ultimate decision maker and liable. Pay close attention to share responsibility matrix

Lightbulb on1

Content you might like

A fully-managed, serverless federation service tightly integrated with a single primary database vendor's cloud ecosystem for ease of use.30%

A flexible solution that offers greater control over deployment (e.g., on-premises, hybrid cloud/VPC) to meet data sovereignty, security, or multi-cloud requirements.43%

A primary focus on real-time performance and complex analytics, even if it means moving data into a specialized data warehouse or data lakehouse.37%

Simplified data governance and a unified security model that can be applied across all connected data sources, regardless of the underlying technology.10%

View Results

Bleeding Edge - We lead the charge!18%

Leading Edge - Willing to accept a reasonable number of issues to be an early adopter62%

Stable - Minimal issues before we adopt18%

If it ain’t broke - As long as it works we are good to go, no need to upset the cart2%

View Results