Kdb+ and Python: EmbedPy and PyQ
1–10 of 40 posts
Re: Kdb+ and Python: EmbedPy and PyQ
#2the idea that I could seamlessly move data between python and kdb+ is making me salivate. Please, make this work well and lower the cost-barrier to using kdb+ and I think you'd see this become the defacto "stack" for many database setups.
Re: Kdb+ and Python: EmbedPy and PyQ
#3I've never quite understood why banks still opt for kdb when (a) hiring staff is ridiculously difficult/expensive and (b) there are so many other cheaper alternatives available. They literally have a strangle hold on every eFX desk in London, and I cannot really figure out why!
Re: Kdb+ and Python: EmbedPy and PyQ
#4I've never quite understood why banks still opt for kdb when (a) hiring staff is ridiculously difficult/expensive and (b) there are so many other cheaper alternatives available. They literally have a strangle hold on every eFX desk in London, and I cannot really figure out why!
Maybe you're wrong about (b)?
Sure, I could cobble something about as fast and functional out of postgres, C, awk, and a bunch of other things, but it'd certainly cost more just in developer time than kdb.
Re: Kdb+ and Python: EmbedPy and PyQ
#5I've never quite understood why banks still opt for kdb when (a) hiring staff is ridiculously difficult/expensive and (b) there are so many other cheaper alternatives available. They literally have a strangle hold on every eFX desk in London, and I cannot really figure out why!
Maybe you're wrong about (b)? Sure, I could cobble something about as fast and functional out of postgres, C, awk, and a bunch of other things, but it'd certainly cost more just in developer time than kdb.
Your comment made me chuckle. In fact, made me immediately think you were employed by Kx at some point; your profile confirmed this was the case!
I think Kx has built a wonderful business, but as an ex MD at a bulge bracket bank, I would not sanction its use any more. It is expensive, and it's difficult to hire good people to work with it (not every guy with kdb on their CV is great). The product is good, but so are many open source offerings, which are now matching it both in terms of performance and flexibility. Plus hiring good people is significantly easier and cheaper.
Re: Kdb+ and Python: EmbedPy and PyQ
#6Earlier quoted context omitted.
Maybe you're wrong about (b)? Sure, I could cobble something about as fast and functional out of postgres, C, awk, and a bunch of other things, but it'd certainly cost more just in developer time than kdb.
Your comment made me chuckle. In fact, made me immediately think you were employed by Kx at some point; your profile confirmed this was the case! I think Kx has built a wonderful business, but as an ex MD at a bulge bracket bank, I would not sanction its use any more. It is expensive, and it's difficult to hire good people to work with it (not every guy with kdb on their CV is great). The product is good, but so are…
As an ex-MD you also know that banks used to not be too price sensitive, so they didn't mind paying a lot for some Kx experts.
Of course, these days, with revenues being squeezed, that's changed.
Re: Kdb+ and Python: EmbedPy and PyQ
#7I like it when kdb is mentioned because then I can post this link: https://github.com/KxSystems/kdb/blob/master/c/c/k.h#L96
It's one of my all-time favorites. A window into a certain type of mind.
Re: Kdb+ and Python: EmbedPy and PyQ
#8Earlier quoted context omitted.
Your comment made me chuckle. In fact, made me immediately think you were employed by Kx at some point; your profile confirmed this was the case! I think Kx has built a wonderful business, but as an ex MD at a bulge bracket bank, I would not sanction its use any more. It is expensive, and it's difficult to hire good people to work with it (not every guy with kdb on their CV is great). The product is good, but so are…
As an ex-MD you also know that banks used to not be too price sensitive, so they didn't mind paying a lot for some Kx experts. Of course, these days, with revenues being squeezed, that's changed.
Agree, price is a much bigger factor now.
Re: Kdb+ and Python: EmbedPy and PyQ
#9I've never quite understood why banks still opt for kdb when (a) hiring staff is ridiculously difficult/expensive and (b) there are so many other cheaper alternatives available. They literally have a strangle hold on every eFX desk in London, and I cannot really figure out why!
huh, so what do i need to learn to be one of these ridiculously expensive people working w/ kdb?
Re: Kdb+ and Python: EmbedPy and PyQ
#10I've never quite understood why banks still opt for kdb when (a) hiring staff is ridiculously difficult/expensive and (b) there are so many other cheaper alternatives available. They literally have a strangle hold on every eFX desk in London, and I cannot really figure out why!
huh, so what do i need to learn to be one of these ridiculously expensive people working w/ kdb?
I'd start with https://code.kx.com/q4m3/