Microservices on .NET
0 likes104 views
This document discusses microservices and provides an overview of key concepts. It begins by defining microservices as single applications composed of small, independent services that communicate using lightweight mechanisms like HTTP. It then covers topics like leaving monolithic architectures, example implementations, dynamic proxies for communication between services, service discovery using Etcd, drawbacks like increased complexity, and the importance of monitoring distributed systems.
![36
_reportService.GetForLast5Min()
[“123”, “345”, “678”]](https://image.slidesharecdn.com/microdotnextvbaum-160618073209/85/Microservices-on-NET-36-320.jpg)
![50
//share of common interface on both
// sides (client and server) ==
// compiler-time checking
[HttpProperties (Port = 80, SSL = true)]
interface IValueService {
IEnumerable<string> Get();
}
BENEFITS?](https://image.slidesharecdn.com/microdotnextvbaum-160618073209/85/Microservices-on-NET-50-320.jpg)
![85
class Program
{
static void Main(string[] args)
{
Cluster.Bootstrap(new WebApiProvider(),
new EtcdProvider(), "values", "v1");
Console.ReadLine();
}
}
public class ValuesController : ApiController
{
public string Get()
{
return "WebApi Service";
}
}](https://image.slidesharecdn.com/microdotnextvbaum-160618073209/85/Microservices-on-NET-85-320.jpg)
Microservices on .NET
- 3. AGENDA • leaving monolith • example • dynamic proxy + communications • elastic search (elk) • service discovery • drawbacks
- 4. 4 WTF?!
- 5. 5 What is it? "Microservices" - yet another new term on the crowded streets of software architecture.
- 6. 6 What is it? Single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, often an HTTP resource API
- 7. 7
- 11. 11 SIZE
- 16. 16 DEPENDECIES
- 21. 21 ISOLATION
- 26. 26 Azure Service Fabric Akka OTP MICROSERVICES PLATFORMS
- 27. 27 BE CHUNKY. NOT CHATTY. RPC ISN’T EQUAL FUNCTION CALL
- 28. 28 EXAMPLE
- 29. 29 FROM MONOLITH TO MICROSERVICE IN A MINUTES
- 30. 30
- 37. 37 IEnumerable<string> GetForLast5Min() { return _valuesService.Get( DateTime.Now.AddMinutes(-5); ); } DEPENDENCY INJECTION
- 42. 42 IEnumerable<string> GetForLast5Min() { return _valuesService.Get( DateTime.Now.AddMinutes(-5); ); } DEPENDENCY INJECTION
- 43. 43 DI CONTAINER CLIENT 1 CLIENT 2 CLIENT 3 SERVICE 1 SERVICE 2 SERVICE 3
- 45. 45 DYNAMIC PROXY CLIENT 1 CLIENT 2 CLIENT 3 SERVICE 1 SERVICE 2 SERVICE 3
- 47. 47 ClientInterceptor void Process(FunctionCall func) { func.Result = MakeHttpCall(func); } GET myservice.local/values?since=5min
- 48. 48 DYNAMIC PROXY CLIENT 1 CLIENT 2 CLIENT 3 SERVICE 1 SERVICE 2 SERVICE 3
- 49. 49 ServerInterceptor HttResponse Process(HttpRequest req) { return CallMyService(req); } >> IValueService.Get(time);
- 50. 50 //share of common interface on both // sides (client and server) == // compiler-time checking [HttpProperties (Port = 80, SSL = true)] interface IValueService { IEnumerable<string> Get(); } BENEFITS?
- 51. 51 DYNAMIC PROXY OVER THE INTERFACE CLIENT 1 CLIENT 2 CLIENT 3 SERVICE 1 SERVICE 2 SERVICE 3
- 52. 52 message HelloRequest { string greeting = 1; } message HelloResponse { string reply = 1; } service HelloService { rpc SayHello(HelloRequest) returns (HelloResponse); }
- 53. 53 service Calculator extends shared.SharedService { i32 add(1:i32 num1, 2:i32 num2) } APACHE THRIFT
- 54. 54 HOW TO TEST?
- 55. 55 IEnumerable<string> GetForLast5Min() { return _valuesService.Get( DateTime.Now.AddMinutes(-5); ); } DEPENDENCY INJECTION
- 56. 56 MANUAL TESTS
- 57. 57 REST IS IN PLACE 0. Simple to use (HTTP) and read (JSON) 1. A lot of tools (wget, curl, postman)
- 59. 59 DYNAMIC PROXY CLIENT 1 CLIENT 2 CLIENT 3 SERVICE 1 SERVICE 2 SERVICE 3
- 60. 60 DynamicServiceClientInterceptor void Process(FunctionCall func) { func.Result = MakeHttpCall(func); } GET myservice.local/values?since=5min ACTUALLY FAKE SERVICE
- 61. 61 DYNAMIC PROXY CLIENT 1 CLIENT 2 CLIENT 3 SERVICE 1
- 62. 62 DYNAMIC PROXY CLIENT 1 CLIENT 2 SERVICE 1 TEST LOGIC
- 63. 63 DynamicServiceClientInterceptor void Process(FunctionCall func) { func.Result = _production ? MakeHttpCall(func) : MakeMockCall(func); } LOCAL FAKE CALL
- 64. 64 A QUESTION: WHAT WAS THE DATA YESTERDAY?
- 66. 66 WEB LOGS
- 68. 68 REST: HTTP + JSON
- 70. 70
- 73. 73 ClientInterceptor void Process(FunctionCall func) { func.Result = MakeHttpCall(func); } GET myservice.local/values?since=5min HARDCODED
- 77. 77 0. Simple to use (REST) 1. Key-Value storage 2. Like a directory tree 3. Sync data to all nodes 4. High available out-of-the-box WHY ETCD?
- 78. 78
- 80. 80 string ResolveUrl(string serviceName) { var url = _readUrlFor(serviceName); return url; } GET http://myetcd/v2/keys/valueService
- 81. 81 applicationapplication application KV storageKV storage KV storage M
- 82. 82 // wait for update GET http://myetcd/v2/keys/valueService? wait=true LONG POOLING AND CACHE LOCAL
- 83. 83 applicationapplication application KV storageKV storage KV storage M
- 84. 84 https://github.com/rogeralsing/Microphone Consul, ETCD Nancy, Web Api MICROPHONE
- 85. 85 class Program { static void Main(string[] args) { Cluster.Bootstrap(new WebApiProvider(), new EtcdProvider(), "values", "v1"); Console.ReadLine(); } } public class ValuesController : ApiController { public string Get() { return "WebApi Service"; } }
- 87. 87 // automatically load balanced over service instances var instance = await Cluster.FindServiceInstanceAsync("orders"); // use Rest# or similar to call into the remote service MakeSomeCall(“/api/orders", instance.ServiceAddress, instance.ServicePort);
- 88. 88 with Load Balancer: - HAProxy - NGINX SERVER-SIDE SERVICE DISCOVERY
- 89. 89 IMPROVEMENTS?
- 90. 90 BE REACTIVE
- 92. 92 SQS Kinesis Queues Service Bus
- 93. DRAWBACKS
- 94. 94 DO NOT KEEP IT MICRO. IT IS NOT ABOUT LINES OF CODE
- 95. 95 COMPLEXITY OVERALL AS A DISTRIBUTED SYSTEM
- 99. 99
- 101. 101
- 103. 103 TAKEAWAYS • Use it if • Continuos Delivery • Fast Changes • Distributed Team • Be ready for • Complexity
- 104. THANKS!
- 105. Q&A