Given the architectural advantages they provide, like the loose coupling between components and its resilient nature, event-driven architectures (EDAs) are becoming quite popular. Serverless architectures—those that incorporate third-party backend-as-a-service (BaaS) products into the application or use functions-as-a-service (FaaS) platforms like AWS Lambda to run server-side code in fully managed and event-driven containers—are also attracting a lot of attention, due to their scalability and the ease of deployment when it comes to distributed services in the cloud.
Karun Japhet and Vinicius Gomes compare the the multiple cross-functional requirements of serverless and microservices implementations of an event-driven system, such as monitorability, scalability, resilience, reliability, and maintainability, and explore the implications of going serverless.
Karun Japhet is a tech lead, developer, and quality advocate at ThoughtWorks. Over the past nine years, he has worked on realizing value for his clients through the creation of highly scaleable applications and integration of large enterprise applications. Karun believes that if you’re not considering serverless architectures in event-driven systems, you may be doing it wrong.
Vinicius Gomes is a software developer at ThoughtWorks. Vinicius is passionate about distributed systems and functional programming. He writes about software development and technology on his blog. Vincius is a strong proponent of microservices architectures and believes in it’s stability and maturity for large scale production systems.
Help us make this conference the best it can be for you. Have questions you'd like this speaker to address? Suggestions for issues that deserve extra attention? Feedback that you'd like to share with the speaker and other attendees?
Join the conversation here (requires login)
©2017, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org