Microservice Architecture Testing
Posted By Sakshi Jain | 29-Jun-2018
Adoption of Microservices architecture has influenced SDLC and introduce many quality challenges. For example:
- Increased dependencies over various microservices.
- Roadblocks in parallel development.
- Traditional methods of testing
- Potential points of failure in application.
Increased dependencies over various Microservices
Microservices architecture involves dividing a big application or service into more logical and isolated components. This method of testing adds value with respect to scaling and flexibility for change. To configure and provision complete test environment setup is exponentially more complex in this architecture.
For example, Consider
Roadblocks in Parallel Development
The increased number of system dependencies due to
Traditional Method of Testing is impacted
Microservices requires a more comprehensive approach of testing at message layer itself.
Validating each independent microservice is just the initial step. It is critical to test all transaction paths through more distributed microservices.
Microservices provides the ability to enable rapid change but it is also important to understand below points while choosing this architecture:
- Changes associated with the service itself.
- Service dependencies when any change occurred in
- Impact of change on critical end-to-end transactions.
- Impact of change on end user experience.
- New requirements for test data.
- Impact on non-functional requirements such as performance, reliability
Potential Points of Failure in Application
Microservices migration involves
Testing teams should monitor
Testing teams should have access to test environments which encapsulate highly componentized and distributed architecture.