Excellent succinct descriptions. I'm curious what your thoughts are on SOX compliance or any other "distinct record" compliances in these Baleen architectures? More and more, my colleagues and I are required to meet these data quality / compliance standards in ELT products.
There is an inherent difficulty in meeting these standards as you alluded to when writing,
"Like late binding on procedure calls across services, ELT is much more adaptive and accepting of differences and evolution. Also, like late binding, it may not perfectly match the semantics but rather give “good enough” answers."
Excellent succinct descriptions. I'm curious what your thoughts are on SOX compliance or any other "distinct record" compliances in these Baleen architectures? More and more, my colleagues and I are required to meet these data quality / compliance standards in ELT products.
There is an inherent difficulty in meeting these standards as you alluded to when writing,
"Like late binding on procedure calls across services, ELT is much more adaptive and accepting of differences and evolution. Also, like late binding, it may not perfectly match the semantics but rather give “good enough” answers."
Hi Pat. Some minor notes:
REST is for "Representational State Transfer", not "Representational State Transformation".
https://en.wikipedia.org/wiki/Representational_state_transfer
The term "shredding" seems to be overloaded. The term is also used to indicate "secure delete":
https://en.wikipedia.org/wiki/Shredding