Skip to content

Phase 3.1 Project Proposal

Jump to bottom
Rutvik Parvataneni edited this page Apr 11, 2020 · 11 revisions

Implementation of Service Mesh Technology

Problem statement

So we would focus on deep - diving into and exploring the Service Mesh Technologies (Istio, LinkerD & Envoy Proxy). Use it's capabilities to solve our problems.

Although our framework is currently being deployed on a Kubernetes cluster that offers in-built load balancing capabilities, we are experiencing unexplained failures. When designing our microservice architecture and investigating related problems, we found that much of our time was focused on finding or interpreting a problem rather than solving it in practice.

Our Problems ::

  • Traffic Distribution - Have to come up with an intelligent system to control the flow of traffic between the various services.

  • Load Balancing - Have to work on an optimized technique for our application.

  • Logging - Able to log the performed actions , can be helpful in detecting cause of failure. Debugging the errors would be quick.

  • Secure service-to-service communication - The communication between microservices is not encrypted and thus increasing the security vulnerability of the web application.

Proposed Solution

As mentioned above , we have planned to use the Service Mesh Technologies using Istio.

  • It would make our application visible by providing the logging. Log the communication between multiple services.

  • Help us control the traffic load between multiple micro-services.

  • Help us add extra security by providing Certificate Management.

Clone this wiki locally