Good Approach for Air Hotel Car booking without involving DB

Question

Hi Team,

In our application, we are rearchitecting a structure in the existing application flow

Current Flow

When the user tries to book for Air Hotel Car from the Search page, we do concurrent API requests in a particular area and store the data in SQL.

Once the user goes to respective list pages for booking,we show respective content for that request

For an example

1. API hit Search

• Air =100 flights
• Hotel=90 Hotels
• Car =80 Cars

2. We store all the data in SQL.

3. The user reaches Air page shows 100 flights, hotel page show 90 hotels & car page show 80 cars

4. Once the user select air, hotel, and car we show the payment option

New Flow

When the user searches for Air Hotel Car from the Search page, we do concurrent API requests in a particular area but don’t want to store data in DB (need to store in memory, session local storage)

The main motive is to remove dependency to store data in DB (SQL /NoSQL). Bcz data is required only for a particular search. We are dumping the payload for logging purposes but we don’t need an extra hit to store in DB

Any idea, any suggestions?