Skip to main content

Zuul Edge Server

Image
By

Zuul to Proxy your Microservices

A common challenge when building microservices is providing a unified interface to the consumers of your system. The fact that your services are split into small composable appsshouldn’t be visible to users or result in substantial development effort.
To solve this problem, Netflix created and open-sourced its Zuul proxy server. Zuul is an edge service that proxies requests to multiple backing services. It is “front door” to your system, which allows a browser, mobile app, or other user interface to consume services from multiple hosts without managing cross-origin resource sharing (CORS) and authentication for each one.
Spring Cloud has created an embedded Zuul proxy to ease the development of a very common use case where a UI application wants to proxy calls to one or more back end services. This feature is useful for a user interface to proxy to the backend services it requires, avoiding the need to manage CORS and authentication concerns independently for all the backends.
To enable it, annotate a Spring Boot main class with @EnableZuulProxy, and this forwards local calls to the appropriate service based on configuration defined in config files. For e.g /api/authservice/… request is forwarded to auth-service.
Zuul has different types of filters that enables us to quickly apply functionality to our edge service. These filters help us perform the following functions:
  • Authentication and Security.
  • Insights and Monitoring.
  • Dynamic Routing.
  • Stress Testing.
  • Load Shedding.
  • Static Response handling.
In our example we have defined routing rules (based of URL it forwards request to client-service), filter for logging request url, method and time of request.
We will be referring to two application which we have posted on different application.
Dependencies














Application.properties







Java Code:







Config class annotated with @EnableZuulProxy








Logging filter
















Config for Zuul routing rules & eureka service discovery. In config we have defined prefix as /api, routes for authclientservice.

In post Ribbon, Hysterix using spring feign we have defined authclientservice using ribbon and hysterix, which communicates to authservice service application.





We have prefix url as “/api”, then “/authclientservice” for authclientservice service application.
RESTful endpoint for authentication defined in authclientservice application is “/auth/login/authenticate”. Now for end client to access authentication end-point through endge-server will be “/api/authclientservice/auth/login/authenicate.

Start application

Application will get started at 6061 port.
Use below curl commands for authentication.




Request getting logged using ZuulFilter which we have defined.



 Request routed to authclientservice application


And at last request is served by authservice application.



Cheers – Happy learning 🙂
Ketan Gote

Labels:

Comments

Post a Comment

Popular posts from this blog

Redis Basic CRUD

By Anonymous
We have seen how to setup on your linux machine here , now we will see how to perform basic CRUD operations using Spring Data & Redis server We will be creating a simple application that would persist an employee information into redis database. You will be needing certain JARs like jedis.jar, spring-data-redis.jar etc details of which you can download and view at https://github.com/meta-magic/RedisCRUDexample.git  First of all we will be creating the Employee entity, plz note that we are using the Serializable interface which automatically mapps the objects against the key. Employee.java import java.io.Serializable ; public class Employee implements Serializable { private static final long serialVersionUID = - 8243145429438016231L ; public enum Gender { Male , Female } private String id; private String name; private Gender gender; private int age; public String getId () { return id; } public void setId ( String
Post a Comment
Read more

Function Point Analysis : ISO/IEC 20926:2009

By
This blog focuses on explaining the Function Point calculations. Software Sizing Background Function Point Rules for Counting FP Deep Dive - Function Point Analysis Case Study General Software Characteristics Details History - Measurement Methodologies Lines of Code (Oldest) Use case based Software Sizing IPFUG Function Point Analysis (ISO) Need for Software Sizing. Estimation and Budgeting Phasing Development Work Prioritization of Work Monitoring the Progress Bidding for Projects Allocating Testing Resources To measure and Manage Productivity Risk Assessment Software Asset Valuation CMMi Level 2 and 3 require that a valid sizing method be used. Software Sizing - Lines of Code The easiest and historically the most common method in Sizing Software project has been counting the number of lines of code and / or the number of screens. Advantages Automation of the counting process can be done Intuitive as the measurements are easily u
Post a Comment
Read more

Redis Installation Steps

By Anonymous
“ Redis is an in-memory key-value store known for its flexibility, performance, and wide language support” Inorder to install redis on your machine you need ubuntu 16.4 and a non-root user with sudo privileges to perform the administrative functions required for this process. Download and Extract the Source Code Create a tmp directory cd /tmp Download the latest stable version of Redis curl -O http://download.redis.io/redis-stable.tar.gz untar tar xzvf redis-stable.tar.gz Move into the Redis source directory structure that was just extracted cd redis-stable Build and Install Redis Now, we can compile the Redis binaries by typing make After the binaries are compiled, run the test suite to make sure everything was built correctly. You can do this by typing: make test This will typically take a few minutes to run. Once it is complete, you can install the binaries onto the system by typing: sudo
Post a Comment
Read more