https://amzn.to/3lNebZm

(paid link) As an Amazon Associate I earn from qualifying purchases.

Welcome to the AGPIAL audiobook production of

McKinsey and Company.

Technology, Media and Telecommunications Practice's article.

SaaS and the Rule of 40.

Don't forget to like and subscribe.

Thank you, Now let's go !

Keys to the critical value creation metric.

Investors reward SaaS companies that hit this operating performance marker, yet a surprisingly small number have been able to do so.

Here’s how more can follow their industry leaders’ example.

by Paul Roche and Sid Tandon

SaaS Lens AWS Well-Architected Framework

https://amzn.to/39rBwd6

(paid link) As an Amazon Associate I earn from qualifying purchases.

Abstract.

This paper describes the SaaS Lens for the AWS Well-Architected Framework, which enables customers to review and improve their cloud-based architectures and better understand the business impact of their design decisions.

We address general design principles as well as specific best practices and guidance in five conceptual areas that we define as the pillars of the Well-Architected Framework.

Introduction.

The AWS Well-Architected Framework helps you understand the pros and cons of decisions you make while building systems on AWS.

By using the Framework you will learn architectural best practices for designing and operating reliable, secure, efficient, and cost-effective systems in the cloud.

It provides a way for you to consistently measure your architectures against best practices and identify areas for improvement.

We believe that having well-architected systems greatly increases the likelihood of business success.

In this “Lens” we focus on how to design, deploy, and architect your multi-tenant software as a service (SaaS) application workloads in the AWS Cloud.

For brevity, we have only covered details from the Well- Architected Framework that are specific to SaaS workloads.

You should still consider best practices and questions that have not been included in this document when designing your architecture.

We recommend that you read the AWS Well-Architected Framework whitepaper.

This document is intended for those in technology roles, such as chief technology officers (CTOs), architects, developers, and operations team members.

After reading this document, you will understand AWS best practices and strategies to use when designing architectures for SaaS applications.

Serverless Architectures with AWS Lambda AWS Whitepaper.

https://amzn.to/2XKjsZp

(paid link) As an Amazon Associate I earn from qualifying purchases.

Abstract.

Since its introduction at AWS re:Invent in 2014, AWS Lambda has continued to be one of the fastest growing AWS services.

With its arrival, a new application architecture paradigm was created—referred to as serverless.

AWS now provides a number of different services that allow you to build full application stacks without the need to manage any servers.

Use cases like web or mobile backends, real-time data processing, chatbots and virtual assistants, Internet of Things (IoT) backends, and more can all be fully serverless.

For the logic layer of a serverless application, you can execute your business logic using AWS Lambda.

Developers and organizations are finding that AWS Lambda is enabling much faster development speed and experimentation than is possible when deploying applications in a traditional server-based environment.

This whitepaper is meant to provide you with a broad overview of AWS Lambda, its features, and a slew of recommendations and best practices for building your own serverless applications on AWS.

Security Overview of AWS Lambda AWS Whitepaper

https://amzn.to/3zpABEs

(paid link) As an Amazon Associate I earn from qualifying purchases.

Abstract.

This whitepaper presents a deep dive of the AWS Lambda service through a security lens.

It provides a well-rounded picture of the service, which is useful for new adopters, and deepens understanding of Lambda for current users.

The intended audience for this whitepaper is Chief Information Security Officers (CISOs), information security engineers, enterprise architects, compliance teams, and any others interested in understanding the underpinnings of AWS Lambda.

Introduction.

Today, more workloads are using AWS Lambda to achieve scalability, performance, and cost efficiency, without managing the underlying infrastructure.

These workloads scale to thousands of concurrent requests per second.

Lambda one of the many important services that is offered by AWS today.

Lambda is used by hundreds of thousands of Amazon Web Services (AWS) customers to serve trillions of requests every month.

Lambda is suitable for mission critical applications in many industries.

A broad variety of customers, from media and entertainment to financial services and other regulated industries, take advantage of Lambda.

These customers decrease time to market, optimize costs, and improve agility by focusing on what they do best: running their business.

The managed runtime environment model enables Lambda to manage much of the implementation details of running serverless workloads.

This model further reduces the attack surface while making cloud security simpler.

This whitepaper presents the underpinnings of that model, along with best practices, to developers, security analysts, security and compliance teams, and other stakeholders.

00:00:00 Welcome

00:00:14 Abstract

00:00:43 Introduction

00:01:56 About AWS Lambda

00:03:32 Benefits of Lambda

00:05:54 Cost for running Lambda-based applications

00:06:20 The Shared Responsibility Model

00:07:00 Lambda Functions and Layers

00:08:23 Lambda Invoke Modes

00:11:40 Lambda Executions

00:13:03 Lambda execution environments

