BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//DevOps.com - ECPv5.16.4//NONSGML v1.0//EN
CALSCALE:GREGORIAN
METHOD:PUBLISH
X-WR-CALNAME:DevOps.com
X-ORIGINAL-URL:https://devops.com
X-WR-CALDESC:Events for DevOps.com
BEGIN:VTIMEZONE
TZID:America/New_York
BEGIN:DAYLIGHT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
DTSTART:20180311T070000
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
DTSTART:20181104T060000
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/New_York:20181018T110000
DTEND;TZID=America/New_York:20181018T120000
DTSTAMP:20260826T112741
CREATED:20180926T135839Z
LAST-MODIFIED:20190907T051549Z
UID:125802-1539860400-1539864000@devops.com
SUMMARY:Lessons from the Birth of Microservices at Google
DESCRIPTION:Google deserves a lot of credit for imagining (and popularizing) what we now call “microservice architectures.” With the benefit of hindsight\, we now recognize that Google made mistakes during those early days of microservices. And unfortunately\, the rest of the industry is repeating many of these mistakes today. What did Google get wrong about microservices\, and how can we apply those lessons today? \nJoin us for our upcoming technical talk where Ben Sigelman – LightStep CEO\, OpenTracing co-creator\, and former Googler who built Dapper\, Google’s distributed tracing infrastructure – will discuss: \n\nThe problems Google wanted to solve with microservices\nWhat Google got wrong with microservices (and a few things they got right)\nCommon microservice pitfalls today and how they compare with Google’s issues many years ago\nPractical steps engineering teams can take to avoid the preventable microservices failure modes
URL:https://devops.com/webinars/lessons-from-the-birth-of-microservices-at-google/
CATEGORIES:2018 Webinars
ATTACH;FMTTYPE=image/jpeg:https://devops.com/wp-content/uploads/2018/09/Google-Microservices-1.jpg
END:VEVENT
END:VCALENDAR