Geek Answers Handbook

Designing a REST API with req / resp and pub / sub requirements

I am currently developing a REST interface for a distributed system. This is a client / server architecture, but with two messaging patterns:

  • req / resp: the most RESTful approach, it will be a CRUD interface for accessing / creating / modifying / deleting objects on the server.
  • pub / subs: this is my main doubt. I need a server to send asynchronous notifications to the client as soon as possible.

Web Search I discovered that one of the solutions could be to implement REST servers on the server and client: Publish / subscribe to the REST-HTTP Simple Protocol web services architecture?

Another alternative would be to implement blocking-REST, and therefore the client does not need to listen on a specific port: Using REST request blocking to implement publishing / subscription

I would like to know what options you would consider for implementing an interface like this. Thanks!

+7
rest publish-subscribe
source share

No one has answered this question yet.

See similar questions:

10
Using REST Request Blocking to Implement Publish / Subscribe

or similar:

731
REST API / web service security guidelines
364
RESTful Search URL Design
62
Node.js, Socket.io, Redis pub / sub high volume, low latency difficulties
27
Messy of Messages: Pub / Sub vs Multicast vs Fan Out
10
Redis pub / sub on rails
6
Problems with Inverted PUB / SUB with ZeroMQ
one
Redis pub / sub architecture returns 0 when published to chanel
one
Verifying PUB / SUB pattern data retrieval
0
How to implement an asynchronous response request in a REST-based web service
0
Redis Pub / Sub does not support messages

More articles:


All Articles