# Any chance of server-side Boolean operations like intersection?

**URL:** <https://forums.foundationdb.org/t/any-chance-of-server-side-boolean-operations-like-intersection/445>\
**Category:** FoundationDB Core\
**Created:** [May 21, 2018, 10:01am UTC](https://forums.foundationdb.org/t/any-chance-of-server-side-boolean-operations-like-intersection/445 "2018-05-21T10:01:41Z")\
**Posts on this page:** 1\
**Showing post:** 9

<div class="post-metadata">

**Author:** ![alloc](https://sea1.discourse-cdn.com/foundationdb/user_avatar/forums.foundationdb.org/alloc/32/9_2.png) [@alloc](https://forums.foundationdb.org/u/alloc)\
**Post date:** [May 22, 2018, 4:57pm UTC](https://forums.foundationdb.org/t/any-chance-of-server-side-boolean-operations-like-intersection/445/9 "2018-05-22T16:57:56Z")

</div>

> [@cloudspeech](#):
>
> Run additional client(s) in each machine of each FDB cluster, implement ‘server-side’ programming-as-layers there while profiting from data locality and machine-local network speed (e.g. Unix domain sockets), and use intra-cluster messaging between those clients to coordinate who does what.

I think there are a few more details on what such a scheme would look like in this thread: [Coprocessors or modules](https://forums.foundationdb.org/t/coprocessors-or-modules/183)

It also sounds like as a constructive proof that you could do that that Wavefront already have such a system set up. It is probably the easiest way to do something like what you’ve described without a new API to push down operations.

---

_[View the full topic](https://forums.foundationdb.org/t/any-chance-of-server-side-boolean-operations-like-intersection/445)._