Use spring boot and thrift, zookeeper to create microservices

Spring Cloud is adapted to cloud services and is also suitable for enterprise informatization SOA construction. Spring boot is also a tool for the development of RESTful micro services. But for the intranet service, the call between service and service, spring does not deliberately encapsulate, perhaps they think it is not necessary, because already have thrift, ice and other powerful framework.

If you use the RESTful service provided by spring boot itself as a call between service and service, the efficiency is much lower, and the efficiency of thrift is about 100-1000 times that of restful. This article is a simple microservices framework based on the spring boot framework, combined with thrift and zookeeper, which uses thrift communication between services and services (thrift is both a means of communication and data compression).

This demo consists of three projects:

Cloud-thrift-server: Service Provider

Cloud-thrift-interface: interface and Transport object definition

Cloud-thrift-client: Service Caller

Open Source code address: Http://git.oschina.net/zhou666/spring-cloud-7simple

1) Establish the Thrift Interface definition document

namespace Java Cloud.simple.service

struct Userdto {

1:I32 ID

2:string username

}

Service UserService {

Userdto GetUser ()

}

After the interface is defined, use the Thrift command to generate the corresponding Java file, which generates two files, Userservice.java and Userdto.java, respectively, put these two files into the Cloud-thrift-interface project, because the client also needs this interface definition.

2) Implement Thrift Service Registration

The interface needs to be implemented on the provider side of the service, and the implementation class is registered to the thrift server.

Userservice.processor Processor = new Userservice.processor (

New Userserviceimpl ());

Tserver Server = new Tthreadpoolserver (New Tthreadpoolserver.args (

Tservertransport ()). Processor (processor));

Userserviceimpl is an interface implementation class that registers its gold tserver.

After registering the service, you need to start tserver, which obviously needs to be started in the thread.

Executor.execute (New Runnable () {

@Override

public void Run () {

Tserver (). serve ();

}

});

3) Registration of service name using zookeeper

Above is the registration of the specific service execution class, this step is to register the service instance into zookeeper, in order to achieve load balancing. Enables clients to select services based on the list of service instances to execute. Of course, there is only the IP of the server where the service is registered, because the client knows the IP and knows the service under that IP.

String ServicePath = "/" +servicename;//root node path

Zkclient zkclient = new Zkclient (serverlist);

Boolean rootexists = Zkclient.exists (ServicePath);

if (!rootexists) {

Zkclient.createpersistent (ServicePath);

}

InetAddress addr = null;

try {

addr = Inetaddress.getlocalhost ();

} catch (Unknownhostexception e) {

E.printstacktrace ();

}

String IP = addr.gethostaddress (). toString ();

String serviceinstance = system.nanotime () + "-" + IP;

Register current service

Zkclient.createephemeral (ServicePath + "/" + serviceinstance);

SYSTEM.OUT.PRINTLN ("Services provided are:" + ServicePath + "/" + serviceinstance);

Note that using Zkclient.createephemeral to create a temporary node, if the server goes down, the temporary node will be purged so that the client will not select the service on the server when it accesses.

4) List of client Update Services

The client needs to be able to listen to changes in the service list and load balance in a timely manner, and we listen to changes in the list of services as follows:

Registering for event monitoring

Zkclient.subscribechildchanges (ServicePath, New Izkchildlistener () {

@Override

public void Handlechildchange (String parentpath,

List<string> currentchilds) throws Exception {

instance (path) List: When a service instance goes down, the instance is subtracted from the instance list

for (String instancename:currentchilds) {

Without the service, establish the service

if (!servicemap.containskey (instancename)) {

Servicemap.put (Instancename,createuserservice (instancename));

}

}

For (map.entry<string, userservice.client> entry:serviceMap.entrySet ()) {

The service has been removed

if (!currentchilds.contains (Entry.getkey ())) {

Servicemap.remove (Entry.getkey ());

}

}

System.out.println (Parentpath + "event trigger");

}

});

With a list of services, clients can use load balancing when invoking a service, using the simplest random method:

Public Userservice.client Getbalanceuserservice () {

Map<string, userservice.client> Servicemap =zookeeperconfig.servicemap;

Obtaining a service instance in a load-balanced manner

For (map.entry<string, userservice.client> entry:serviceMap.entrySet ()) {

SYSTEM.OUT.PRINTLN ("Alternative Services:" +entry.getkey ());

}

int rand=new Random (). Nextint (Servicemap.size ());

string[] Mkeys = Servicemap.keyset (). ToArray (New String[servicemap.size ());

Return Servicemap.get (Mkeys[rand]);

}

The end of this article, specifically see the code, in addition, did not know thrift and zookeeper friends, do not be frightened by them, in fact, they are very lightweight technology, very easy to get started, which may be their popular reason.

Use spring boot and thrift, zookeeper to create microservices