Home › Software Testing › Software Testing › microservices_cloud_observability › Microservices testing differs from monolith test…
Microservices testing differs from monolith testing because
AMicroservices need no testing at all
BMonoliths cannot be tested in CI builds
CMicroservices share a single database always
DServices communicate over the network
Answer & Solution
Correct answer: D. Services communicate over the network
Microservices interact via network calls (HTTP, gRPC, messaging), introducing latency, partial failures, partitions, version skew, and orchestration concerns absent in in-process monolith calls. Testing strategy must address these explicitly.
Related questions
A 'red team' in security testing is a group that'Test impact analysis' speeds CI byIn Test Maturity Model integrated (TMMi), Level 2 is'Test pyramid' for microservices typically pushes effort toQuality gates in a deployment pipeline areA test environment management strategy primarily addressesGame days in production resilience testing involveFeature flags enable testing by