Reading Time: 5 minutes
In this tutorial, we discuss the Apache .htaccess file and the many ways it can be modified and configured to suit your specific needs. We will be reviewing how to configure .htaccess redirects, rewrites, and add other customizations.
Continue reading “How to Configure a .htaccess Redirect”
Let’s say you have decided to change domain names or have one web address on your site that you want to redirect to a completely different location. Using a .htaccess redirects, you can send visitors to the new page or site automatically!
Reading Time: 5 minutes
Today we will demonstrate how to install Envoy Proxy on Ubuntu.
Continue reading “How to install Envoy Proxy on Ubuntu 18”
Envoy is a high performance C++ distributed proxy designed for single services and applications, as well as a communication bus and “universal data plane” designed for large microservice “service mesh” architectures. Built on the learnings of solutions such as NGINX, HAProxy, hardware load balancers, and cloud load balancers, Envoy runs alongside every application and abstracts the network by providing common features in a platform-agnostic manner.
Reading Time: 4 minutes
cURL is a Linux command that is used to transfer multiple data types to and from a server. It operates utilizing the libcurl library, which allows it to use the following protocols to move information:
Continue reading “Fun With Curl”
Reading Time: < 1 minute
What is a Service Mesh?
A service mesh is a layer of communication and control between applications or microservices and the network stack they typically communicate over. This layer controls communication and helps microservices share data. This service-to-service interaction is governed by logic built into the service mesh layer. Simply put, microservices are small or partial applications, or individual functions, and the network stack is the physical networking layer.
How is a Service Mesh Achieved?
Typically, a service mesh is implemented via sidecars. These sidecars are usually attached to every microservice on your network. The service mesh abstracts communication between microservices into these sidecars and the sidecars communicate with one another in a mesh topology.
Because most modern apps are now smaller than their predecessors, they have shrunken the communication logic written into each app, microservice, function, etc. With one or two microservices, or maybe even a dozen, the communication logic generally isn’t difficult to deal with. At scale, or when you have hundreds of such apps, a service mesh can be thought of as ‘required’.
So, a service mesh consists of the following components:
- A communication layer of control between apps or microservices
- The network stack they typically communicate over
- Abstracts communication and implements ‘sidecars’ with every microservice