![]() Unlike the recent microservice trend, most applications were the traditional monolithic 3-tier application. Plus, JavaScript started to really take off in browsers and it was much easier to deal with REST, than it was SOAP. It was easy to use URLs to spit out some text. People were using SOAP, RMI, CORBA, and EJBs. ![]() When Roy Fielding proposed REST in 2000, REST was a kale sandwich in a field of much worse tasting sandwiches. How did this come to pass? Well, at the time REST emerged, there were even worse options. That is not a good thing - in fact, it’s a very bad thing. Representational State Transfer (REST) has become the de facto standard for communicating between microservices. It is a connection-oriented, message-driven protocol with built-in flow control at the application level. Open source RSocket is designed for services. We need a modern material to replace HTTP for creating modern services.For data that is sent via streams, application flow control is needed. Engineers want the ability to process data as it comes - they want to be able to stream data.Some of the things we would want in a protocol designed for microservice communication include binary serialisation, bi-directional communication, multiplexing, and the ability to exchange metadata.Not being easy to read is a tooling issue. An often-cited reason to use RESTful web services is that it’s easy to debug because its “human readable”. REST was implemented as a hack on top of HTTP. ![]() The author argues that is not a good thing - in fact, it’s a very bad thing, particularly for microservice communication
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |