Skip to main content

Attributes of a Good Data Integration

  • Chapter
  • First Online:
Developing Data Migrations and Integrations with Salesforce
  • 744 Accesses

Abstract

If you were to ask someone, “What’s the difference between an integration and a migration?” you’ll likely get an answer along the lines of: “Migrations are one-time runs whereas integrations are ongoing.” As discussed in Chapter 4, data migrations are not really a one-time run-and-done job. Because testing is critical to success, the same code needs to be run for QA and UAT.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 54.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 69.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Notes

  1. 1.

    I have no idea why, but for some reason, new hardware—particularly servers—never show up on time.

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 2019 David Masri

About this chapter

Check for updates. Verify currency and authenticity via CrossMark

Cite this chapter

Masri, D. (2019). Attributes of a Good Data Integration. In: Developing Data Migrations and Integrations with Salesforce. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-4209-4_5

Download citation

Publish with us

Policies and ethics