@ediri
About
Cloud Native Pilgrim | Kubernetes Enthusiast | Serverless Believer | Customer Experience Architect @ Pulumi | (he/him) | CK{A,AD} |
Available for
Nothing here yet.
Cloud Native Pilgrim | Kubernetes Enthusiast | Serverless Believer | Customer Experience Architect @ Pulumi | (he/him) | CK{A,AD} |
Nothing here yet.
I can only explain it, that my web server can't handle all the requests/s and timeout. I see some timeouts in the result of bombardier: Bombarding http://127.0.0.1:6767 with 5000000 request(s) using 50 connection(s) 5000000 / 5000000 [==================================================================================================================================================================================================================================================================================] 100.00% 106194/s 47s Done! Statistics Avg Stdev Max Reqs/sec 106292.69 44491.73 224577.53 Latency 393.78us 91.33ms 33.91s Latency Distribution 50% 43.00us 75% 63.00us 90% 103.00us 95% 170.00us 99% 642.00us HTTP codes: 1xx - 0, 2xx - 4999962, 3xx - 0, 4xx - 0, 5xx - 0 others - 38 Errors: dial tcp 127.0.0.1:6767: connect: operation timed out - 38 Throughput: 21.90MB/s
No, it's not about immutable fields. It's all about the way to control the creation process of complex objects with a step by step approach + you isolate the complex construction code from the business logic of the product. But then, nothing wrong to not(!) us a pattern. If you think your code may not benefit from using a pattern then don't use it.
