This is a continuation of the earlier posts starting with this one: http://ravinote.blogspot.com/2020/09/best-practice-from-networking.html
There are several formats of metrics and monitoring data and generally, they are proprietary. Utilizing an external stack for these purposes via APIs helps alleviate the concerns from the storage service.
Virtually every service utilized from the infrastructure is a candidate for standardization and consistency so that one component/vendor in the infrastructure may be replaced with another with little or no disruption
There are several stack frames that a developer must traverse in order to find the code path taken by the execution thread and they don’t always pertain to layers but if the stack frames can get simpler for the developer, the storage product overall improves tremendously. This is not a rule but just a rule of thumb that the simpler the better.
As with all one-point maintenance code, there is bloating and complexity to handle different use cases from the same code. Unfortunately, developers don’t have the luxury to rewrite core components without a significant investment of time and effort. Therefore version 1 of the product must always strive for building it right from the get-go.
As use cases increase and the business improves, the product management pays a lot of attention to sustainable growth in the face of business needs. It is at this cusp of technology and business that the system architecture plays its best.
No comments:
Post a Comment