00:16:00 Execution role

00:17:14 Lambda MicroVMs and Workers

00:20:15 Lambda Isolation Technologies

00:22:07 Storage and state

00:24:29 Runtime Maintenance in Lambda

00:27:00 Monitoring and Auditing Lambda Functions

00:29:16 Architecting and Operating Lambda Functions

00:30:41 Lambda and Compliance

00:31:55 Lambda Event Sources

00:33:32 Conclusion

00:34:09 Contributors

Serverless Applications Lens AWS Well-Architected Framework

https://amzn.to/3znWIvg

(paid link) As an Amazon Associate I earn from qualifying purchases.

Abstract.

This document describes the Serverless Applications Lens for the AWS Well-Architected Framework.

The document covers common serverless applications scenarios and identifies key elements to ensure that your workloads are architected according to best practices.

Introduction.

The AWS Well-Architected Framework helps you understand the pros and cons of decisions you make while building systems on AWS.

By using the Framework, you will learn architectural best practices for designing and operating reliable, secure, efficient, and cost-effective systems in the cloud.

It provides a way for you to consistently measure your architectures against best practices and identify areas for improvement.

We believe that having well-architected systems greatly increases the likelihood of business success.

In this “Lens” we focus on how to design, deploy, and architect your serverless application workloads in the AWS Cloud.

For brevity, we have only covered details from the Well-Architected Framework that are specific to serverless workloads.

You should still consider best practices and questions that have not been included in this document when designing your architecture.

We recommend that you read the AWS Well-Architected Framework whitepaper.

This document is intended for those in technology roles, such as chief technology officers (CTOs), architects, developers, and operations team members.

After reading this document, you will understand AWS best practices and strategies to use when designing architectures for serverless applications.

Reliability Pillar AWS Well-Architected Framework.

https://amzn.to/3zk4UwC

(paid link) As an Amazon Associate I earn from qualifying purchases. 

Abstract.

The focus of this paper is the reliability pillar of the AWS Well-Architected Framework.

It provides guidance to help customers apply best practices in the design, delivery, and maintenance of Amazon Web Services (AWS) environments.

Introduction.

The AWS Well-Architected Framework helps you understand the pros and cons of decisions you make while building workloads on AWS.

By using the Framework you will learn architectural best practices for designing and operating reliable, secure, efficient, and cost-effective workloads in the cloud.

It provides a way to consistently measure your architectures against best practices and identify areas for improvement.

We believe that having well-architected workload greatly increases the likelihood of business success.

The AWS Well-Architected Framework is based on five pillars:

Operational Excellence

Security

Reliability

Performance Efficiency

Cost Optimization This paper focuses on the reliability pillar and how to apply it to your solutions.

Achieving reliability can be challenging in traditional on-premises environments due to single points of failure, lack of automation, and lack of elasticity.

By adopting the practices in this paper you will build architectures that have strong foundations, resilient architecture, consistent change management, and proven failure recovery processes.

This paper is intended for those in technology roles, such as chief technology officers (CTOs), architects, developers, and operations team members.

After reading this paper, you will understand AWS best practices and strategies to use when designing cloud architectures for reliability.

This paper includes high-level implementation details and architectural patterns, as well as references to additional resources.

Cost Optimization Pillar AWS Well-Architected Framework

https://amzn.to/2VLUhon

(paid link) As an Amazon Associate I earn from qualifying purchases.

Welcome to the AGPIAL audiobook production of

Cost Optimization Pillar AWS Well-Architected Framework.

Don't forget to like and subscribe.

Thank you, Now let's go !

Abstract.

This whitepaper focuses on the cost optimization pillar of the Amazon Web Services (AWS) Well- Architected Framework.

It provides guidance to help customers apply best practices in the design, delivery, and maintenance of AWS environments.

A cost-optimized workload fully utilizes all resources, achieves an outcome at the lowest possible price point, and meets your functional requirements.

This whitepaper provides in-depth guidance for building capability within your organization, designing your workload, selecting your services, configuring and operating the services, and applying cost optimization techniques.

Introduction.

The AWS Well-Architected Framework helps you understand the decisions you make while building workloads on AWS.

The Framework provides architectural best practices for designing and operating reliable, secure, efficient, and cost-effective workloads in the cloud.

It demonstrates a way to consistently measure your architectures against best practices and identify areas for improvement.

We believe that having well-architected workloads greatly increases the likelihood of business success.

The framework is based on five pillars:

Operational Excellence

Security

Reliability

Performance Efficiency

Cost Optimization

This paper focuses on the cost optimization pillar, and how to architect workloads with the most effective use of services and resources, to achieve business outcomes at the lowest price point.

You’ll learn how to apply the best practices of the cost optimization pillar within your organization.

