liveBook · Manning

Experimentation

As explained in Microservices Patterns, Second Edition

The practice of evaluating a technology through controlled trials that approximate the application's real operational needs.

A new technology can look promising without fitting an application or organization. Test that fit with an experiment that is both realistic and low-cost: implement and deploy one subdomain rather than relying on toy applications or committing to a whole complex application. section 5.3.2

When considering a technology such as Rust, weigh these approaches:

  • Toy applications are inexpensive but do not test production deployment. section 5.3.2
  • A complex production application is realistic but risks a large investment before revealing a poor fit. section 5.3.2
  • A deployed subdomain provides a realistic test with a comparatively limited investment; this is usually the best option. section 5.3.2

How Microservices Patterns, Second Edition covers it

How deep it goes
Compares toy, full-production, and single-subdomain trials, then recommends the latter without detailing experiment execution.
Examples
Uses Rust adoption to contrast toy applications, a complex production application, and a deployed subdomain.
What you can do after
Evaluate technology fit by implementing and deploying one application subdomain with the candidate technology.
How it connects
Connects technology adoption with production deployment and application evolvability.

Also explained in

Compare how 20 books explain experimentation →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Microservices Patterns, Second Edition. The section links point to the parts of the book it draws on.