This document discusses testing in microservices architectures. It covers why organizations adopt microservices, challenges in testing microservices compared to monolithic architectures, and strategies for testing microservices including using mock servers. Specific challenges covered include dependency management, session management, dealing with decentralized databases, managing test data, and documenting service contracts. The presentation provides an agenda and overview of moving from a monolithic to microservices architecture.

1. Testing in Micro-services
Architecture
Varuna Srivastava
Bangalore
August 22nd 2015

2. Agenda
• Why MicroServices
• Monolithic to MicroServices Architecture
• Challenges In Testing
• Demo using MockServer

3. No Free Lunch

4. API

5. Monolithic Enterprise to Microservice Architecture

6. Multiple services work together as a system…. ..to provide
business feature

7. Traditional Testing Approach

8. New Perspective in Testing

9. Validating small component
Persist
ence
CertificationAddress

10. Micro Service Interactions
Certification
Address
Payment

11. Challenges
• Dependency Management
• Tackle a Session
• Distributed System Complexity (Decentralized Database)
• Managing Test Data
• Contract Documentation

12. #1 Dependency Management

13. Dependency Management

14. Dependency Management

15. #2 Session Management

16. Session Management

17. #3 Decentralized Database

18. #4
• Mock Test Data Service environment specific

19. #5 Contract Documentation

20. Address Contract Documentation

21. SnowCrash
snowcrash Address.md

22. •
• Aglio -i Address.md –o Address.html
Dredd Address.md

23. Some Tricks
• Focus on one service end point at a time
• Define the boundary of test
• Make sure services are designed to support different content type.

24. Mock Server