This is a continuation of the earlier posts starting with this one: http://ravinote.blogspot.com/2020/09/best-practice-from-networking.html
The statistics may be stored in a container belonging to the system. Since the system containers are treated differently from the user, they will need to be serviced separately.
Application and system both publish statistics. They may both need to be the source of truth for their data
When the same container is replicated in different zones, there is a notion of local and remote. Only one of them is designated as primary. The remote is usually secondary
The number of applications using the same network is usually not a concern. The ability to serve them with different quality of service makes it special.
When an application wants to change the workload on the network, architects to prefer to swap a networking product with something more suitable. However, a performance engineer can circumvent the approach with optimizations that leverage the existing product. It is always a good practice to give this a try.
System architecture holds in favor of changing business needs from the smallest components to the overall topology. However, it is rather centralized and sometimes using another instance of the topology with customizations can mitigate the urgency while giving ample time for consolidation.
The use of networking products also depends on the developer community. Many products such as software-defined stacks and container orchestration framework have generated greater acceptance by endearing the product to developers.
No comments:
Post a Comment