Implement LRU cache with increasing logical complexity and adding new steps for such cache.

1. Tell about a project that you did and a bit deep dive and things that could have been improved or were problematic and how did you overcome it or how would you approve it. 2. Given the following code: /** * Handles events * Tries to send them 5 times before deleting * For example: * * 12:00 * 12:02 * 12:04 * 12:08 * 12:16 */ public class EventsHandler { /** * Is triggered every minute 12:00, 12:01, 12:02, 12:03... * @param events event to save */ public void handle(List events) { } /** * Tries to save an event in DB * @param event * @return true = event was saved successfully, false = event wasn't saved * */ private boolean saveEvent(Event event) { return DBUtil.saveEventToDB(event); } } Method saveEvent, can sometimes return false for events to failed to be saved in the db. In case an event failed to be saved we need to store it somewhere and manage it, so in the next round (handle method runs every minute), it will run all the events that failed in the previous round. In short implement retries for failed events (including storing them somewhere). You can use whatever you want. Implement the handle method so it can manage and save