Q: give me java code with output for this three scenario with 3 ways (lock - ArrayBlokingQueue -Bounded Buffer) in bank website

scenario 1 : lock

scenario 2 : ArrayBlokingQueue

scenario 3 : Bounded Buffer

For the bank website scenario, let's consider the following scenario: Scenario 1: Producer: Bank teller Consumer: Customer Buffer: Bank account In this scenario, the bank teller acts as a producer by making transactions on behalf of the customer and updating the customer's bank account (buffer) accordingly. The customer acts as the consumer by checking their account balance and transaction history. To implement this scenario, we can use the Lock and Condition interface to synchronize the access of the bank account by the bank teller and customer. The lock will ensure that only one thread (either bank teller or customer) can access the account at a time, while the condition will be used to signal the customer that the account has been updated by the bank teller. Scenario 2: Producer: Customer Consumer: Bank teller Buffer: Customer request queue In this scenario, the customer acts as a producer by making requests (such as account balance check or transfer funds) on the bank website. These requests are stored in a customer request queue (buffer) for the bank teller to process. The bank teller acts as the consumer by processing the requests from the queue and updating the customer's account accordingly. To implement this scenario, we can use the ArrayBlockingQueue data structure to store the customer requests and ensure that only one bank teller can access the queue at a time. Scenario 3: Producer: Customer Consumer: Bank Buffer : customer transaction history In this scenario, the customer acts as the producer by making transactions on the bank website, which are then recorded in their transaction history (buffer). The bank acts as the consumer by processing the transactions and updating the customer's account balance. To implement this scenario, we can use the Bounded Buffer pattern to ensure that the size of the transaction history buffer does not exceed a certain limit. This will help prevent the buffer from growing too large and consuming excessive memory