You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Distribution of high load to independent servers *(Horizontal Scaling)
Possible Proposition
Distributing load to different servers would be great step for Haaukins project, based on this, I included simple diagram which shows how it can be visualized.
In the diagram, service instances are micro services which are responsible for spinning up resources on different servers, they should provide a feedback about server *(Memory, CPU usage, network bandwidth) to evenly distribute the incoming requests.,
REST API is optional, it can be kept as gRPC between micro services.
It would be beneficial to keep the discussions documented as well, to do not repeat ourselves.
Possible Service Registries
Apache Zookeeper - is a centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services.
Consul - is a multi-networking tool that offers a fully-featured service mesh solution that solves the networking and security challenges of operating microservices and cloud infrastructure (multi-cloud and hybrid cloud)
etcd - is a distributed reliable key-value store for the most critical data of a distributed system
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Problem
Distribution of high load to independent servers *(Horizontal Scaling)
Possible Proposition
Distributing load to different servers would be great step for Haaukins project, based on this, I included simple diagram which shows how it can be visualized.
In the diagram, service instances are micro services which are responsible for spinning up resources on different servers, they should provide a feedback about server *(Memory, CPU usage, network bandwidth) to evenly distribute the incoming requests.,
REST API is optional, it can be kept as gRPC between micro services.
It would be beneficial to keep the discussions documented as well, to do not repeat ourselves.
Possible Service Registries
Beta Was this translation helpful? Give feedback.
All reactions