# Embedded Use

**URL:** <https://discuss.aerospike.com/t/embedded-use/1436>\
**Category:** Requests\
**Created:** [June 26, 2015, 12:20pm UTC](https://discuss.aerospike.com/t/embedded-use/1436 "2015-06-26T12:20:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![sirinath](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/sirinath/32/260_2.png) [@sirinath](https://discuss.aerospike.com/u/sirinath)\
**Post date:** [June 26, 2015, 12:20pm UTC](https://discuss.aerospike.com/t/embedded-use/1436/1 "2015-06-26T12:20:10Z")

</div>

With a view to reduce client to server latencies is it possible to release an embeddable version of the application?

---

<div class="post-metadata">

**Author:** ![ManuelSchmidt](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/manuelschmidt/32/424_2.png) [@ManuelSchmidt](https://discuss.aerospike.com/u/ManuelSchmidt)\
**Post date:** [June 27, 2015, 10:02am UTC](https://discuss.aerospike.com/t/embedded-use/1436/2 "2015-06-27T10:02:40Z")

</div>

Do you want to run AS-client and AS-server on the same node or your App-server and the AS-server?

Even though AS does clearly not recommend running App- and DB-server on the same node, I see many small projects using exactly this 1-server setup. It sounds interesting to offer a bypass of the slow TCP-stack in such scenarios. Redis is offering a unix domain sockets-mode, which does exactly that, if my interpretation is right. Maybe that would be an easier option than maintaining an embedded version.

Performance-wise, this should be significantly faster than standard TCP (even on localhost). @see [TCP loopback connection vs Unix Domain Socket performance - Stack Overflow](http://stackoverflow.com/questions/14973942/performance-tcp-loopback-connection-vs-unix-domain-socket)