Useful information in log entries

Posted . Visible to the public. Draft.
  1. Timestamps
  2. Identifiers
  3. Source
  4. Level or category
Sanjay
Say thanks

Related cards:

Common code to include in Microservice chassis

  • Logging
  • Configuration fetching
  • Metrics collection
  • Data store setup
  • Health checks
  • Service registry and discovery
  • The chosen transport-related boilerplate (AMQP, HTTP)

Sections in a design review document for a new microservice

Section Purpose
Problem ...

Microservices Team Models

  1. Grouping by function
  • Unclear ownership
  • Lack of autonomy
  • No long-term responsibility
  • Risk of silos
  1. Grouping across functions
  • Aligning teams with business value will be reflected in the application developed; the te...

6 fundamental capabilities of microservice production environment

  1. A deployment target, or runtime platform, where services are run, such as virtual machines (Ideally, engineers can use an API to configure, deploy, and update service configuration. You also could call this API the control pane, as shown in the...

Characteristics of a successful on-cal rotation

  • Inclusive — Everyone who can do it, should do it, including VPs and directors.
  • Fair — On-call work should be remunerated in addition to normal working hours.
  • Sustainable — Enough engineers should be in a rotation to avoid burnout...

Maximizing Service Reliability

  1. Load balancing and service health
  • Readiness
  • Liveness
  1. Rate limits
  • Back-pressure via headers
  1. Validating reliability and fault tolerance
  • Load testing ([The art of scalability](The
    Art of Scalability))
    1. Load test as part...

Three common patterns for zero-downtime deployments

  1. Rolling deploy — You progressively take old instances (version N) out of service while you bring up new instances (version N+1), ensuring that you maintain a minimum percentage of capacity during deployment.
  2. Canaries — You add a sing...

How to build reliable communication

  1. Retries
  • Exponential backoff
    1. Use jitter
  • Considerations
    1. Always limit the total number of retries.
    2. Use exponential back-off with jitter t...

What’s the purpose of a microservice chassis?

  1. Making it easier to onboard team members
  2. Getting a good understanding of the code structure and concerns regarding the tech stack that an engineering team uses
  3. Limiting the scope of experimentation for production systems as the team build...

Components of a monitoring stack

  • Metrics
  • Logs
  • Traces
Posted by Sanjay to Microservices In Action (2019-07-13 01:26)
This website uses short-lived cookies to improve usability.
or learn more