Niyazi ÇAPAR

"Netflix #Eureka is a service registry. It provides a REST API for managing service-instance registration and for querying available instances.

There are two main service discovery patterns: client-side discovery and server-side discovery."

"There are several binary formats to choose from. If you are using Thrift RPC, you can use binary Thrift. If you get to pick the message format, popular options include ProtocolBuffers and Apache Avro."

"Consequently, you might want to consider using a binary format"

"A downside of using a text-based message format is that the messages tend to be verbose."

"There are two main kinds of message formats: text and binary. Examples of text-based formats include JSON and XML."

"Even if you are writing your #microservices in a single language today, it’s likely that you will use other languages in the future."

"If you are using a messaging system or REST, you get to pick your message format."

"Thrift also gives you a choice of transport protocols including raw TCP and HTTP. Raw TCP is likely to be more efficient than HTTP. However, HTTP is firewall-friendly, browser-friendly, and human-friendly."

"Thrift supports various message formats: JSON, binary, and compact binary."

"You use the Thrift compiler to generate client-side stubs and server-side skeletons. The compiler generates code for a variety of languages including C++, Java, Python, PHP, Ruby, Erlang, and Node.js."

Apache Thrift is an interesting alternative to REST. It is a framework for writing cross language RPC clients and servers. Thrift provides a C-style IDL for defining your APIs."

"Others, such as RAML, require you to use a separate specification such as JSON Schema. As well as describing APIs, IDLs typically have tools that generate client stubs and server skeletons from an interface definition."

"Some IDLs, such as Swagger, allow you to define the format of request and response messages."

" • It directly supports request/response-style communication. • HTTP is, of course, firewall-friendly. • It doesn’t require an intermediate broker, which simplifies the system’s architecture. "

"• HTTP is simple and familiar. • You can test an HTTP API from within a browser using an extension such as Postman,or from the command line using curl (assuming JSON or some other text format is used)."

"There are numerous benefits to using a protocol that is based on HTTP: "

"Today it is fashionable to develop APIs in the RESTful style. REST is an IPC mechanism that (almost always) uses HTTP."