Required logic description and Pseudo-code

Question

  Required logic description and Pseudo-code of given scenario

 

Scenario 2:

 

To help combat the issue with the orders being overwritten, it is decided that an Order Queue project should be developed. The following are the basic requirements for the project:

• Each user can select their next order to work on from a queue of available orders to work on

• Once an order is selected by one user, it cannot be selected by any other user

• Once an order is selected, it no longer appears within the order queue

• Once a user finishes making modifications to an order, they submit the order to their supervisor for approval.

• Each user is able to see a listing of orders they specifically modified that are awaiting approval from their supervisor

Questions:

1) Describe how a services based architecture could be used to implement the Order Queue

a. What endpoints are needed? (include naming examples):

2) Describe potential database structures and relations that would be needed to accomplish the Order Queue

3) Are there any other solutions besides a queueing service that could solve the core issue?