# 🆕 Updates to the Glide + Make integration

**URL:** <https://community.glideapps.com/t/updates-to-the-glide-make-integration/67979>\
**Category:** General\
**Tags:** integration, make\
**Created:** [November 20, 2023, 9:45pm UTC](https://community.glideapps.com/t/updates-to-the-glide-make-integration/67979 "2023-11-20T21:45:51Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![david](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/david/32/62831_2.png) [@david](https://community.glideapps.com/u/david)\
**Post date:** [November 22, 2023, 2:14am UTC](https://community.glideapps.com/t/updates-to-the-glide-make-integration/67979/16 "2023-11-22T02:14:51Z")

</div>

Increment is not an atomic operation. The increment happens on the client, and the result is sent to the server. For atomic increment, you should use Call API with a service like Upstash that offers serverless redis (a database with first-class support for atomic increment). You can get a good result this way! We did it for PGA when they needed a distributed counter for their grandstands.

We’d like to offer atomic increment in Glide but it’s not a top request from customers yet.

---

_[View the full topic](https://community.glideapps.com/t/updates-to-the-glide-make-integration/67979)._
