# Glide App + MySQL

**URL:** <https://community.glideapps.com/t/glide-app-mysql/36805>\
**Category:** Project Showcase\
**Created:** [January 7, 2022, 12:48pm UTC](https://community.glideapps.com/t/glide-app-mysql/36805 "2022-01-07T12:48:17Z")\
**Posts on this page:** 1\
**Showing post:** 41

<div class="post-metadata">

**Author:** ![gvalero](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/gvalero/32/1037_2.png) [@gvalero](https://community.glideapps.com/u/gvalero)\
**Post date:** [May 13, 2022, 10:27pm UTC](https://community.glideapps.com/t/glide-app-mysql/36805/41 "2022-05-13T22:27:50Z")

</div>

Jeje, sorry for this “spam” Hani 🤣

Take a look at this another thread to know a little more about it:

> [@Is Glide suited for developing open-ended data apps?](https://community.glideapps.com/t/is-glide-suited-for-developing-open-ended-data-apps/36631):
>
> I see developers creating open-ended data apps, like social media, messaging apps. What puzzles me is that when the app is used by thousands of users, the data alone would break 25,000 records. What then? You can’t remove/archive data to save on storage. Consider 1000 users posting 5 records per month. In 5 months, the app will have over 25k records. In view of this restriction, I find Glide apps only good for internal, mid-size data uses. Am I understanding this correctly?

Feliz día!

---

_[View the full topic](https://community.glideapps.com/t/glide-app-mysql/36805)._