Enhance Application Reliability and Scalability with Internal Load Balancing Reviews

Heriyanto G. · Reviewed over 1 year ago

Fikri F. · Reviewed over 1 year ago

Jovita S. · Reviewed over 1 year ago

i had to restart the lab, it was shutdown. the reason is the ip of the loadbalancer 10.10.30.5:80 when i created the loadbalancer that ip was used by a vm instance in the instanceGroup2. you probably should change it to 10.10.30.15 to avoid conflict. i dont know why the instance group scaled to 5vms the first time i didnt send any trafic so the 10.10.30.5 was already taken by one of the instances

Mohamed Souhayel M. · Reviewed over 1 year ago

Lakkakula C. · Reviewed over 1 year ago

Aashish P. · Reviewed over 1 year ago

Moises Andre A. · Reviewed over 1 year ago

Drexler A. · Reviewed over 1 year ago

alejandro o. · Reviewed over 1 year ago

Deva A. · Reviewed over 1 year ago

Jesaya Fernando N. · Reviewed over 1 year ago

Juan D. R. · Reviewed over 1 year ago

Rania N. · Reviewed over 1 year ago

Hangxu L. · Reviewed over 1 year ago

Mohmmed Jabir H. · Reviewed over 1 year ago

mohammed M. · Reviewed over 1 year ago

Kailash S. · Reviewed over 1 year ago

Bushra D. · Reviewed over 1 year ago

ARDHIA PRAMESTI REGITA C. · Reviewed over 1 year ago

Shaily S. · Reviewed over 1 year ago

Lisha K. · Reviewed over 1 year ago

Ayush V. · Reviewed over 1 year ago

Devesh B. · Reviewed over 1 year ago

Berlian Syiffa Ardana R. · Reviewed over 1 year ago

Azad Asanali A. · Reviewed over 1 year ago