kdb+ on demand requires an always on internet connection to operate. Whilst the software is all installed on your local environment, kdb+ on demand sends ‘I’m alive’ packets out to our servers on a regular basis. These packets form the basis of billing for commercial users. kdb+ on demand will exit if it is unable to send these packets.
I don’t understand why they are still doing this. Given Dyalog is free for non-commercial use, while J is GPLv2, what is kdb+‘s edge to allow them to do this? I believe those tech people in banks are not all foolish, but I don’t see any appeal of kdb+.
I’d guess they have customers paying them well for it telling them it’s unlike any other solution. Then, they just protect their IP by default. With that mindset, we then have to convince the upper management that some other solution is better for them.
Your question is difficult to unpack. FWIW I’m not using kdb in a bank or finance setting.
kdb+ is “better than Dyalog and J” because it is faster, has better interfaces to C, and much better IO primitives. Software problems that involve a bunch of moving data around and then doing some processing on it are much easier in kdb+ than other solutions. I don’t know if this is what you want to talk about though.
kdb+ is also free for non-commercial use, and has been for some time. The new thing here is that the 64-bit version is free for non-commercial use.
I don’t understand why they are still doing this. Given Dyalog is free for non-commercial use, while J is GPLv2, what is kdb+‘s edge to allow them to do this? I believe those tech people in banks are not all foolish, but I don’t see any appeal of kdb+.
I’d guess they have customers paying them well for it telling them it’s unlike any other solution. Then, they just protect their IP by default. With that mindset, we then have to convince the upper management that some other solution is better for them.
Your question is difficult to unpack. FWIW I’m not using kdb in a bank or finance setting.
kdb+ is “better than Dyalog and J” because it is faster, has better interfaces to C, and much better IO primitives. Software problems that involve a bunch of moving data around and then doing some processing on it are much easier in kdb+ than other solutions. I don’t know if this is what you want to talk about though.
kdb+ is also free for non-commercial use, and has been for some time. The new thing here is that the 64-bit version is free for non-commercial use.