This document discusses Broadridge's use of AWS serverless technologies like AWS Lambda and Amazon API Gateway to build their Experience Manager application. It provides an overview of Broadridge, describes the problem of migrating essential communications from physical to digital, and how the Experience Manager solution leverages AWS services. It then covers benefits Broadridge realized by moving to AWS, including faster deployments, usage-based pricing, and automated key rotation.
6. Business to IT IT to Business
Changing the conversation
In a world of unprecedented market disruption
Business expects a different conversation from IT
IT Supplier Business Enabler
When will infrastructure be ready?
Can we have another environments?
When will you deliver x capability?
How will you reduce budget by XX% ?
Feel free to start building what you need
Here is a new security API you can use
Here are the results of a pilot we ran
And by the way, we cut your costs by X
8. Accelerated development lifecycle and product iterations
Create new data models and get real time insights
Deliver new capabilities to your customers
developers customers
releasetestbuild
plan monitor
feedback loop
automation
Increasing velocity of the dev teams
10. • Faster provisioning
time
• Limited “self service”
• Other benefits…
• Improved uptime
• Better utilization
• Hardware
independence
• On-demand
provisioning
• Automation (CI/CD)
• Other benefits…
• Elasticity
• High availability and
fault tolerance
• Global reach
• Opex vs. Capex
• Distributed
architectures
• Modern languages
Each progressive step was better
Physical Servers
in Datacenters
Virtual Servers
in Datacenters
Virtual Servers
in the Cloud
11. What size servers are right
for my budget?
How many users create too
much load for my servers?
How much remaining capacity
do my servers have?
How can I detect if a server
has been compromised?
How many servers
should I budget for?
Which OS should my
servers run?
Which users should have
access to my servers?
How can I control access from
my servers?
How will I keep my server
OS patched?
How will new code be
deployed to my servers?
How can I increase
utilization of my servers?
When should I decide to
scale out my servers?
What size server is
right for my performance?
Should I tune OS settings
to optimize my application?
Which packages should be
baked into my server images?
When should I decide to
scale up my servers?
How should I handle server
configuration changes?
How will the application handle
server hardware failure?
But they are still servers…
12. Fully managed
• No provisioning
• No patching
• High availability
Developer productivity
• Focus on the code that matters
• Innovate rapidly
• Reduce time to market
Continuous scaling
• Automatically
• Scale up and scale down
What is Serverless?