Tallan's Technology Blog

Tallan's Top Technologists Share Their Thoughts on Today's Technology Challenges

Optimizing Document Caches

Many times when a document cache is created for use in a lookup function, only a few values are actually needed. A typical approach to document caching would write an entire document to the cache, including unneeded values. This approach works fine when caching a small number of documents, but will perform worse as more documents need to be cached. A much more efficient approach is to only cache the elements of a document that are actually used.

 

In a typical approach to document caching, a process may look like the example below. In this case, the Inventory Item documents are being cached for a lookup later in the interface. Only the Internal ID and Item ID will be needed for that lookup. As you can see, the document goes straight from the connector to the cache. For the Inventory Item object that means around 130 (mostly unneeded) elements are potentially being written to the cache.

optdoccache1

 

To make this process more efficient, the amount of data that is written to the cache should be restricted. Since the lookup function will only be using the Internal and Item IDs, those are the only pieces of data that need to be written to the cache. Although this could be accomplished by changing which columns are requested in the NSQueryInventoryItem operation, we will focus on restricting the amount of data after it was already been pulled into the process.

First makes some sort of generic XML profile that contains only the information needed in the cache, similar to the profile pictured below. Then create a cache or modify an existing cache using the generic profile.

optdoccache2

 

optdoccache3

 

 

Now add a map to the process between the connector and document cache, as show below. Map the required fields. The data written to the cache will now only contain the required fields.

optdoccache4

 

In addition to an increase in performance, especially if columns are restricted in the NetSuite connector operation, simplifying the cache structure allows for a polymorphic cache. As shown in the picture below, the cache with uses the Item ID/Internal ID XML profile can receive records from both Inventory Item and Assembly Item.

optdoccache5

 

Dell Boomi AtomSphere

The Dell Boomi AtomSphere integration platform is a shared-everything, multi-tenant platform that supports cloud-to-cloud, SaaS-to-SaaS, cloud-to-on-premises, on-premises-to-on-premises and B2B integration. Boomi AtomSphere supports real-time integration and elastically scales to meet high-volume needs in mobile, batch (ETL) and EDI environments. Easily accessed via a browser, it delivers an impressive range of integration, master data management (MDM) and platform extension capabilities.

Tallan Integration Solutions for Dell Boomi
Tallan is a certified Dell Boomi Partner specializing in iPaaS platform integrations. We specialize in Integrations using EDI and Dell Boomi as the iPaaS platform of choice. Leverage Tallan’s vast integration experience for your AtomSphere platform needs.  Our certified architects and developers provide the expertise, best practices, and guidance to deliver a successful integration solution.

We hope this guide will help you in your use of AtomSphere. If you have any questions or comments, or need assistance with any Integrations or development questions, please contact us at integrations@tallan.com.

No comments

Leave a Reply

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>