It is important for the architecture to be fast, flexible, easy to scale, and simple. Image by Jimmy Soh on When Architecture Becomes Complex An example of such architecture can look like this. The problems come when you build an application that consists of dozens of backend services regularly communicating with each other. REST works well for most cases, especially if you build a monolithic application that does not have complex within-application communication.

They prefer REST to alternative approaches such as RPC and GraphQL. When it comes to micro-services, ThriftвЂ™s rapid binary serialization and countless languages makes it a no-brainer.Usually, whenever somebody wants to start building an HTTP API for their website, they pretty much exclusively use REST as the go-to architectural style. REST is perfect for simple web APIs, but its heavy serialization makes it inappropriate for internal company wide services. Thrift and REST both have their pros and cons. The y-axis is the amount of time in seconds to call the service a 1M times. The above graph shows the performances of the same service implemented using different protocols including our two competitors, Thrift and REST. The binary encoding makes it easier to send large amounts of data over internal networks. For example, the same service can communicate using a binary protocol, XML or even JSON. Here is an example of a Thrift service that would be used to monitor GitHub projects:Д¬reateResult create ( 1 : Project proj ) }ДЄn additional benefit of Thrift is the support for multiple protocols.

Use a Thrift server to implement the service.

Generate a server stub and implement it.Generate client stubs in any desired languages.The workflow to create a service is the following: ThriftвЂ™s infrastructure allows to create cross-language services and currently supports almost 20 languages (C++, Java, JavaScript, etc.). We can also cite HBaseвЂ™s Thrift interface. For example, HiveServer2 is built using Thrift. It is nearly impossible to deploy a Big Data infrastructure without coming across Thrift. Apache ThriftДЄpache Thrift was originally developed at Facebook, it was open sourced in 2007, registered in the Apache incubator program in 2008 and became a top level Apache project in 2009. Indeed, the serialization and deserialization of these protocols and formats can be prejudicial for overall speed. However, the stack composed of REST, HTTP and JSON is not optimal for high performances required for internal data transfer. Most of the web relies on HTTP and REST for communication and they both have proven their worth, reliability and scalability over the years. With such characteristics, REST systems aim at fast performances, reliability, and the ability to be modified without affecting the system as a whole. It allows communication between web resources (computers, web browsers, etc.) respecting a set of constraints: REST, for Representational State Transfer, was defined in 2000 by Roy Fielding. An important part of the presentation covered how Apache Thrift compares with REST and gRPC in term of velocity. The focus was that Thrift is very fast and how it applies to microservices. I had the opportunity to follow a presentation made by Randy Abernethy and Jens Geyer of RM-X, a cloud native consulting company, about the use of Apache Thrift in the building of high performance microservices. Adaltas recently attended the Open Source Summit Europe 2017 in Prague.

Thrift idl