Microservices
Microservices is a variant of the service-oriented architecture (SOA) architectural style that structures an application as a collection of loosely coupled services. In a microservices architecture, services should be fine-grained and the protocols should be lightweight. The benefit of decomposing an application into different smaller services is that it improves modularity and makes the application easier to understand, develop and test. It also parallelizes development by enabling small autonomous teams to develop, deploy and scale their respective services independently. It also allows the architecture of an individual service to emerge through continuous refactoring. Microservices-based architectures enable continuous delivery and deployment.
DevOps, in Wikipedia. Retrieved 2/24/2018. https://en.wikipedia.org/wiki/Microservices
Presentations about Microservices
Microservices & Scaling of Rational Interactions
Microservices Lessons Learned From a Startup
Observability and Emerging Infrastructures
Securing Serverless – By Breaking In
How to Build Observable Distributed Systems
Microservices Panel
Microservices Panel
Microservices Panel
Microservices Panel
Microservices Panel
Insecure Transit - Microservice Security
Microservices: API Re-platforming @Expedia
Logistics as a Service: Building the Ocado Smart Platform
Logistics as a Service: Building the Ocado Smart Platform
Debugging Microservices Applications
Models in Minutes not Months: AI as Microservices
3 Common Pitfalls in Microservice Integration
How to Re-Architect Without Breaking Stuff
AMA w/ Rob Harrop
AMA w/ Randy Shoup
Testing Microservices: Contracts, Simulation and Observability
Testing Microservices: Contracts, Simulation and Observability
Designing Microservices with Sam Newman
Interviews
Securing Serverless – By Breaking In
How you you describe the persona and level of the target audience?
Mid-senior technical staff - notably in the dev, ops or security - who influence the quality, process or architecture of software being developed. This includes architects, senior developers, managers, and of course application security people.
What do you want “that” persona to walk away from your talk knowing that they might not have known 50 minutes before?
A good understanding of the risks presented by using a Serverless platform for your applications, how they differ from other ops paradigms, and how you can defend yourself from them.
See more interviews
