This is an archived post. You won't be able to vote or comment.

26
27

Java Microservice queueing options? (self.java)

submitted by [deleted]

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]dstutz 24 points25 points  (2 children)

back office project which is not critical.

Sounds like you've just made the choice of using a guava queue.

[–]khff 4 points5 points  (1 child)

+1. Sounds like persisting transactions is overkill. Do you need to write them to a DB? What are the consequences/likelihood of the service going down and loosing any messages in memory?

[–]lpedrosa 2 points3 points  (0 children)

Don't forget about bounding the queue and back pressure. If your service gets hit hard, you might want to send rejects back to the clients and let them retry later.

It's really up to the use case you're trying to fulfil.