Four Distributed Systems Architectural Patterns by Tim Berglund
Subscribe to Devoxx on YouTube @ https://bit.ly/devoxx-youtube
Like Devoxx on Facebook @ https://www.facebook.com/devoxxcom
Follow Devoxx on Twitter @ https://twitter.com/devoxx
Developers and architects are increasingly called upon to solve big problems, and we are able to draw on a world-class set of open source tools with which to solve them. Problems of scale are no longer consigned to the web’s largest companies, but are increasingly a part of ordinary enterprise development. At the risk of only a little hyperbole, we are all distributed systems engineers now.
In this talk, we’ll look at four distributed systems architectural patterns based on real-world systems that you can apply to solve the problems you will face in the next few years. We’ll look at the strengths and weaknesses of each architecture and develop a set of criteria for knowing when to apply each one. You will leave knowing how to work with the leading data storage, messaging, and computation tools of the day to solve the daunting problems of scale in your near future.
Tim Berglund is a teacher, author, and technology leader with Confluent, where he serves as the Senior Director of Developer Experience. He can frequently be found at speaking at conferences in the United States and all over the world. He is the co-presenter of various O’Reilly training videos on topics ranging from Git to Distributed Systems, and is the author of Gradle Beyond the Basics. He tweets as @tlberglund, blogs very occasionally at http://timberglund.com, is the co-host of the http://devrelrad.io podcast, and lives in Littleton, CO, USA with the wife of his youth and their youngest child, the other two having mostly grown up.
Видео Four Distributed Systems Architectural Patterns by Tim Berglund канала Devoxx
Like Devoxx on Facebook @ https://www.facebook.com/devoxxcom
Follow Devoxx on Twitter @ https://twitter.com/devoxx
Developers and architects are increasingly called upon to solve big problems, and we are able to draw on a world-class set of open source tools with which to solve them. Problems of scale are no longer consigned to the web’s largest companies, but are increasingly a part of ordinary enterprise development. At the risk of only a little hyperbole, we are all distributed systems engineers now.
In this talk, we’ll look at four distributed systems architectural patterns based on real-world systems that you can apply to solve the problems you will face in the next few years. We’ll look at the strengths and weaknesses of each architecture and develop a set of criteria for knowing when to apply each one. You will leave knowing how to work with the leading data storage, messaging, and computation tools of the day to solve the daunting problems of scale in your near future.
Tim Berglund is a teacher, author, and technology leader with Confluent, where he serves as the Senior Director of Developer Experience. He can frequently be found at speaking at conferences in the United States and all over the world. He is the co-presenter of various O’Reilly training videos on topics ranging from Git to Distributed Systems, and is the author of Gradle Beyond the Basics. He tweets as @tlberglund, blogs very occasionally at http://timberglund.com, is the co-host of the http://devrelrad.io podcast, and lives in Littleton, CO, USA with the wife of his youth and their youngest child, the other two having mostly grown up.
Видео Four Distributed Systems Architectural Patterns by Tim Berglund канала Devoxx
Показать
Комментарии отсутствуют
Информация о видео
Другие видео канала
Processing Streaming Data with KSQL - Tim BerglundNETFLIX System design | software architecture for netflixDistributed Systems in One Lesson by Tim BerglundArchitecting Large Scale Systems | Creating Scalable Web Application ArchitectureGOTO 2017 • The Many Meanings of Event-Driven Architecture • Martin Fowler10 Tips for failing badly at Microservices by David SchmitzScaling Instagram InfrastructureGOTO 2019 • Building Resilient Frontend Architecture • Monica LentEvent-Driven Architecture | EDA | Software Architectural PatternsETL Is Dead, Long Live Streams: real-time streams w/ Apache KafkaWhat is Apache Kafka®? (A Confluent Lightboard by Tim Berglund) + ksqlDBAvoiding Microservice Megadisasters - Jimmy BogardSystems Design Interview Concepts (for software engineers / full-stack web)Introduction to NoSQL databasesBuilding event-driven (Micro)Services with Apache Kafka by Guido SchmutzSystem Design Interview - Distributed CacheMicroservices + Events + Docker = A Perfect TrioGoogle Systems Design Interview With An Ex-GooglerUsing sagas to maintain data consistency in a microservice architecture by Chris Richardson