BEGIN:VCALENDAR PRODID;X-RICAL-TZSOURCE=TZINFO:-//Calagator//EN CALSCALE:GREGORIAN X-WR-CALNAME:Calagator METHOD:PUBLISH VERSION:2.0 BEGIN:VTIMEZONE TZID;X-RICAL-TZSOURCE=TZINFO:America/Los_Angeles BEGIN:DAYLIGHT DTSTART:20190310T020000 RDATE:20190310T020000 TZOFFSETFROM:-0800 TZOFFSETTO:-0700 TZNAME:PDT END:DAYLIGHT END:VTIMEZONE BEGIN:VEVENT CREATED;VALUE=DATE-TIME:20190917T032340Z DTEND;TZID=America/Los_Angeles;VALUE=DATE-TIME:20190919T200000 DTSTART;TZID=America/Los_Angeles;VALUE=DATE-TIME:20190919T180000 DTSTAMP;VALUE=DATE-TIME:20190917T032340Z LAST-MODIFIED;VALUE=DATE-TIME:20190917T032340Z UID:http://calagator.org/events/1250476209 DESCRIPTION:This month I am going to be talking about my current work on sharding large mysql databases with Vitess. My team has been on a journ ey towards splitting our largest mysql databases and I want to share my experiences and lessons learned. We are going to look at the problems a nd possible solutions to scaling reads and writes in relational database s. \;\n \;\nVitess is an open source project born at youtube to sc ale their largest and most critical databases. It has been adopted in a s a Cloud Native Compute Foundation incubator project. With PostgreSQL on the medium-term road map\, let’s take a look at what we have been abl e to do with mysql. \;\n \;\nHi its me Grant. I work on the datab ase engineering team at New Relic. I’ve been using Postgres in producti on since 9.2. I co-organize the Postgres user group in Portland with Ma rk Wong.\n\nTags: pdxpug\, postgres\, postgresql\, mysql\, vitess\n\nImp orted from: http://calagator.org/events/1250476209 URL:https://pdx.postgresql.us SUMMARY:PDXPUG: Sharding large MySQL databases with Vitess LOCATION:PSU Business Accelerator: 2828 SW Corbett Ave\, Portland OR 9720 1 US SEQUENCE:1 END:VEVENT END:VCALENDAR