Hello @Debashis Jena,
because the CosmosDB route for IoT Hub is still in preview, you are looking for a production-ready alternative.
You need to put some logic between the IoT Hub and CosmosDB so the obvious alternative is Azure Functions.
Azure Functions can be seen as 'code logic with an endpoint'.
The logic is triggered by some external event, here it would be a telemetry message coming from an IoT Hub.
Check out the IoT Hub trigger for Azure Functions.
Once the telemetry is read in code, you need to persist it in CosmosDB.
You could either program against CosmosDB using the available SDKs or use the Azure Function Output binding.
The output binding is more convenient, I suppose.
Notice it is recommended to use a separate consumer group for your Azure Function trigger (see the comments in the other question).
I recommend starting with the Azure Function Consumption plan and start calculating when it's more cost-effective to switch over to a 'self-hosted' service plan. Especially with high volumes or heavy computing, this is recommended. You are also more in control regarding response times when the service plan is not based on the consumption plan.
If the response helped, do "Accept Answer". If it doesn't work, please let us know the progress. All community members with similar issues will benefit by doing so. Your contribution is highly appreciated.