SESSION + Live Q&A
Monitoring Serverless Architectures
Serverless architectures are attracting more and more interest from the IT professionals and companies hoping to lower the costs of creating and operating distributed systems without constant worrying about availability, scalability and capacity management. Despite all the attractive properties that serverless architectures offer, such systems still need to be comprehensively monitored to be effectively operated and maintain the expected quality of service and SLAs.
In this talk, I will provide the overview of monitoring capabilities required by system built on the Serverless stack, discuss various AWS services that can be used to deliver such capabilities. I will cover everything from metering and logging to tracing, auditing and alerting.
Additionally, I will share some top tips on how to monitor and optimise the spend on the cloud infrastructure as well as control and adjust provisioned capacity for the resources that use provisioned capacity model, like DynamoDB and Kinesis.
Lastly, I will also offer some suggestions on how to supplement provider’s own solutions with bespoke extensions, built using the Serverless stack, to provide even more comprehensive monitoring.
Speaker
![](https://archive.qconlondon.com/sites/qcon_london/files/styles/240x240/public/rafal-gancarz.jpeg?itok=EvE_HhIU)
Rafal Gancarz
Lead Consultant @OpenCredo
Rafal is a Lead Consultant for OpenCredo, a London-based consultancy specialising in helping clients build and deploy emerging technologies to deliver business value. He is an experienced technologist with expertise in architecting and delivering large-scale distributed systems. Rafal is also an...
Read moreFind Rafal Gancarz at:
From the same track
Avoiding Alerts Overload From Microservices
Microservices can be a great way to work: the services are simple, you can use the right technology for the job, and deployments become smaller and less risky. Unfortunately, other things become more complex. You probably took some time to design a deployment pipeline and set up self-service...
![](https://archive.qconlondon.com/sites/qcon_london/files/styles/240x240/public/sarah_wells.jpeg?itok=srnIu-is)
Sarah Wells
Former Tech Director for Engineering Enablement @FT (Financial Times)
Do You Really Know Your Response Times?
With the recent surge in highly available microsevervices with high incoming traffic, it is becoming more and more important to know how your service is performing right now and to be able to diagnose issues in production quickly. It took a while for us to understand how to produce meaningful...
![](https://archive.qconlondon.com/sites/qcon_london/files/styles/240x240/public/daniel_rolls.jpg?itok=kNp_3ebJ)
Daniel Rolls
Collecting and Interpreting Large-Scale Data Collected @SkyUK
After Acceptance: Reasoning About System Outputs
Modern software development allows us to prove that new work is functionally complete. We write a set of executable specifications. We automatically execute them in the form of acceptance tests as part of our continuous delivery pipeline. When all the tests pass, we are done! This approach is...
![](https://archive.qconlondon.com/sites/qcon_london/files/styles/240x240/public/stefanos_zachariadis.jpg?itok=OPMvmi8k)
Dr. Stefanos Zachariadis
Senior Software Engineer
Observability, Event Sourcing and State Machines
What is a way to have complete transparency of the state of a service? Ideally we would record everything - the inputs, outputs and timings - in order to capture highly reproducible and transparent state changes. However, is it possible to record every event or message in and out of a service...
![](https://archive.qconlondon.com/sites/qcon_london/files/styles/240x240/public/peter_lawrey_0.jpeg?itok=GLD57mys)
Peter Lawrey
CEO @Chronicle_SW