.NET Core using AWS with Jon Vines & Ian Cooper with Event Driven Collaboration
Description changed:
This event will be split into two parts, Jon Vines presenting Building .NET Core Apps using AWS and the Serverless Framework and the second half will be Ian Cooper presenting Event Driven Collaboration.
**Building .NET Core Apps using AWS and the Serverless Framework**
Jon has been building serverless applications for over 18 months, including simple APIs providing data for a front-end, to event-driven data pipelines providing new insights and applications. In this talk Jon will introduce the basics of serverless development and explain how to get up and running with the Serverless Framework on Amazon Web Services.
He will reveal how his team succeeded in deploying a critical service into production in less than two weeks and share some of the hard-learned lessons gleaned on the way.
Bio
Jon Vines is a software engineer and team lead at AO.com. He has been building, deploying and operating systems for over ten years. He is interested in serverless, event-driven architectures and the application of DevOps principles and practices.
This event will be split into two parts, Jon Vines presenting Building .NET Core Apps using AWS and the Serverless Framework and the second half will be Ian Cooper presenting Event Driven Collaboration.
📅 Agenda
- 👋 Welcome
- 🗑️ Housekeeping
- 👨🏫 Building .NET Core Apps using AWS and the Serverless Framework
- 🍕 Food/Drinks
- 👨🏫 Event Driven Collaboration
- 🍻 Social @ http://www.sheffieldtap.com/
👉 **Building .NET Core Apps using AWS and the Serverless Framework**
Jon has been building serverless applications for over 18 months, including simple APIs providing data for a front-end, to event-driven data pipelines providing new insights and applications. In this talk Jon will introduce the basics of serverless development and explain how to get up and running with the Serverless Framework on Amazon Web Services.
He will reveal how his team succeeded in deploying a critical service into production in less than two weeks and share some of the hard-learned lessons gleaned on the way.
🕵️♂️ Jon Vines:
Jon Vines is a software engineer and team lead at AO.com. He has been building, deploying and operating systems for over ten years. He is interested in serverless, event-driven architectures and the application of DevOps principles and practices.
👉 **Event Driven Collaboration**
When we move from a monolith to microservices we abandon integrating via a shared database, as each service must own its own data to allow them it to be autonomous. But now we have a new problem, our data is distributed. What happens if I need one service needs to talk to another about a shared concept such as a product, a hotel room, or an order? Does every service need to have a list of all our users? Who knows what users have permissions to the entities within the micro service? What happens if my REST endpoint needs to include data from a graph that includes other services to make it responsive? And I am not breaking the boundary of my service when all of this data leaves my service boundary in response to a request?
Naive request-based solutions result in chatty calls as each service engages with multiple other services to fulfil a request, or in large message payloads as services add all the data required to process a message to each message. Neither scale well.
In 2005, Pat Helland wrote a paper ‘Data on the Inside vs. Data on the Outside’ which answers the question by distinguishing between data a service owns and reference data that it can use. Martin Fowler named the resulting architectural style; Event Driven Collaboration. This style is significant because it shifts the pattern from request to receiver-driven flow control.
In this presentation we will explain how events help us integrate our service architectures. We’ll provide examples in C#, Python and Go as well as using RMQ and Kafka.
🕵️♂️ Ian Cooper:
Polyglot Coding Architect in London, founder of #ldnug, speaker, tabletop gamer, geek. Tattooed, pierced, and bearded. The 'guv' on @BrighterCommand
