Upgrade to Pro — share decks privately, control downloads, hide ads and more …

俺のメッシュがこんなに可愛いわけがない

 俺のメッシュがこんなに可愛いわけがない

Rei Shimizu

July 18, 2020
Tweet

More Decks by Rei Shimizu

Other Decks in Programming

Transcript

  1. 俺のメッシュがこんなに可愛いわけがない
    〜サービスメッシュ入門〜

    View Slide

  2. whoami
    ● Shikugawa / Rei Shimizu (@_iy4)
    ● M1, Computer Science and Engineering
    ● Member of Envoy Proxy
    ● Member of Istio
    ● Loves C++ and Cloud Native
    For more detail: https://shikugawa.net

    View Slide

  3. monolithic vs microservices
    Monolithic Microservices
    One large service is aggregation of many
    business logics.
    One business logic is independent.
    One large service is aggregation of many
    services.

    View Slide

  4. The challenges of microservices
    ● Hard to define service boundaries.
    ● Hard to ensure data consistency.
    ● Service Discovery
    ● Observability
    ● Zero-Trust networking workload (AuthN/AuthZ)
    etc...

    View Slide

  5. The challenges of microservices
    ● Hard to define service boundaries.
    ● Hard to ensure data consistency.
    ● Service Discovery
    ● Observability
    ● Zero-Trust networking workload (AuthN/AuthZ)
    etc...
    Service Mesh
    Can Service Mesh be the Silver Bullet to overcome these
    challenges of microservices..…?

    View Slide

  6. What is Service Mesh?
    ● Provide service management layer on your infrastructure.
    ● The main components of Service Mesh are
    ○ Data Plane
    ■ Provide L4/L7 related networking ability as reverse proxy.
    ■ Split out only business logic from services.
    ○ Control Plane
    ■ Manage Data Planes
    Disentangle common networking related workloads from services.

    View Slide

  7. What is Service Mesh?
    https://www.redhat.com/ja/topics/microservices/what-is-a-service-mesh

    View Slide

  8. What is Service Mesh?
    Service A
    Data Plane
    Service B
    Data Plane
    Control Plane
    Config Config
    https://speakerdeck.com/shikugawa/xds-deep-dive

    View Slide

  9. Envoy
    ● Envoy is a de-facto standard data plane implementation for Service Mesh.
    ● L4/L7 reverse proxy optimized for cloud native workload.
    ○ Dynamic configurable
    ○ Custom L4/L7 filter
    ○ Advanced logging/stats observability
    ○ High performance
    ● Not only for data plane on Service Mesh!
    ○ We can use envoy as edge proxy.

    View Slide

  10. Challenges of Service Mesh
    ● Hard to introduce existing large-scaled microservices
    ● Complexity explosion
    ● Latency
    ● Hard to manage large-scaled Service Mesh
    ○ e.g. Istio config is very very very complex....

    View Slide

  11. Service Mesh is not so cute….

    View Slide

  12. Thank you!
    質問などはTwitter(@_iy4)で受け付けております!

    View Slide