J
James Arsenault
Guest
Corticon provides the flexibility to either pass the data in on the call to the decision service or to have the decision service retrieve data; or a mix of both. What you choose depends on your needs. In the majority of Corticon deployments, the data is passed in. This simplifies the architecture because you don't need to account for Corticon connecting to external data sources. This is especially true when you have legacy systems which cannot be easily accessed. In some cases the data passed in can be large; for example all the data needed to process a loan application for a single applicant. In some deployments Corticon needs to retrieve supporting data. This adds another connection to the architecture but it can be a considerable savings not passing all the data in. This is especially true where the data is selective; i.e. the rules are choosing some subset of data that is needed. This can also be useful with reference data that you want to cache. In still other deployments Corticon needs to retrieve the data for efficiency. An example would be a batch application where you need to process a billion records at the end of the month. In such cases efficient moving of data is essential for performance. Short answer, it all depends on your use case. Jim
Continue reading...
Continue reading...