Testing a Service Fabric solution and live happy!!
Download as PPTX, PDF1 like555 views
This document discusses testing Service Fabric solutions. It emphasizes the importance of unit testing microservices to ensure reliability and stability. It identifies three main obstacles to unit testing microservices - the Service Fabric platform, external dependencies, and other microservices. It proposes solutions such as mocking the platform, abstracting proxies, and creating layers of indirection to overcome these obstacles. The document also discusses chaos testing to evaluate how solutions handle errors and complex state transitions in production-like conditions.
Testing a Service Fabric solution and live happy!!
- 1. 1 Testing a Service Fabric solution and live happy!!! Massimo Bonanni Paranormal Developer, with the head in the Cloud and all the REST in microservices! @massimobonanni massimo.bonanni@microsoft.com
- 5. 5
- 6. 6
- 7. Unit testing
- 8. 8 Programming Models Dev & Ops Tooling Orchestration Lifecycle Management Health & Monitoring Always On Availability Auto Scaling AzureOn-premises infrastructureAny cloudDev machine Service Fabric: Microservices platform ExecutablesReliable Services (.NET, Java) Reliable Actors (.NET, Java)ASP.NET Core Containers
- 9. 9 F5 is our friend…. It is the most used test tools It's free and you can find it in all Visual Studio versions You don’t have to write any additional code
- 10. 10 F5 is not useful …. with Service Fabric Resources – you need a local cluster Time – you need to publish the app Code complete – you need all the microservices you interact with
- 11. 11 Why unit test… A unit test is an automated piece of code that invokes a unit of work in the system and then checks a single assumption about the behavior of that unit of work. Roy Osherove – The Art Of Unit Testing Microservices are small, perform single functionality and loosely coupled. Microservices Architecture
- 12. 12 Why unit test… A unit test is an automated piece of code that invokes a unit of work in the system and then checks a single assumption about the behavior of that unit of work. Roy Osherove – The Art Of Unit Testing Microservices are small, perform single functionality and loosely coupled. Microservices Architecture A microservice is your Unit of Work to test!!!
- 13. 13 The three obstacles Your µService Service Fabric Platform Replicas Partitioning State Management…… File System Database Web Service External Components Others µServices
- 14. 14 Real case: Shopping Cart & Order We model 3 typical shopping cart scenarios • The cart can be created only if it is a new cart Creating the shopping cart • Need to check if the product is still available Adding a product to the cart • The order is created starting from the cart and only if the order is new Creating an order from the cart
- 15. 15 Scenario : Creating the shopping cart We must "replace" the Service Fabric platform, so our tests doesn’t need the cluster. Service Fabric Platform Replicas Partitioning State Management ……
- 16. 16 Scenario : Creating the shopping cart this.StateManager.TryGetStateAsync<State>(StateKeyName, cancellationToken); this.StateManager.SetStateAsync(StateKeyName, state, cancellationToken); this.RegisterReminderAsync(ExpiredReminderName, null, CartExpiredTimeout, TimeSpan.FromMilliseconds(-1));
- 17. 17 Scenario : Adding a product to the cart We need to decouple our microservice from external components, so that our tests can verify only the actor's logic. File System Database Web Service External Components
- 18. 18 Scenario : Adding a product to the cart private async Task<ProductData> GetProductFromStorageAsync(string productId, double quantity, CancellationToken cancellationToken) { ProductData result = null; try { using (SqlConnection conn = new SqlConnection(connectionString)) using (SqlCommand cmd = new SqlCommand("CheckProduct", conn)) { // Database code } } catch { result = null; } return result; }
- 19. 19 Scenario : Creating an order from the cart We must to replace the static classes ActorProxy and ServiceProxy used in the creation of communication proxies. Others µServices
- 20. 20 Scenario : Creating an order from the cart var orderProxy = ActorProxy.Create<IOrderActor>(this.Id, new Uri("fabric:/TestingApp/OrderActor"));
- 21. Demo: Unit test
- 22. 22 The three obstacles….three solutions! Your µService Service Fabric Platform Replicas Partitioning State Management …… File System Database Web Service External Components Others µServices Mock the platform (ServiceFabric.Mocks) Abstract the proxy factories Create a layer of indirection
- 23. The CHAOS
- 24. 24 Keep the stability!!!! Solutions based on distributed architectures such as cloud infrastructures must be: This is why you need to be able to test the stability of your solutions when complex state transitions due to errors occur in the underlying infrastructure. •able to withstand or recover quickly from difficult conditionsResilient • its status does not get corrupted as a result of a problemReliable
- 25. 25 What can go wrong in production? Restarting a node Restarting a distributed code package Removing a replica Restarting a replica Moving a primary replica Moving a secondary replica Remove a node Add a node
- 26. 26
- 27. 27 Start-ServiceFabricChaos Chaos induces faults in the cluster based on the received input parameters. Chaos runs in multiple iterations: each iteration consists of faults and cluster validation. You can control: • how long Chaos runs, • how long it waits between iterations, • how many faults it can induce during an iteration, • how long it waits between faults. • ….
- 28. Demo: Chaos test
- 29. 29 Take away…. Keep the microservices simple….they will be testability simply! When design a solution, keep in mind the testability! Mock, fake and shim are your best friends! If car companies launch expensive cars against a wall to test them, why should not you do it with your code?