Are you working with large number of entities, being customer specific prices or entities that changes often like e.g. inventory numbers?

Up until now Enterspeed has had its strength on static data from a CMS, a PIM system or something similar. This is because the way Enterspeed preprocesses the data making it stable and fast to fetch on the client.

But no approach is the perfect solution for all use cases, and we know that not all data is static and requires transformations. So, why put data through a transformation process that takes a lot of resources if the data doesn’t need transformation or if it’s never even being fetch by the client?

That’s why we added a new type of data flow in Enterspeed called Auto Indexing.

It’s a feature you enable on the Source group. Once it’s enabled all the data you ingest into this Source group will automatically be added directly to an Index you can query from the Query API.

The new Auto Indexing mode lives comfortably together with the existing schema transformation mode, given you the options to use whatever mode is the best for your specific data set and often it will be a combination of both for your project.

When using Auto Indexing you don’t have the option to create schemas for the source entities, so you can’t do transformation on the data. But instead, you can ingest a large volume of data and have frequently changes to the data making it perfect for dynamic data like customer specific prices or inventory numbers. And especially in combination with the bulk Ingest API you can really send some data through to Enterspeed and have a fast and flexible Query API to fetch the data and offload your ERP system or wherever your data is coming from 🚀

Head over to your Enterspeed tenant today and start using the now Auto Indexing mode and if you need more information, check out the documentation about Auto Indexing.