Cost optimization can be challenging in traditional on-premises solutions because you must predict future capacity and business needs while navigating complex procurement processes.

Adopting the practices in this paper will help your organization achieve the following goals:

Practice Cloud Financial Management

Expenditure and usage awareness

Cost effective resources

Manage demand and supply resources

Optimize over time

Performance Efficiency Pillar AWS Well-Architected Framework. AGPIAL Audiobook 

https://amzn.to/2VKRZpz(paid link) 

As an Amazon Associate I earn from qualifying purchases.  

Thank you.  

Abstract.

This whitepaper focuses on the performance efficiency pillar of the AWS Well-Architected Framework.

It provides guidance to help customers apply best practices in the design, delivery, and maintenance of AWS environments.

The performance efficiency pillar addresses best practices for managing production environments.

This paper does not cover the design and management of non-production environments and processes, such as continuous integration or delivery.

Introduction.

The AWS Well-Architected Framework helps you understand the pros and cons of decisions you make while building workloads on AWS.

Using the Framework helps you learn architectural best practices for designing and operating reliable, secure, efficient, and cost-effective workloads in the cloud.

The Framework provides a way for you to consistently measure your architectures against best practices and identify areas for improvement.

We believe that having well-architected workloads greatly increases the likelihood of business success.

The framework is based on five pillars:

Operational Excellence

Security

Reliability

Performance Efficiency

Cost Optimization This paper focuses on applying the principles of the performance efficiency pillar to your workloads.

In traditional, on-premises environments, achieving high and lasting performance is challenging.

Using the principles in this paper will help you build architectures on AWS that efficiently deliver sustained performance over time.

This paper is intended for those in technology roles, such as chief technology officers (CTOs), architects, developers, and operations team members.

After reading this paper, you’ll understand AWS best practices and strategies to use when designing a performant cloud architecture.

This paper does not provide implementation details or architectural patterns.

However, it does include references to appropriate resources.

Operational Excellence Pillar AWS Well-Architected Framework

https://amzn.to/394m8Ds

(paid link) As an Amazon Associate I earn from qualifying purchases.

Operational Excellence Pillar AWS Well-Architected Framework

Introduction.

The AWS Well-Architected Framework helps you understand the benefits and risks of decisions you make while building workloads on AWS.

By using the Framework you will learn operational and architectural best practices for designing and operating reliable, secure, efficient, and cost-effective workloads in the cloud.

It provides a way to consistently measure your operations and architectures against best practices and identify areas for improvement.

We believe that having Well-Architected workloads that are designed with operations in mind greatly increases the likelihood of business success.

The framework is based on five pillars:

Operational Excellence

Security

Reliability

Performance Efficiency

Cost Optimization This paper focuses on the operational excellence pillar and how to apply it as the foundation of your well-architected solutions.

Operational excellence is challenging to achieve in environments where operations is perceived as a function isolated and distinct from the lines of business and development teams that it supports.

By adopting the practices in this paper you can build architectures that provide insight to their status, are enabled for effective and efficient operation and event response, and can continue to improve and support your business goals.

This paper is intended for those in technology roles, such as chief technology officers (CTOs), architects, developers, and operations team members.

After reading this paper, you will understand AWS best practices and the strategies to use when designing cloud architectures for operational excellence.

This paper does not provide implementation details or architectural patterns.

However, it does include references to appropriate resources for this information.

The Scrum Guide.

The Definitive Guide to Scrum, The Rules of the Game.

Purpose of the Scrum Guide.

We developed Scrum in the early 1990s.

We wrote the first version of the Scrum Guide in 2010 to help people worldwide understand Scrum.

We have evolved the Guide since then through small, functional updates.

Together, we stand behind it.

The Scrum Guide contains the definition of Scrum.

Each element of the framework serves a specific purpose that is essential to the overall value and results realized with Scrum.

Changing the core design or ideas of Scrum, leaving out elements, or not following the rules of Scrum, covers up problems and limits the benefits of Scrum, potentially even rendering it useless.

We follow the growing use of Scrum within an ever-growing complex world.

We are humbled to see Scrum being adopted in many domains holding essentially complex work, beyond software product development where Scrum has its roots.

As Scrum’s use spreads, developers, researchers, analysts, scientists, and other specialists do the work.

We use the word “developers” in Scrum not to exclude, but to simplify.

If you get value from Scrum, consider yourself included.

As Scrum is being used, patterns, processes, and insights that fit the Scrum framework as described in this document, may be found, applied and devised.

Their description is beyond the purpose of the Scrum Guide because they are context sensitive and differ widely between Scrum uses.

Such tactics for using within the Scrum framework vary widely and are described elsewhere.

Ken Schwaber & Jeff Sutherland November 2020