This is a tutorial to show the basic API usage of big queue, the source of this tutorial is here.
The interface of big queue is here, basically, it’s as simple as the queue interface we learned in data structure course in college, if you want to refresh the concept of queue ADT, here is the wikipeida link.
You can create(initialize) a new big queue in just one statement:
the first parameter is a directory you want to store the queue data file, the second parameter is the queue name. Now you have a reference to an empty queue.
To add or produce item into the queue, you just call the enqueue method on the queue reference, here we enqueue 10 numbers into the queue:
1 2 3 4 5
Note: the enqueue method only accept byte array data as input, if your object is not byte array data, you are responsible to convert your object into byte array first before enqueue, this is called serialization, when you dequeue later, you are also response to de-serialize the byte array data into your object format.
Now there are 10 items in the queue, and it’s not empty anymore, to find out the total number of items in the queue, call the size method:
The peek method just let you peek item at the front of the queue without removing the item from the queue:
To remove or consume item from the queue, just call the dequeue method, here we dequeue 5 items from the queue:
1 2 3 4
since the queue is a FIFO queue, the number dequeued will be in FIFO order: 0, 1, 2, 3, 4.
To remove all remaining items from the queue, just do like this:
1 2 3 4 5
Now the queue is empty again, to check it’s empty, just call isEmpty method:
Finally, when you finish with the queue, just call close method to release resource used by the queue, this is not mandatory, just a best practice, call close will release part of used memory immediately. Usually, you initialize big queue in a try block and close it in the finally block, here is the usage paradigm:
1 2 3 4 5 6 7
Now its your turn to play with the big queue, in this tutorial, I just used very small number of data, but actually the big queue can hold lage amount of data, the total size is only limit by your avaiable disk space, so just try to enqueue and dequeue as much data as you can imagine, also, please review test code of big queue to learn more advanced usage like multi-threads producing and consuming cases.