# Elastic Search for Frequent Location Updates
**URL:** https://discuss.elastic.co/t/elastic-search-for-frequent-location-updates/323542
**Category:** Elasticsearch
**Created:** [January 19, 2023, 7:32pm UTC](https://discuss.elastic.co/t/elastic-search-for-frequent-location-updates/323542 "2023-01-19T19:32:03Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@nsarvesh](https://discuss.elastic.co/u/nsarvesh)
#### Post date: [January 19, 2023, 7:32pm UTC](https://discuss.elastic.co/t/elastic-search-for-frequent-location-updates/323542/1 "2023-01-19T19:32:03Z")
Hi Team,
We are planning to build a calendar application with Location-based Search Capabilities. We want to store the user availability and the geolocation.
```auto
Eg:
{
User: "foo"
day: "Jan-19-2022"
availability: {09:00 to 10:00}
location: {lat, long},
User: "foo"
day: "Jan-19-2022"
availability: {11:00 to 12:00}
location: {lat, long}
}
```
However, we will display the results based on availability and location once the user has selected the desired day and location from UI/APIs. We need to remove his availability from the Elasticsearch. The rate of updates will be 500 transactions per second. Right now we are leveraging SQL. By moving to Elastic Search, what challenges might we encounter? We are clear that Elastic search is a good product for Search (Read heavy). Does it also support frequent updates? It will be great if you can share your thoughts on this approach. We are looking for both Ready & Write Heavy
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 16, 2023, 7:32pm UTC](https://discuss.elastic.co/t/elastic-search-for-frequent-location-updates/323542/2 "2023-02-16T19:32:50Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.