NGINX

I use NGINX because of its efficient use of resources, straightforward configuration, and well-targeted feature set. It also has an excellent track record with regard to security.

I use NGINX because it is fast, flexible, lightweight in terms of memory and CPU usage, and it's open source. I love the fact that it is easy to configure and that there is such a large community of users who are helpful and have written great tutorials on many nginx topics.

I use Kong because of following reasons. (1) reliability (2) great community supports (3) ease of using plugins (4) surfaced free benefits of NGINX

We've switched our static pages from NGINX to HAProxy. Using stick tables, traffic rules and ACLs allowed us to have better control over our traffic while load balancing. Also, performance gain with latency, threads, and processes.

We chose AWS because, at the time, it was really the only cloud provider to choose from.

We tend to use their basic building blocks (EC2, ELB, Amazon S3, Amazon RDS) rather than vendor specific components like databases and queuing. We deliberately decided to do this to ensure we could provide multi-cloud support or potentially move to another cloud provider if the offering was better for our customers.

We’ve utilized c3.large nodes for both the Node.js deployment and then for the .NET Core deployment. Both sit as backends behind an NGINX instance and are managed using scaling groups in Amazon EC2 sitting behind a standard AWS Elastic Load Balancing (ELB).

While we’re satisfied with AWS, we do review our decision each year and have looked at Azure and Google Cloud offerings.

#CloudHosting #WebServers #CloudStorage #LoadBalancerReverseProxy