Because kdb+/q has such few datatypes and you can't define anymore, it's very easy:

  q) .j.k"[2.2, 3.5]"
  2.2 3.5

Serialization is also trivial:

  q) .j.j 0 1 2 3
  "[0,1,2,3]"

In general, sending stuff across memory boundaries (files, network, ram, etc) is exceedingly trivial in kdb+/q. To execute a function on a remote server, simply connect to a server and send across the call to the handle. For example, to send synchronously compute 1+1:

  q) h:hopen `::6666
  q) h(+;1;1)
  2

You can send over anything you want, even the entire source code of program to be executed! This is a really flexible environment, where you can create really powerful app-engines. All members of a cluster can send code, data, and messages to any other node, async or sync.

Much like Common Lisp and SmallTalk, you can easily connect to production nodes and modify code while the service is running.

It's rare to find such a dynamic, flexible, and interpreted language that also has world class performance, even often beating hand written C. Combined with an integrated database, you get a distributed system that can't be beat, at least performance-wise. And the craziest thing is that all of this sits in at 650kb executable with libc has the only dependency. And all probably in less lines of code than a simple javascript webapp!