<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/feed.rss.xml" type="text/xsl" media="screen"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Shuzhi</title>
    <description/>
    <link>https://speakerdeck.com/xiaozhi239</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/xiaozhi239.rss"/>
    <lastBuildDate>2022-03-01 15:00:44 -0500</lastBuildDate>
    <item>
      <title>Design a mobile app logging platform that scales for hundreds of engineers</title>
      <description>Logging for a giant app is challenging. Besides the general challenges such as mobile network reliability, data quality or performance concern. For a giant app you have to control the log growth sustainably, ensure data interoperability across logs from teams who probably even don't know each other, avoid the tragedy of the commons, reduce cognitive load for logging, control data quality without slowing people down...

The talk shares some experience we learnt in designing a sustainable logging platform that is effective and scales. It will cover the principles, origins, evolvement, and some good practices. The talk will steer away from specific technical terms or implementation details, but the abstract design concepts should be transferrable and IMO way more important. I think it's a fun story of a platform team (well described concept from Team Topologies) in action.

Through the journey, we learn some of the values that an architect can bring (quotes from Software Architect Elevator):
- Prevent people from exercising intelligence unnecessarily. 
- Act like a gardener, create context where ideas can evolve and thrive in harmony. </description>
      <media:content url="https://files.speakerdeck.com/presentations/d0faea6d955846bbabec6af0868ba675/preview_slide_0.jpg?20642814" type="image/jpeg" medium="image"/>
      <content:encoded>Logging for a giant app is challenging. Besides the general challenges such as mobile network reliability, data quality or performance concern. For a giant app you have to control the log growth sustainably, ensure data interoperability across logs from teams who probably even don't know each other, avoid the tragedy of the commons, reduce cognitive load for logging, control data quality without slowing people down...

The talk shares some experience we learnt in designing a sustainable logging platform that is effective and scales. It will cover the principles, origins, evolvement, and some good practices. The talk will steer away from specific technical terms or implementation details, but the abstract design concepts should be transferrable and IMO way more important. I think it's a fun story of a platform team (well described concept from Team Topologies) in action.

Through the journey, we learn some of the values that an architect can bring (quotes from Software Architect Elevator):
- Prevent people from exercising intelligence unnecessarily. 
- Act like a gardener, create context where ideas can evolve and thrive in harmony. </content:encoded>
      <pubDate>Tue, 01 Mar 2022 00:00:00 -0500</pubDate>
      <link>https://speakerdeck.com/xiaozhi239/design-a-mobile-app-logging-platform-that-scales-for-hundreds-of-engineers</link>
      <guid>https://speakerdeck.com/xiaozhi239/design-a-mobile-app-logging-platform-that-scales-for-hundreds-of-engineers</guid>
    </item>
  </channel>
</rss>
