Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
Cognite Functions are looking like a great solution to filling some of the gaps to what the CDF API is able to provide, allowing us to effectively extend the API with custom aggregations not possible with the limitations of Synthetic Time Series as well as alleviate the need for application vendors to run more complex business logic in their own backend service layer.
Currently the native language during the Cognite Functions preview is Python. As Cognite Functions moves towards being production-ready I propose the next language/ecosystem that official support be added for is .NET 6. Our company has quite a lot of IP written in a .NET backend and it would be nice to be able to leverage Cognite Functions to port this over and quickly swap out our queries to our Azure SQL instance over to where data will be persisted in CDF.
Hi, Ben!
Thank you for your feedback, and the interest in Cognite Functions. As you say, the initial support is for Python based on our user base requests and feedback.
We want our community of users to leverage their already built IP as much as possible, so we take your feedback seriously and will add this to our product feedback and evaluate it.
If other customers have similar needs, please comment here or add your vote in the Product Ideas section here on the hub.
All the best, Knut
Hello Ben,
Thank you for taking the time to share your feedback with us. Currently, our primary focus for Cognite Functions is support for the Python ecosystem, as it’s prevalent among our users. We will take .NET into account when we consider expanding to other languages in the future.
I understand that we all have limited capacity, it is quite difficult to hire developers to expand capacity at this point in time, and you have prioritized Python to come first. Thank you for the update.