Strangler fig pattern in Microservices - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the Strangler fig pattern in system design?

It is a method to gradually replace or modernize a legacy system by building a new system around it and slowly redirecting parts of the old system's functionality to the new one until the old system is fully replaced.

beginner

Why is the Strangler fig pattern named after a strangler fig tree?

Because just like the strangler fig tree grows around an old tree and eventually replaces it, this pattern grows a new system around the old one until the old system is no longer needed.

intermediate

What is a key benefit of using the Strangler fig pattern?

It allows safe, incremental migration without stopping the entire system, reducing risk and downtime during modernization.

intermediate

How does the Strangler fig pattern relate to microservices?

It helps break a monolithic legacy system into microservices step-by-step by redirecting specific features or modules to new microservices gradually.

advanced

What is a common challenge when implementing the Strangler fig pattern?

Managing data consistency and integration between the old and new systems during the transition phase can be complex.

What is the main goal of the Strangler fig pattern?

A Merge two unrelated systems

B Build a new system from scratch without old system

C Gradually replace a legacy system with a new system

D Keep the legacy system unchanged

The Strangler fig pattern focuses on gradually replacing the legacy system by building a new system around it.

Which analogy best describes the Strangler fig pattern?

A A tree growing around and replacing another tree

B A river splitting into two streams

C A bridge connecting two islands

D A house being painted a new color

The pattern is named after the strangler fig tree that grows around an old tree and eventually replaces it.

What is a key advantage of the Strangler fig pattern?

A Allows incremental migration with minimal downtime

B Requires complete system shutdown

C Eliminates need for testing

D Avoids any changes to legacy code

It enables gradual migration, reducing risk and downtime.

In microservices, how is the Strangler fig pattern typically used?

A By ignoring the legacy system

B By gradually redirecting features from monolith to microservices

C By rewriting the entire monolith at once

D By merging microservices into a monolith

It helps break down a monolith by incrementally moving features to microservices.

What is a common challenge when applying the Strangler fig pattern?

A Designing user interfaces

B Finding new developers

C Choosing a programming language

D Managing data consistency between old and new systems

Data consistency and integration during transition is often complex.

Explain the Strangler fig pattern and how it helps in modernizing legacy systems.

Think about how a new system grows around an old one like a tree.

Describe how the Strangler fig pattern can be applied to break a monolithic system into microservices.

Focus on moving parts step-by-step rather than all at once.