Upgrade to PRO for Only $50/Year—Limited-Time Offer! 🔥

マイクロサービスとSRECon / #microserv

マイクロサービスとSRECon / #microserv

8/9 に FiNC 社で開催された Microservices Meetup vol.2 で、マイクロサービスと SRECon という話をしました。

Takumi Sakamoto

August 09, 2016
Tweet

More Decks by Takumi Sakamoto

Other Decks in Technology

Transcript

  1. ࣗݾ঺հ • ࡔຊ୎າ (@takus) • SRE @ εϚʔτχϡʔεגࣜձࣾ • ࠷ۙͷڵຯ

    : OLAP data store (ಛʹ druid.io) • ࠷ۙͷझຯɿଉࢠ (5 ݄ʹര஀) ͱ༡ͿɺҭࣇຊΛಡΉ
  2. AWS ͷϒϩάʹدߘ͠·ͨ͠ How SmartNews Built a Lambda Architecture on AWS

    to Analyze Customer Behavior and Recommend Content
  3. SmartNews • News discovery app for mobile • Algorithm-driven article

    selection • 18M+ downloads in world wide https://www.smartnews.com/
  4. εϚχϡʔࣗओ౉ߤ঑ྭ੍౓ • ൒ظ͝ͱʹ 1 ճɺSan Francisco ·ͨ͸ New York ΦϑΟε

    ͷ๚໰ɺ·ͨ͸ΧϯϑΝϨϯεࢀՃͷͨΊͷւ֎౉ߤʹ͔͔ Δߤۭ݊අɺަ௨අɺ॓ധඅɺ௨৴අɺւ֎౉ߤอݥɺΧϯ ϑΝϨϯεɾֶձ౳ࢀՃඅΛෛ୲ͯ͘͠ΕΔࣾ಺੍౓ • ΪϣʔϜʹ௚઀ؔ܎ͳ͍ΧϯϑΝϨϯεͰ΋ OK
  5. • Conference for Site Reliability Engineers (SRE) • April 7-8,

    2016 in Santa Clara, CA. • 600+ attendees https://www.usenix.org/conference/srecon16
  6. SRECon ͱ͸ʁ • Site Reliability Engineer (SRE) ͷͨΊͷΧϯϑΝϨϯε • ࠓ೥ͷ

    4/7 - 8 ʹΧϦϑΥϧχΞभαϯλΫϥϥͰ։࠵ • ΞϝϦΧࠃ಺Λத৺ʹ 600 ໊ఔ౓ͷࢀՃऀ
  7. ௌߨͨ͠ηογϣϯͷҰ෦ • Netflix: 190 Countries and 5 CORE SREs •

    Panel: Who/What Is SRE? • Shaping Reality to Shape Outcomes: Making SRE Work with Uber Growth • nrrd 911 ic me: The Incident Commander Role • A Young Lady's Illustrated Primer to Technical Decision-Making • Continuous Deployment to Millions of Users 40 Times a Day • Finding the Order in Chaos • Performance Checklists for SREs • Doorman: Global Distributed Client Side Rate Limiting • Running Consul at Scale—Journey from RFC to Production • Panel: SRE Managers
  8. Ͱ΋ɺϚΠΫϩαʔϏε͸ΞλϦϚΤ ⬇ൃදऀͷձࣾͷϒϩά΍εϥΠυ⬇ • Netflix • MicroServices at Netflix - challenges

    of scale • Uber • Service-Oriented Architecture: Scaling Our Codebase As We Grow • Fastly • Microservices war stories
  9. Ͳ͜·Ͱࣗ༝ͳͷ͔ฉ͍ͯΈͨ Q. Freedom ͬͯݴͬͯΔ͚ͲɺͲ͜·Ͱࣗ༝ͳͷʁ • جຊతʹ֤αʔϏεͷ͜ͱ͸શͯ։ൃνʔϜʹ೚ͤΔ • Ͳͷ։ൃऀ΋ Netflix ͷγεςϜΛյͤΔ΄ͲͷΞΫηεݖ

    ݶ͕༩͑ΒΕ͍ͯΔ Q. ҙਤ͠ͳ͍ૢ࡞ͰαʔϏεΛഁյ͞ΕͨΓ͠ͳ͍ͷʁ • ͦ͜Ͱ SRE ͕࡞͍ͬͯΔπʔϧ͕ॏཁʹͳΔ • πʔϧ͕ศར͗͢ΔͷͰ։ൃऀ͸࢖͍ʹ͘͘ࣄނ΋ى͖΍ ͍͢ଞͷπʔϧΛબΜͩΓ͠ͳ͍
  10. ࣾ಺޲͚πʔϧͷ։ൃ΋ ϓϩμΫτ։ൃͷͭ΋ΓͰ Overall, these SRE-developed tools are full-fledged software engineering

    projects, distinct from one-off solutions and quick hacks, and the SREs who develop them have adopted a product-based mindset that takes both internal customers and a roadmap for future plans into account. Chapter 18. Software Engineering in SRE - Site Reliability Engineering
  11. ྫ: εϚχϡʔࣾ಺ PaaS • ࣾ಺ͷ՝୊ΛΈ͚ͭΔ (՝୊͸݈ࡏԽͯ͠Δ͜ͱ΋ଟ͍) • ϓϩτλΠϓΛ࡞Δ (࡞ΓࠐΈա͗ͳ͍ɺMVP Λҙࣝ)

    • ࠷ॳͷސ٬ (։ൃऀ) ΛΈ͚ͭΔ • ϩʔυϚοϓΛ੔උɺ༏ઌ౓Λ͚ͭͯ։ൃ͍ͯ͘͠ • υοάϑʔσΟϯά͢Δ • ސ٬ͷ੠ʹࣖΛ܏͚Δɺސ٬ͷߦಈཤྺΛ௥͍͔͚Δ
  12. ྑ͍श׳Λࣗવʹ࡞Δ࢓૊Έ ͋ΔछͷήʔϛϑΟέʔγϣϯʁ • Chaos Engineering / ϑΣΠϧΦʔόʔͷςετ • ఆظతʹյ͢͜ͱͰো֐Λҙࣝͯ͠΋Β͏ •

    յΕͳ͍Α͏ʹ޻෉͢Δ • σϓϩΠ࣌ʹ໰୊Λൃݟ͢ΔͱࣗಈϩʔϧόοΫ • ϑΣΠϧͨ͠෦෼ʹ͍ͭͯߟ͑ͯཧղͯ͠΋Β͏ • σϓϩΠͷͨΊʹΫϦΞ͠Α͏ͱ޻෉͢Δ
  13. SRE should not be a Servant • Google SRE's 50%

    ϧʔϧ • ӡ༻ΛؚΊͨٿर͍తͳ࢓ࣄΛ 50% Ҏ্΍Βͳ͍ • ٿर͍ͯ͠ʮಇ͍ͨؾʯʹͳ͍ͬͯ·ͤΜ͔ʁ • Կ͔ΛࠜຊతʹΑ͘͢Δ࣌ؒΛࣦ͍ͬͯΔ͔΋ • λεΫͷ༏ઌॱҐΛͪΌΜͱҙࣝ͢Δ • ࣌ʹ͸ No Λݴ͏͜ͱ΋େ੾ • ΋ͪΖΜো֐ରԠͷΞγετͳͲ͸༏ઌ