The document discusses event-driven infrastructure and how infrastructure can react to different types of events. It describes how infrastructure as code tools like Puppet, Chef, and Ansible can be used to configure infrastructure. It also discusses how serverless architectures using AWS Lambda allow infrastructure to scale automatically in response to events with no administration. Finally, it considers how event-driven infrastructure affects operational practices for DevOps.
9. - Real
time
(or
near
real
time)
- Push
notifications
- One-‐way
‘fire-‐and-‐forget’
- Immediate
action
at
event
consumer
- Informational
(“monkey
took
bananas”)
and
not
commands
(“perform
banana
inventory”)
5
CHARACTERISTICS
10. WHY?
- Decouple
responsibilities
- Communicate
by
triggering
events
- Scale
out
components
horizontally
- Higher
responsiveness
- High
availability
&
Resiliency
17. - A
zero-‐administration
compute
platform
- Stored
procedures
for
the
cloud
- Function-‐as-‐a-‐Service
(NodeJS/Java)
- Event
driven
from
other
services
- …or
triggered
externally
and
even
chained
WHAT
IS
LAMBDA?
24. STREAMING
EVENTS
Cloudtrail
logs
streaming
to
Cloudwatch
Subscribe
Kinesis
stream
to
Cloudwatch
logs
Lambda
func8on
subscribed
to
Kinesis
watching
for
pa:erns
SNS
no8fica8on
for
insecure
pa:erns
in
Cloudtrail
logs