Automatic Discovery of Service Metadata for Systems that Scale

This was a talk by Martina Iglesias from Spotify about how they automatically discover microservice (container) metadata.

Notes:

  • Spotify has:
    • 120 teams (all over the world)
    • 1,000+ services
    • Microservices arch (each part of UI is one/several services)
  • Documentation used to be in a different place for each service
  • SystemZ
    • web tool, internal
    • Integrated with Apollo (MS framework)
    • Gets config + uptime from all containers for a particular service and aggregates
    • Gets the service API (client docs)
    • Gets “system map” about MS dependencies
      • auto generated at runtime
    • Use DNS conventions for service discovery
    • Apollo-Meta
      • Exposes metadata endpoint
      • Collects:
        • Instance Info (version, uptime)
        • Configuration (loaded config, can be filtered)
        • endpoints (lists full list of endpoints, like docs for writing client)
        • Call info
          • Lists incoming services
          • List outgoing calls to services

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.