Home » Data in Motion

Data in Motion

Service Components
  • Primary Concern is the management of data flowing between solutions
    • Could be internal flows between business units and other applications; or external flows to customers, suppliers, partners or regulators
      • Extract, transform and load over secured and encrypted channels
      • Batch, API, service bus or queue
    • Only authenticated and authorized applications should have access to data
    • Able to validate both senders and recipients of data
    • Apply end-to-end data encryption on all transfers
  • Control and audit what data is being transferred and between whom is it being sent
    • Ordered delivery and automated retry on failure
    • Receipt tracking and non-repudiation
    • Unauthorized Data Loss Prevention (DLP) mechanisms
  • Maintain the integrity of the information protected by Data at Rest
    • Validate the structure of data being received
    • Validate the content of data as it arrives before it is stored
    • Works to decouple the Data at Rest components from external dependencies

Why To decouple Information Systems?

  • Tightly-coupled information systems are inherently fragile
  • Assuming “A” and “B” are applications that exchange data in real-time using a tightly-coupled mechanism, if A fails, B also fails
  • Decoupling the data exchange between A and B minimizes dependencies and increases robustness
  • To minimize operational risk, it is recommended that Data at Rest components do not exchange data using a tightly coupled mechanism with any other application (internal or external). Within your Data Agnostic Services, tight coupling is only allowed to Data at Rest; if you can’t access your own data, you can’t do anything anyway!
  • Ensure that the design of your Data in Action, Data in Motion and Data Presentation service components do not “lock” the Data at Rest if they fail

How to decouple Information Systems?

  • Buffered communications channels using mechanisms, such as:
    • Events and Notifications
    • Message Queues including SMS and email
    • Service Bus Queues and Topics
    • File Transfer – Extract, Transform and Load (ETL)
    • Shared data stores
    • Combinations of the above
      • For example, drop a file and send an event/message