Hello , We are planning to drop the data in typesense using alias approach The steps we are plannign to follow are 1) new collection - newprodcollection 2) migrate data to this new collection newprodcollection 3) drop the original collection - prodcollection 4) create a alias to this new collection newprodcollection with alias name as exiting collection name prodcollection Can you please help us whether this will be an ideal approach with least downtime and mimimal changes for the consumers who are using this typesense service already

You can create an alias first and then migrate your app to use that alias and then make the alias to point to the new collection later on once the new collection is populated.

But since its used in multiple places in our app , and this activity of restoring data will happen in future also , So we dont want to change the url and payload on app side

Then there will be a small time period between steps 3) and 4) above which can cause requests to fail. The typical usecase of an alias is to do the switch without any such downtime.

Ok got it , yes we will be notifying on the small downtime ,