# Do you think that expose aerospike service via REST API is good or not for production?

**URL:** <https://discuss.aerospike.com/t/do-you-think-that-expose-aerospike-service-via-rest-api-is-good-or-not-for-production/7921>\
**Category:** Rest Client\
**Created:** [October 13, 2020, 2:52am UTC](https://discuss.aerospike.com/t/do-you-think-that-expose-aerospike-service-via-rest-api-is-good-or-not-for-production/7921 "2020-10-13T02:52:44Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![qingtiaz](https://avatars.discourse-cdn.com/v4/letter/q/f07891/32.png) [@qingtiaz](https://discuss.aerospike.com/u/qingtiaz)\
**Post date:** [October 13, 2020, 2:52am UTC](https://discuss.aerospike.com/t/do-you-think-that-expose-aerospike-service-via-rest-api-is-good-or-not-for-production/7921/1 "2020-10-13T02:52:44Z")

</div>

As the title, if there is only one external IP can be used to expose aerospike service, do you think REST API is a good choice or not for production? need to consider latency/performance/HA.

Does anyone do so in production? any experience to share?

Thanks!

---

<div class="post-metadata">

**Author:** ![rbotzer](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/rbotzer/32/2114_2.png) [@rbotzer](https://discuss.aerospike.com/u/rbotzer)\
**Post date:** [October 19, 2020, 3:42am UTC](https://discuss.aerospike.com/t/do-you-think-that-expose-aerospike-service-via-rest-api-is-good-or-not-for-production/7921/2 "2020-10-19T03:42:43Z")

</div>

People are using the REST client in production, and it scales well. It’s attractive for two situations

1. Supporting applications written in languages that don’t have a [support client](https://www.aerospike.com/docs/guide/client_matrix.html) (also check the [Launchpad](https://www.aerospike.com/community/launchpad/#developer) for community-driven clients).
2. Replacing clients in multi-process deployments (such as FastCGI) with the multi-threaded REST client, which creates a lot less connections to the cluster (as opposed to a client per process).

If you’re going to compare something like Python in a multi-process setup versus REST, don’t just look at a single thread comparison. You want to run a realistic workload with multiple connections.