[pyuser583]

If you’re using KDB, use KDB. The decision has been made, the license paid.

Work to change your organization, not your technology.

Nuclear bombs used to be controlled by decades old systems that worked off floppy disks. Why? Because the systems were so important people worked around the tech.

You’re in a similar spot.

Even when using conventional languages and platforms, sometimes the decision has been made and you’re stuck with it.

KDB might not be the best fit for a datalake, but plenty of people will sleep better just knowing it’s KDB.

Change the people, not the tech.

[steveBK123]

Right what's left unsaid is - even if you are right, having your firms entire data lake rewritten into a new tech stack is a multi-million dollar, multi-year project that will probably take longer than your tenure at the firm.

So figure out how to make it work for you as its a powerful tool and more than adequate for the job, as you aren't going to find something 10x better for time series market data.

Have your team talk to some consulting firms for one-off projects or advisory assistance within your team (like Data Intellect) if the central org is not responsive.

[blitzar]

>rewritten into a new tech stack is a multi-million dollar, multi-year project

(In normal companies i.e. non tech but especially finance) I have seen many promising careers destroyed by these, your corporate life is about the same as a bomb diffuser in a war zone.

12 months and $10mil to roll out the entire system will become $100mil and 4 years to roll out half the system with hacky interconnects to the legacy systems and eventually everyone from IT to compliance will have the finger in the pie taking a cut.