Showing posts with label load_balancers. Show all posts
Showing posts with label load_balancers. Show all posts

Tuesday, February 6, 2018

What is Proxy Server and Reverse Proxy Server?




I have been confused about this concept and get it mixed in my head. This video is short and simple.

In short, NGINX, HAPROXY is both load-balancer and reverse proxy. I think load-balancer and reverse-proxy means the same thing. But for now, I think I know what is going on. More about it later.
---------
If the above video still confuses you, you can read an excellent article here:
http://fullstackmastery.com/2017/06/17/5-ways-improve-server-architecture-nginx/

I have found all articles from this author to be well written and very clear. 

Saturday, December 16, 2017

System Design : High Availability & Scalability




LB's can also be used for HA but it is not default setup.



Veritas Scalable System Architecture



Database Clusters with HA & Scalibility


How to choose your Database for HA and Scalability? This talk from Neha is an excellent overview of what goes in choosing a appropriate database for your application. One thing she said that struck me is "Don't start with Scalibility".  She also talks about how NoSQL is not the solution for all your High Scalibility Problems. 

Here's her talk :




A related article based on Neha's talk is from Pinetrust : 


Database Sharding with Django


System Design : Load Balancing


Why Load Balancers?



Load Balancing with NGINX and IP_HASH vs Round-Robin


  • Setup Nginx Webserver (Could have used Apache Webserver also) and Nginx LB Configuration.




Load Balancing with Nginx (Haven't seen this video but with likes I figure this one could be a good one)



Friday, December 15, 2017

My Frustrations with System Design - Try2

Prologue : The aptness of this title is known to me only after I lost my first draft of this article by accident. Sure enough it is frustrating but let's focus on my deal with Software System Design. The second writeup will not have any dramatic entries I had in my first one but focus on MVP.

The knowledge of Big Data System Design has many components which can be happily group into various categories. My plan is to write one blog per category so that I understand them in more detail. This is to help me store all my learning at one place and help as a quick guidebook when times comes for Job Interviews or Project Execution.

The various categories that come to my mind so far are:-
  1. Data Orchestration : Hbase, Flume, Zookeeper
  2. Search : Solr, Elasticsearch
  3. Data Access :  Pig, Hive, Sqoop
  4. Hadoop : HDFS, MapReduce, Yarn
  5. Spark : Stream Processing 
  6. NoSQL Database : MongoDB, Casandra
  7. Load Balancers : HAProxy, Nginx
  8. Message Broker : RabbitMQ, Kafka
  9. High Availability & Scalability
  10. Container Orchestration Engine : Mesos, Kubernetes or Swarm


It's OK to be NOT-OK.

02/22/2021  Last week I was just un-productive and was not doing enough to talk about. I also wanted to say that weeks before the last, I ha...