Everything fails all the time. Knowing how to deal with these failures in serverless applications becomes essential to building resilient, highly-available systems. In traditional monolithic applications, catching errors and handling retries is relatively straightforward. But as our systems become more distributed, we now have multiple (often asynchronous) components processing events from several sources, all with vastly different retry behaviors and failure mechanisms. Utilizing old patterns can cause errors to get swallowed, creating brittle, unreliable systems that are difficult to debug and hard to maintain.
In this talk, we’ll explore the built-in tools and processes that AWS has in place to appropriately deal with failures in distributed serverless applications.
Building resilient serverless systems with non serverless componentsJeremy Daly
Serverless functions (like AWS Lambda, Google Cloud Functions, and Azure Functions) have the ability to scale almost infinitely to handle massive workload spikes. While this is a great solution for compute, it can be a MAJOR PROBLEM for other downstream resources like RDBMS, third-party APIs, legacy systems, and even most managed services hosted by your cloud provider. Whether you’re maxing out database connections, exceeding API quotas, or simply flooding a system with too many requests at once, serverless functions can DDoS your components and potentially take down your application. In this talk, we’ll discuss strategies and architectural patterns to create highly resilient serverless applications that can mitigate and alleviate pressure on “non-serverless” downstream systems during peak load times.
Building resilient serverless systems with non-serverless components (Belfast)Jeremy Daly
Serverless functions have the ability to scale almost infinitely. While great for compute, it can be a MAJOR PROBLEM for other downstream resources. In this talk, we'll discuss strategies and patterns to create highly resilient serverless apps that mitigate pressure on "non-serverless" systems.
Building resilient serverless systems with non-serverless components - Server...Jeremy Daly
Serverless functions (like AWS Lambda, Google Cloud Functions, and Azure Functions) have the ability to scale almost infinitely to handle massive workload spikes. While this is a great solution for compute, it can be a MAJOR PROBLEM for other downstream resources like RDBMS, third-party APIs, legacy systems, and even most managed services hosted by your cloud provider. Whether you’re maxing out database connections, exceeding API quotas, or simply flooding a system with too many requests at once, serverless functions can DDoS your components and potentially take down your application. In this talk, we’ll discuss strategies and architectural patterns to create highly resilient serverless applications that can mitigate and alleviate pressure on “non-serverless” downstream systems during peak load times.
Building resilient serverless systems with non-serverless components - Cardif...Jeremy Daly
Serverless functions have the ability to scale almost infinitely. While great for compute, it can be a MAJOR PROBLEM for other downstream resources. In this talk, we'll discuss strategies and patterns to create highly resilient serverless apps that mitigate pressure on "non-serverless" systems.
Building Resilient Serverless Systems with Non-Serverless ComponentsJeremy Daly
Serverless functions (like AWS Lambda, Google Cloud Functions, and Azure Functions) have the ability to scale almost infinitely to handle massive workload spikes. While this is a great solution to compute, it can be a MAJOR PROBLEM for other downstream resources like RDBMS, third-party APIs, legacy systems, and even most managed services hosted by your cloud provider. Whether you’re maxing out database connections, exceeding API quotas, or simply flooding a system with too many requests at once, serverless functions can DDoS your components and potentially take down your application. In this talk, we’ll discuss strategies and architectural patterns to create highly resilient serverless applications that can mitigate and alleviate pressure on non-serverless downstream systems during peak load times.
Serverless Microservice Patterns for AWSJeremy Daly
Serverless gives us the power to focus on writing code without worrying about the provisioning and ongoing maintenance of the underlying compute resources. Cloud providers (like AWS) also give us a huge number of managed services that we can stitch together to create incredibly powerful and massively scalable serverless microservices. This talk focuses on common design patterns that can be used to implement serverless microservices in AWS.
Building Event-Driven Applications with Serverless and AWS - AWS Summit New YorkJeremy Daly
Serverless enables us to develop applications that scale quickly and reliably based on incoming requests. These requests are often in the form of events that go well beyond API Gateway requests and scheduled rules in CloudWatch. In this Dev Chat, we’ll explore the different types of events available to your serverless applications, where they come from, and how to utilize them to build powerful applications that can automate business processes and provide more value to your customers.
Serverless Security: Best practices and mitigation strategies (re:Inforce 2019)Jeremy Daly
There are many inherent security benefits of using serverless (like no more patching servers or allowing direct network access to functions), but it does introduce additional complexities in how we build, deploy, and secure our applications. In this talk, we'll introduce several serverless security best practices, look at some common attack vectors, and discuss how we can apply them to increase our overall security posture. Special thanks to Ory Segal for content collaboration.
Building resilient serverless systems with non serverless componentsJeremy Daly
Serverless functions (like AWS Lambda, Google Cloud Functions, and Azure Functions) have the ability to scale almost infinitely to handle massive workload spikes. While this is a great solution for compute, it can be a MAJOR PROBLEM for other downstream resources like RDBMS, third-party APIs, legacy systems, and even most managed services hosted by your cloud provider. Whether you’re maxing out database connections, exceeding API quotas, or simply flooding a system with too many requests at once, serverless functions can DDoS your components and potentially take down your application. In this talk, we’ll discuss strategies and architectural patterns to create highly resilient serverless applications that can mitigate and alleviate pressure on “non-serverless” downstream systems during peak load times.
Building resilient serverless systems with non-serverless components (Belfast)Jeremy Daly
Serverless functions have the ability to scale almost infinitely. While great for compute, it can be a MAJOR PROBLEM for other downstream resources. In this talk, we'll discuss strategies and patterns to create highly resilient serverless apps that mitigate pressure on "non-serverless" systems.
Building resilient serverless systems with non-serverless components - Server...Jeremy Daly
Serverless functions (like AWS Lambda, Google Cloud Functions, and Azure Functions) have the ability to scale almost infinitely to handle massive workload spikes. While this is a great solution for compute, it can be a MAJOR PROBLEM for other downstream resources like RDBMS, third-party APIs, legacy systems, and even most managed services hosted by your cloud provider. Whether you’re maxing out database connections, exceeding API quotas, or simply flooding a system with too many requests at once, serverless functions can DDoS your components and potentially take down your application. In this talk, we’ll discuss strategies and architectural patterns to create highly resilient serverless applications that can mitigate and alleviate pressure on “non-serverless” downstream systems during peak load times.
Building resilient serverless systems with non-serverless components - Cardif...Jeremy Daly
Serverless functions have the ability to scale almost infinitely. While great for compute, it can be a MAJOR PROBLEM for other downstream resources. In this talk, we'll discuss strategies and patterns to create highly resilient serverless apps that mitigate pressure on "non-serverless" systems.
Building Resilient Serverless Systems with Non-Serverless ComponentsJeremy Daly
Serverless functions (like AWS Lambda, Google Cloud Functions, and Azure Functions) have the ability to scale almost infinitely to handle massive workload spikes. While this is a great solution to compute, it can be a MAJOR PROBLEM for other downstream resources like RDBMS, third-party APIs, legacy systems, and even most managed services hosted by your cloud provider. Whether you’re maxing out database connections, exceeding API quotas, or simply flooding a system with too many requests at once, serverless functions can DDoS your components and potentially take down your application. In this talk, we’ll discuss strategies and architectural patterns to create highly resilient serverless applications that can mitigate and alleviate pressure on non-serverless downstream systems during peak load times.
Serverless Microservice Patterns for AWSJeremy Daly
Serverless gives us the power to focus on writing code without worrying about the provisioning and ongoing maintenance of the underlying compute resources. Cloud providers (like AWS) also give us a huge number of managed services that we can stitch together to create incredibly powerful and massively scalable serverless microservices. This talk focuses on common design patterns that can be used to implement serverless microservices in AWS.
Building Event-Driven Applications with Serverless and AWS - AWS Summit New YorkJeremy Daly
Serverless enables us to develop applications that scale quickly and reliably based on incoming requests. These requests are often in the form of events that go well beyond API Gateway requests and scheduled rules in CloudWatch. In this Dev Chat, we’ll explore the different types of events available to your serverless applications, where they come from, and how to utilize them to build powerful applications that can automate business processes and provide more value to your customers.
Serverless Security: Best practices and mitigation strategies (re:Inforce 2019)Jeremy Daly
There are many inherent security benefits of using serverless (like no more patching servers or allowing direct network access to functions), but it does introduce additional complexities in how we build, deploy, and secure our applications. In this talk, we'll introduce several serverless security best practices, look at some common attack vectors, and discuss how we can apply them to increase our overall security posture. Special thanks to Ory Segal for content collaboration.
Everything fails all the time! A quote repeated by many everyday. How does it feel when things fail in production? How do you recover from such situations? How can you make sure they don’t repeat? All these discussed with real production incidents and the measures taken to mitigate such failures. We will also look at few of the most common failure possibilities in a serverless ecosystem.
Remember, when everything fails all the time, you must learn something everyday to be operational all the time!
Stephen Liedig: Building Serverless Backends with AWS Lambda and API GatewaySteve Androulakis
Stephen Liedig (Amazon Web Services) is a Public Sector Solutions Architect at AWS working closely with local and state governments, educational institutions, and non-profit organisations across Australia and New Zealand to design, and deliver, highly secure, scalable, reliable and fault-tolerant architectures in the AWS Cloud while sharing best practices and current trends, with a specific focus on DevOps, messaging, and serverless technologies.
Serverless architectures let you build and deploy applications and services with infrastructure resources that require zero administration. In the past, you had to provision and scale servers to run your application code, install and operate distributed databases, and build and run custom software to handle API requests. Now, AWS provides a stack of scalable, fully-managed services that eliminates these operational complexities.
In this session, you will learn about the benefits of serverless architectures and the basics of the serverless stack AWS provides. We will also walk through how you can use serverless architectures for everything from data processing to mobile and web backends.
AWS DevDay San Francisco, June 21, 2016.
Presenter: Jeremy Edberg, Co-Founder, CloudNative, & AWS Community Hero
Choosing the right messaging service for your serverless app [with lumigo]Dhaval Nagar
By their nature, serverless applications are highly-distributed and event-driven, relying heavily on relaying events from one service to another. With that in mind, selecting the right messaging service for routing events is critical for your serverless application's functionality and performance.
I reviewed the three major event-routing services on AWS -- SNS, SQS, and EventBridge. Also, examine their differences and which service is optimal for which use case.
Finally, looked at the best way to monitor and debug a serverless application that uses an event-routing messaging service
Serverless needs no introduction these days. It is viewed as a magic recipe for organisations moving to cloud and for those moving beyond the container hell.
LEGO.com was migrated from a legacy monolith eCommerce platform onto serverless on AWS. This employed serverless and managed services at its core within an agile development process. Is early success with serverless a springboard to future possibilities? Does serverless really deliver what it promises?
We will look at how serverless helped in the migration and what can it do to the organisation beyond its initial adoption!
ENT310 Microservices? Dynamic Infrastructure? - Adventures in Keeping Your Ap...Amazon Web Services
Keeping an application running at scale can be a daunting task. When do you need to add more capacity? Larger databases? Additional servers? These questions get harder as the complexity of your application grows. Microservice based architectures and cloud-based dynamic infrastructures are technologies that help you keep your application running with high availability, even during times of extreme scaling. We will discuss some of the best practices we’ve learned working with New Relic customers on how you can manage your applications running at scale, and how technologies such as microservices and dynamic infrastructure can help you with this challenge. This session is brought to you by AWS Summit San Francisco Platinum Sponsor New Relic.
Enterprise Serverless Adoption. An Experience ReportSheenBrisals
The adoption of Serverless is growing in the industry. However, its adoption in larger enterprises is somewhat slow compared to start-ups and individual developers. This talk tells an enterprise adoption success story and shares insights into the secrets behind its success!
Using AWS Lambda to Build Control Systems for Your AWS InfrastructureAmazon Web Services
Defining infrastructure resource policies in an organized manner can help your company better manage its infrastructure resources.
This session will familiarize you with using AWS Lambda to process data and provide control logic for your infrastructure. You can use Amazon CloudWatch Events to monitor infrastructure resources in real-time, and you can use AWS Lambda to react to events based on a set of rules. We will demonstrate how you can build a rules engine for creating, monitoring, and managing policies.
AWS DevDay San Francisco, June 21, 2016.
Presenter: Bryan Liston, Community Manager, AWS Lambda
WKS404 7 Things You Must Know to Build Better Alexa SkillsAmazon Web Services
As we add thousands of skills to the skills store our developers have uncovered some basic and more complex tips for building better skills. Whether you are new to Alexa Skill development or if you have created skills that are live today, this session will help you understand and learn best practices. During this session, you’ll build an Alexa skill using more advanced VUI concepts and we’ll cover how to use AWS services like dynamoDB and S3 to implement the best practices we cover.
Thinking Asynchronously Full Vesion - Utah UGEric Johnson
Speed matters, and developers are challenged to reduce latency in their applications at every turn. In traditional synchronous programming patterns, users are asked to monitor the spinning wheel as the application moves from one task to the next until a response can be returned. However, developers can reclaim these precious milliseconds by learning to think asynchronously. Asynchronous patterns challenge developers to evaluate what tasks require the client to wait versus what can be done after the fact. When developing serverless applications on AWS this process is made easier by the asynchronous and polling patterns that are native to AWS Lambda.
In this session I will demonstrate taking an existing translation application that is synchronous and modifying it to use asynchronous patterns. This will be accomplished using Amazon DynamoDB Streams and the recently released Amazon EventBridge.
Since AWS launched Lambda in 2014, the term “serverless” has been used (and misused) to describe compute models, technologies, architectural patterns, operational constructs, and even rebranded cgi-bins. The term is now used so broadly that it’s turning into a buzzword with no discernible meaning.
In this talk, we’ll cut through all the marketing hype, and discuss why the underlying concept of “serverless”, and the superpowers that come with it, are much more important than the name itself.
CQRS (Command Query Responsibility Segregation) was all the hype in .NET architecture circles a few years back. But has it faded away? Is it old news? I argue that it hasn't, and the concepts of CQRS are alive and well and probably more widely accepted and considered today than a few years ago. From event-driven systems to the Reactive Manifesto, the principles of CQRS are with us and impacting many different tools. In this session, we'll explore those CQRS principles and how they have manifested themselves in the architectures of choice today. You'll come away with a greater appreciation of CQRS and ideas on how to incorporate those principles in your applications today.
Serverless architectures are promising and will play an important role in the coming years but the ecosystem around serverless is still pretty young. We have been operating Lambda based applications for about a year and faced several challenges. In this presentation we share these challenges and propose some solutions to work around them.
Everything fails all the time! A quote repeated by many everyday. How does it feel when things fail in production? How do you recover from such situations? How can you make sure they don’t repeat? All these discussed with real production incidents and the measures taken to mitigate such failures. We will also look at few of the most common failure possibilities in a serverless ecosystem.
Remember, when everything fails all the time, you must learn something everyday to be operational all the time!
Stephen Liedig: Building Serverless Backends with AWS Lambda and API GatewaySteve Androulakis
Stephen Liedig (Amazon Web Services) is a Public Sector Solutions Architect at AWS working closely with local and state governments, educational institutions, and non-profit organisations across Australia and New Zealand to design, and deliver, highly secure, scalable, reliable and fault-tolerant architectures in the AWS Cloud while sharing best practices and current trends, with a specific focus on DevOps, messaging, and serverless technologies.
Serverless architectures let you build and deploy applications and services with infrastructure resources that require zero administration. In the past, you had to provision and scale servers to run your application code, install and operate distributed databases, and build and run custom software to handle API requests. Now, AWS provides a stack of scalable, fully-managed services that eliminates these operational complexities.
In this session, you will learn about the benefits of serverless architectures and the basics of the serverless stack AWS provides. We will also walk through how you can use serverless architectures for everything from data processing to mobile and web backends.
AWS DevDay San Francisco, June 21, 2016.
Presenter: Jeremy Edberg, Co-Founder, CloudNative, & AWS Community Hero
Choosing the right messaging service for your serverless app [with lumigo]Dhaval Nagar
By their nature, serverless applications are highly-distributed and event-driven, relying heavily on relaying events from one service to another. With that in mind, selecting the right messaging service for routing events is critical for your serverless application's functionality and performance.
I reviewed the three major event-routing services on AWS -- SNS, SQS, and EventBridge. Also, examine their differences and which service is optimal for which use case.
Finally, looked at the best way to monitor and debug a serverless application that uses an event-routing messaging service
Serverless needs no introduction these days. It is viewed as a magic recipe for organisations moving to cloud and for those moving beyond the container hell.
LEGO.com was migrated from a legacy monolith eCommerce platform onto serverless on AWS. This employed serverless and managed services at its core within an agile development process. Is early success with serverless a springboard to future possibilities? Does serverless really deliver what it promises?
We will look at how serverless helped in the migration and what can it do to the organisation beyond its initial adoption!
ENT310 Microservices? Dynamic Infrastructure? - Adventures in Keeping Your Ap...Amazon Web Services
Keeping an application running at scale can be a daunting task. When do you need to add more capacity? Larger databases? Additional servers? These questions get harder as the complexity of your application grows. Microservice based architectures and cloud-based dynamic infrastructures are technologies that help you keep your application running with high availability, even during times of extreme scaling. We will discuss some of the best practices we’ve learned working with New Relic customers on how you can manage your applications running at scale, and how technologies such as microservices and dynamic infrastructure can help you with this challenge. This session is brought to you by AWS Summit San Francisco Platinum Sponsor New Relic.
Enterprise Serverless Adoption. An Experience ReportSheenBrisals
The adoption of Serverless is growing in the industry. However, its adoption in larger enterprises is somewhat slow compared to start-ups and individual developers. This talk tells an enterprise adoption success story and shares insights into the secrets behind its success!
Using AWS Lambda to Build Control Systems for Your AWS InfrastructureAmazon Web Services
Defining infrastructure resource policies in an organized manner can help your company better manage its infrastructure resources.
This session will familiarize you with using AWS Lambda to process data and provide control logic for your infrastructure. You can use Amazon CloudWatch Events to monitor infrastructure resources in real-time, and you can use AWS Lambda to react to events based on a set of rules. We will demonstrate how you can build a rules engine for creating, monitoring, and managing policies.
AWS DevDay San Francisco, June 21, 2016.
Presenter: Bryan Liston, Community Manager, AWS Lambda
WKS404 7 Things You Must Know to Build Better Alexa SkillsAmazon Web Services
As we add thousands of skills to the skills store our developers have uncovered some basic and more complex tips for building better skills. Whether you are new to Alexa Skill development or if you have created skills that are live today, this session will help you understand and learn best practices. During this session, you’ll build an Alexa skill using more advanced VUI concepts and we’ll cover how to use AWS services like dynamoDB and S3 to implement the best practices we cover.
Thinking Asynchronously Full Vesion - Utah UGEric Johnson
Speed matters, and developers are challenged to reduce latency in their applications at every turn. In traditional synchronous programming patterns, users are asked to monitor the spinning wheel as the application moves from one task to the next until a response can be returned. However, developers can reclaim these precious milliseconds by learning to think asynchronously. Asynchronous patterns challenge developers to evaluate what tasks require the client to wait versus what can be done after the fact. When developing serverless applications on AWS this process is made easier by the asynchronous and polling patterns that are native to AWS Lambda.
In this session I will demonstrate taking an existing translation application that is synchronous and modifying it to use asynchronous patterns. This will be accomplished using Amazon DynamoDB Streams and the recently released Amazon EventBridge.
Since AWS launched Lambda in 2014, the term “serverless” has been used (and misused) to describe compute models, technologies, architectural patterns, operational constructs, and even rebranded cgi-bins. The term is now used so broadly that it’s turning into a buzzword with no discernible meaning.
In this talk, we’ll cut through all the marketing hype, and discuss why the underlying concept of “serverless”, and the superpowers that come with it, are much more important than the name itself.
CQRS (Command Query Responsibility Segregation) was all the hype in .NET architecture circles a few years back. But has it faded away? Is it old news? I argue that it hasn't, and the concepts of CQRS are alive and well and probably more widely accepted and considered today than a few years ago. From event-driven systems to the Reactive Manifesto, the principles of CQRS are with us and impacting many different tools. In this session, we'll explore those CQRS principles and how they have manifested themselves in the architectures of choice today. You'll come away with a greater appreciation of CQRS and ideas on how to incorporate those principles in your applications today.
Serverless architectures are promising and will play an important role in the coming years but the ecosystem around serverless is still pretty young. We have been operating Lambda based applications for about a year and faced several challenges. In this presentation we share these challenges and propose some solutions to work around them.
this is the slides from the talk i gave at DevGeekWeek2014
further details are in my blog: http://blogs.microsoft.co.il/iblogger/2014/06/25/devgeekweek-2014-slides-and-demos/
This webinar by Orkhan Gasimov (Senior Solution Architect, Consultant, GlobalLogic) was delivered at Java Community Webinar #3 on October 16, 2020.
During webinar we had simplified overview of classical and modern architecture patterns and concepts that are used for development of distributed applications during the last decade.
More details and presentation: https://www.globallogic.com/ua/about/events/java-community-webinar-3/
- My presentation in faculty of computers and artficial intelligence, cairo university on Serverless Computing model
- And How to migrate your application to serverless computing model and to a cloud service like AWS that serves that serverless model
Site reliability in the Serverless age - Serverless Boston 2019Erik Peterson
Is SRE, DevOps and serverless a match made in heaven or is something missing? What about cost when building reliable Serverless systems? To answer this, lets explore SRE and Serverless principals, a new concept called FinDevOps, and along the way make a few predictions about our serverless future
Unless you have a problem which scales to many independent tasks easily e.g. web services, you may find that the best way to improve throughput is by reducing latency. This talk starts with Little's Law and it's consequences for high performance computing.
Reliability of the Cloud: How AWS Achieves High Availability (ARC317-R1) - AW...Amazon Web Services
In this chalk talk, we explore the implementation details of achieving availability and reliability, as described in the whitepaper, AWS Well-Architected Framework - Reliability Pillar
7 Common Questions About a Cloud Management PlatformRightScale
You already know you need to deliver software more quickly. But what’s the best route to get that agility? Cloud, containers, and DevOps can all help, and a cloud management platform (CMP) pulls it all together. Get answers to the common questions about a CMP.
Communications Mining Series - Zero to Hero - Session 1DianaGray10
This session provides introduction to UiPath Communication Mining, importance and platform overview. You will acquire a good understand of the phases in Communication Mining as we go over the platform with you. Topics covered:
• Communication Mining Overview
• Why is it important?
• How can it help today’s business and the benefits
• Phases in Communication Mining
• Demo on Platform overview
• Q/A
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
UiPath Test Automation using UiPath Test Suite series, part 6DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 6. In this session, we will cover Test Automation with generative AI and Open AI.
UiPath Test Automation with generative AI and Open AI webinar offers an in-depth exploration of leveraging cutting-edge technologies for test automation within the UiPath platform. Attendees will delve into the integration of generative AI, a test automation solution, with Open AI advanced natural language processing capabilities.
Throughout the session, participants will discover how this synergy empowers testers to automate repetitive tasks, enhance testing accuracy, and expedite the software testing life cycle. Topics covered include the seamless integration process, practical use cases, and the benefits of harnessing AI-driven automation for UiPath testing initiatives. By attending this webinar, testers, and automation professionals can gain valuable insights into harnessing the power of AI to optimize their test automation workflows within the UiPath ecosystem, ultimately driving efficiency and quality in software development processes.
What will you get from this session?
1. Insights into integrating generative AI.
2. Understanding how this integration enhances test automation within the UiPath platform
3. Practical demonstrations
4. Exploration of real-world use cases illustrating the benefits of AI-driven test automation for UiPath
Topics covered:
What is generative AI
Test Automation with generative AI and Open AI.
UiPath integration with generative AI
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Generative AI Deep Dive: Advancing from Proof of Concept to ProductionAggregage
Join Maher Hanafi, VP of Engineering at Betterworks, in this new session where he'll share a practical framework to transform Gen AI prototypes into impactful products! He'll delve into the complexities of data collection and management, model selection and optimization, and ensuring security, scalability, and responsible use.
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
A tale of scale & speed: How the US Navy is enabling software delivery from l...sonjaschweigert1
Rapid and secure feature delivery is a goal across every application team and every branch of the DoD. The Navy’s DevSecOps platform, Party Barge, has achieved:
- Reduction in onboarding time from 5 weeks to 1 day
- Improved developer experience and productivity through actionable findings and reduction of false positives
- Maintenance of superior security standards and inherent policy enforcement with Authorization to Operate (ATO)
Development teams can ship efficiently and ensure applications are cyber ready for Navy Authorizing Officials (AOs). In this webinar, Sigma Defense and Anchore will give attendees a look behind the scenes and demo secure pipeline automation and security artifacts that speed up application ATO and time to production.
We will cover:
- How to remove silos in DevSecOps
- How to build efficient development pipeline roles and component templates
- How to deliver security artifacts that matter for ATO’s (SBOMs, vulnerability reports, and policy evidence)
- How to streamline operations with automated policy checks on container images
20 Comprehensive Checklist of Designing and Developing a WebsitePixlogix Infotech
Dive into the world of Website Designing and Developing with Pixlogix! Looking to create a stunning online presence? Look no further! Our comprehensive checklist covers everything you need to know to craft a website that stands out. From user-friendly design to seamless functionality, we've got you covered. Don't miss out on this invaluable resource! Check out our checklist now at Pixlogix and start your journey towards a captivating online presence today.
Alt. GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using ...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Observability Concepts EVERY Developer Should Know -- DeveloperWeek Europe.pdfPaige Cruz
Monitoring and observability aren’t traditionally found in software curriculums and many of us cobble this knowledge together from whatever vendor or ecosystem we were first introduced to and whatever is a part of your current company’s observability stack.
While the dev and ops silo continues to crumble….many organizations still relegate monitoring & observability as the purview of ops, infra and SRE teams. This is a mistake - achieving a highly observable system requires collaboration up and down the stack.
I, a former op, would like to extend an invitation to all application developers to join the observability party will share these foundational concepts to build on:
LF Energy Webinar: Electrical Grid Modelling and Simulation Through PowSyBl -...DanBrown980551
Do you want to learn how to model and simulate an electrical network from scratch in under an hour?
Then welcome to this PowSyBl workshop, hosted by Rte, the French Transmission System Operator (TSO)!
During the webinar, you will discover the PowSyBl ecosystem as well as handle and study an electrical network through an interactive Python notebook.
PowSyBl is an open source project hosted by LF Energy, which offers a comprehensive set of features for electrical grid modelling and simulation. Among other advanced features, PowSyBl provides:
- A fully editable and extendable library for grid component modelling;
- Visualization tools to display your network;
- Grid simulation tools, such as power flows, security analyses (with or without remedial actions) and sensitivity analyses;
The framework is mostly written in Java, with a Python binding so that Python developers can access PowSyBl functionalities as well.
What you will learn during the webinar:
- For beginners: discover PowSyBl's functionalities through a quick general presentation and the notebook, without needing any expert coding skills;
- For advanced developers: master the skills to efficiently apply PowSyBl functionalities to your real-world scenarios.
DevOps and Testing slides at DASA ConnectKari Kakkonen
My and Rik Marselis slides at 30.5.2024 DASA Connect conference. We discuss about what is testing, then what is agile testing and finally what is Testing in DevOps. Finally we had lovely workshop with the participants trying to find out different ways to think about quality and testing in different parts of the DevOps infinity loop.
Pushing the limits of ePRTC: 100ns holdover for 100 daysAdtran
At WSTS 2024, Alon Stern explored the topic of parametric holdover and explained how recent research findings can be implemented in real-world PNT networks to achieve 100 nanoseconds of accuracy for up to 100 days.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
How to Get CNIC Information System with Paksim Ga.pptxdanishmna97
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
How to Get CNIC Information System with Paksim Ga.pptx
How to fail with serverless
1. How to Fail with Serverless
Jeremy Daly
CTO, AlertMe.news
@jeremy_daly
2. Jeremy Daly
• CTO at AlertMe.news
• Consult with companies building in the cloud
• 20+ year veteran of technology startups
• Started working with AWS in 2009 and started using
Lambda in 2015
• Blogger (jeremydaly.com), OSS contributor, speaker
• Publish the Off-by-none serverless newsletter
• Host of the Serverless Chats podcast
@jeremy_daly
3. Agenda
• Distributed systems and serverless
• Writing code FOR the cloud
• Failure modes in the cloud
• Serverless patterns to deal with failure
• Decoupling our services
@jeremy_daly
4. Distributed Systems are…
Systems whose components are located on
different networked computers, which communicate
and coordinate their actions by passing messages to
one another. ~Wikipedia
@jeremy_daly
They’re also really hard!
6. 8 Fallacies of Distributed Computing
@jeremy_daly
The network
is reliable
Latency
is zero
Bandwidth
is infinite
The network is
secure
Topology
doesn’t change
There is one
administrator
Transport cost
is zero
The network is
homogeneous
🚫 🚫 🚫 🚫
🚫 🚫 🚫 🚫
7. Serverless applications are…
Distributed systems on steroids! 💪 💪 💪
@jeremy_daly
• Smaller, more distributed compute units
• Stateless, requiring network access to state
• Uncoordinated, requires buses, queues, pub/sub, state machines
• Heavily reliant on other networked cloud services
8. What does it mean to be Serverless?
• No server management
• Flexible scaling
• Pay for value / never pay for idle
• Automated high availability
• LOTS of configuration and knowledge of cloud services
• Highly event-driven
@jeremy_daly
9. Lots of services to communicate with!
@jeremy_daly
ElastiCache
RDS
EMR Amazon ES
Redshift
Fargate
Anything “on EC2”Lambda Cognito Kinesis
S3 DynamoDB SQS
SNS API Gateway
AppSync IoT Comprehend
“Serverless” Managed Non-Serverless
DocumentDB
(MongoDB)
Managed Streaming
for Kada
EventBridge
10. Reliability or High Availability is…
@jeremy_daly
A characteristic of a system, which aims to ensure an
agreed level of operational performance,
usually uptime, for a higher than normal period.
~Wikipedia
11. Resiliency is…
@jeremy_daly
The ability of a software solution to absorb the impact
of a problem in one or more parts of a system, while
continuing to provide an acceptable service level to
the business. ~ IBM
IT’S NOT ABOUT PREVENTING FAILURE
IT’S UNDERSTANDING HOWTO GRACEFULLY DEAL WITH IT
13. Using Lambda for our business logic
• Ephemeral compute service
• Runs your code in response to events
• Automatically manages the runtime,
compute, and scaling
• Single concurrency model
• No sticky-sessions or guaranteed
lifespan
@jeremy_daly
14. Traditional Error Handling & Retries
try {
// Do something important
} catch (err) {
// Do some error handling
// Do some logging
// Maybe retry the operation
}
@jeremy_daly
What happens to the
original event?
What happens if the function
container crashes?
What happens if there is a
network issue?
👨✈ Losing events is very bad!
What happens if the function
never runs?
16. The cloud is better than you…
…at error handling
…at retrying failures
…at understanding network failures
…at mapping the network topology
…at handling failover and redundancy
@jeremy_daly
So why not let the
cloud do those
things for you? 🤷
17. Fail up the stack
• Don’t swallow errors with try/catch – fail the function
• Return errors directly to the invoking service
• Configure built-in retry mechanisms to reprocess events
• Utilize dead letter queues to capture failed events
@jeremy_daly
(sometimes 😉)
18. Types of Lambda Functions
• The Lambdalith
• The Fat Lambda
• The Single-Purpose Function
@jeremy_daly
😬
🤔
👍
19. The Mighty Lambdalith
• The entire application is in one
Lambda function
• Often times these are “lift and
shift” Express.js or Flask apps
• Events are synchronous via API
Gateway or ALB
• Partial failures are handled “in the
code”
@jeremy_daly
20. The Fat Lambda
• Several related methods are collocated in a single Lambda function
• Generally used to optimize the speed of synchronous operations
• Partial failures are still handled “in the code”
• Under the right circumstances, this can be useful
@jeremy_daly
21. The Single-Purpose Function
• Tightly scoped function that handles a single discrete piece of
business logic
• Can be invoked synchronously or asynchronously
• Failures are generally “total failures” and are passed back to the
invoking service
• Can be reused as part of other “workflows”, can scale (or throttle)
independently, and can utilize the Principle of Least Privilege
@jeremy_daly
22. Failure Modes in the Cloud
WARNING: Firehose of overly-technical content ahead 👩🚒
23. A quick word about retries…
• Retries are a vital part of distributed systems
• Most cloud services guarantee “at least once” delivery
• It is possible for the same event to be received more than once
• Retried operations should be idempotent
@jeremy_daly
24. Idempotent means that…
An operation can be repeated multiple times and
always provide the same result, with no side effects
to other objects in the system. ~ Computer Hope
@jeremy_daly
Idempotent operations:
• Update a database record
• Authenticate a user
• Check if a record exists and create if not
There are lots of
strategies to ensure
idempotency!
25. What are Dead Letter Queues (DLQs)?
• Capture messages/events that fail to process or are skipped
• Allows for alarming, inspection, and potential replay
• Can be added to SQS queues, SNS subscriptions, Lambda functions
@jeremy_daly
26. Lambda Invocation Types
• Synchronous – request/response model
• Asynchronous – set it and forget it
• Stream-based – push
• Poller-based – pull
@jeremy_daly
27. Synchronous Lambda Retry Behavior
• Functions are invoked directly using request/response method
• Failures are returned to the invoker
• Retries are delegated to the invoking application
• Some AWS services automatically retry (e.g. Alexa & Cognito)
• Other services do not retry (e.g. API Gateway, ALB, Step Functions)
• API Gateway and ALB can return errors to the client for retry
@jeremy_daly
28. Asynchronous Lambda Retry Behavior
• The Lambda Service accepts requests and adds them to a queue
• The invoker receives a 202 status code and disconnects
• The Lambda Service will attempt to reprocess failed events up to
2 times, configured using the MaximumRetryAttempts setting
• If the Lambda function is throttled, the event will be retried for up to
6 hours, configured using MaximumEventAgeInSeconds
• Failed and expired events can be sent to a Dead Letter Queue (DLQ)
or an on-failure destination
@jeremy_daly
29. Stream-based Lambda Retry Behavior
• Records are pushed synchronously to Lambda from Kinesis or
DynamoDB streams in batches (10k and 1k limits per batch)
• MaximumRetryAttempts: number of retry attempts for batches
before they can be skipped (up to 10,000)
• MaximumRecordAgeInSeconds: store records up to 7 days
• BisectBatchOnFunctionError: recursively split failed batches
(poison pill)
• Skipped records are sent to an On-failure Destination (SQS or SNS)
@jeremy_daly
30. Poller-based Lambda Retry Behavior
• The Lambda Poller pulls records synchronously from SQS in
batches (up to 10)
• Errors fail the entire batch
• MaxReceiveCount: number of times messages can be returned to
the queue before being sent to the DLQ (up to 1,000)
• Polling frequency is tied to function concurrency
• VisibilityTimeout should be set to at least 6 times the timeout
configured on your consuming function
@jeremy_daly
31. Lambda Destinations
• Only for asynchronous invocations
• Routing based on SUCCESS and/or FAILURE
• OnFailure should be favored over a standard DLQ
• Destinations can be an SQS queue, SNS topic,
Lambda function, or EventBridge event bus
@jeremy_daly
32. Lambda Destinations (continued)
Destination-specific JSON format
• SQS/SNS: JSON object is passed as the Message
• Lambda: JSON is passed as the payload to the function
• EventBridge: JSON is passed as the Detail in the PutEvents call
• Source is ”lambda”
• DetailType is “Lambda Function Invocation Result – Success/Failure”
• Resource fields contain the function and destination ARNs
@jeremy_daly
33. SQS Redrive Policies
• Only supports another SQS queue as the DLQ
• Messages are sent to the DLQ if the Maximum Receives value is
exceeded
@jeremy_daly
34. SNS Redrive Policies
• Dead Letter Queues are attached to Subscriptions, not Topics
• Only supports SQS queues as the DLQ
• Client-side errors (e.g. Lambda doesn’t exist) do no retry
• Messages to SQS or Lambda are retried 100,015 times over 23 days
• Messages to SMTP, SMS, and Mobile retry 50 times over 6 hours
• HTTP endpoints support customer-defined retry policies
(number of retries, delays, and backoff strategy)
@jeremy_daly
35. EventBridge Retry Behavior
• Will attempt to deliver events for up to 24 hours with backoff
• Lambda functions are invoked asynchronously
• Failed events are lost (this is very unlikely)
• Once events are accepted by the target service, failure modes of
those services are used
@jeremy_daly
36. Step Functions
• State Machines: Orchestration workflows
• Lambdas are invoked synchronously
• Retriers and Catchers allow for complex
error handling patterns
• Use “error names” with ErrorEquals for
condition error handling (States.*)
• Control retry policies with IntervalSeconds,
MaxAttempts, BackoffRate
@jeremy_daly
Complex Error Handling Pattern
Credit:Yan Cui
37. AWS SDK Retries
• Automatic retries and exponential backoff
@jeremy_daly
AWS SDK
Maximum retry
count
Connection
timeout
Socket timeout
Python (Boto 3) depends on service 60 seconds 60 seconds
Node.js depends on service N/A 120 seconds
Java 3 10 seconds 50 seconds
.NET 4 100 seconds 300 seconds
Go 3 N/A N/A
39. miss
Caching strategy
Client API Gateway RDSLambda
Elasticache
Key Points:
• Create new RDS connections ONLY on misses
• Make sureTTLs are set appropriately
• Include the ability to invalidate cache
@jeremy_daly
YOU STILL NEEDTO
SIZEYOUR DATABASE
CLUSTERS APPROPRIATELY
40. RDS
Buffer events for throttling and durability
Client API Gateway
SQS
Queue
SQS
(DLQ)
Lambda Lambda
(throttled)
ack
“Asynchronous”
Request
Synchronous
Request
@jeremy_daly
Key Points:
• SQS adds durability
• Throttled Lambdas reduce downstream pressure
• Failed events are stored for further inspection/replay
Limit the
concurrency to match
RDS throughput
x
Utilize Service
Integrations
41. DynamoDB
Stripe API
The Circuit Breaker
Client API Gateway Lambda
Key Points:
• Cache your cache with warm functions
• Use a reasonable failure count
• Understand idempotency!
Status
Check CLOSED
OPEN
Increment Failure Count
HALF OPEN
“Everything fails all the time.”
~WernerVogels
@jeremy_daly
Elasticache
or
44. Multicasting with SNS
Key Points:
• SNS has a “well-defined API”
• Decouples downstream processes
• Allows multiple subscribers with message filters
Client
SNS
“Asynchronous”
Request
ack
Event Service
@jeremy_daly
HTTP
SMS
Lambda
SQS
Email
SQS (DLQ)
45. @jeremy_daly
Multicasting with EventBridge
Key Points:
• Allows multiple subscribers with RULES, PATTERNS and FILTERS
• Forward events to other accounts
• 24 hours of automated retries
Asynchronous
“PutEvents” Request
ack
w/ event id
Amazon
EventBridge
Lambda
SQS
Client
Step Function
Event Bus
+16 others
46. Key Points:
• Filter events to selectively trigger services
• Manage throttling/quotas/failures per service
• Use Lambda Destinations with asynchronous events
Stripe API
@jeremy_daly
Distribute & Throttle
ack
SQS
Queue Lambda
(concurrency 25)
Client API
Gateway
Lambda
Order Service
"total": [{ "numeric": [ ”>", 0 ]}]
RDS
SQS
Queue Lambda
(concurrency 10)
SMS Alerting Service
Twilio API
SQS
Queue Lambda
(concurrency 5)
Billing Service
"detail-type": [ "ORDER COMPLETE" ]
EventBridge
47. Key Takeaways
• Be prepared for failure – everything fails all the time!
• Utilize the built in retry mechanisms of the cloud
• Understand failure modes to protect against data loss
• Buffer and throttle events to distributed systems
• Embrace asynchronous processes to decouple components
@jeremy_daly