1. Justin Bouldin – CTO Community TechKnowledge
8 THINGS YOU NEED TO KNOW
ABOUT DATABASE INTEGRATION

2. 1.
2.
3.
4.
5.
6.
7.
8.
What is Database Integration?
Why Does Everyone Want It?
What About All Those Words?
What Types Are Available?
Is it Possible with My System?
How Do I Do it Right?
How Much Does it Cost?
Is it Worth It?
www.communitytech.net
2

3. 1. What is Database Integration?
Hey Buddy! How
you feelin?
Pretty
normal…
Databases “talking” to each other
www.communitytech.net
3

4. In a Nutshell
• Copying data from one location to another
• Pulling data from multiple locations into a
single “view”
• Leveraging functionality of one system to
enhance the other
www.communitytech.net
4

5. 2. Why Does Everyone Want It?
• It’s empowering
o More reliable data
o Better reporting
o Enhanced functionality
• It saves time
o Less data entry or manual report compilation
• It can save money
o If you do it right
www.communitytech.net
5

6. 3. What About All Those Words?
www.communitytech.net
6

7. CSV
(Comma Separated Values)
Pros
Cons
• In use for 40 years
• Accepted by almost every system
• Can be viewed and edited in any
spreadsheet software
• No hierarchy structure (flat)
• Prone to formatting errors
www.communitytech.net
7

8. XML
(Extensible Markup Language)
Pros
Cons
• Can store a lot of information
• Powerful transformational tools
• Every system stores the
information in its own format
• Very difficult for humans to
understand or manipulate
www.communitytech.net
8

9. JSON
(JavaScript Object Notation)
Pros
Cons
• Rapidly becoming the standard for • Still not really editable by a human
new technologies
• Combines power, simplicity, and
speed
{"statement":"JSON is awesome", "reasons":["it's
(almost) universal", "it's powerful","it's fast","it's easy"]}
www.communitytech.net
9

10. API
(Application Programming Interface)
• A broad term that includes a lot of technical
jargon, mystery, and misunderstanding
• A set of commands that one system makes
available to other systems
• Almost always requires a developer to
implement
www.communitytech.net
10

11. SOAP
(Simple Object Access Protocol)
• The API protocol that brought interoperability
to the masses
• Relies heavily on Java and XML
• Generally considered a slow, cumbersome, and
outdated methodology
www.communitytech.net
11

12. REST
(Representational State Transfer)
• The way browsers and web servers naturally communicate
• More or less a universal language
• Much lighter and easier to use than a SOAP based API
• Plays to the inherent strengths of web servers
• Leverages existing internet infrastructure
• Often uses JSON as the format for data transfer
www.communitytech.net
12

13. SOA
(Service Oriented Architecture)
• A modular software design pattern providing
functionality as services to other applications
• Each service is a self-contained unit
• Services can be used individually, or combined to
create a full application
• Each service is built in a way that allows the exchange
of information without human interaction
www.communitytech.net
13

14. 4. What Types are Available?
•
•
•
•
•
•
•
•
Manual
Direct Access
Export/Import
Synchronization
Integration Tool
Triggered
Built-in
All-in-one Solution
www.communitytech.net
14

15. 5. Is It Possible With My Systems?
• You need access to both systems
• The newer the technology, the more likely it is to be open to integration
• Systems that run in a web browser, or in the “cloud”, are more likely to
be open to integration
• The systems need to be compatible
• You will most likely have to convince one or both vendors to co-operate
TIPS FROM THE INSIDE





Have a clear understanding of your current process
Know what problems you want to solve
Know what benefits you hope to gain
Keep an open mind about the solution
Be a mediator, not a translator
www.communitytech.net
15

16. 6. How Do I Do It Right?
•
Choose the right vendors
•
Think it through
•
Choose a system of record
•
Find a solution that is:
If you are looking for a Magic
Bullet, remember that the key
components of any magic trick are
sleight of hand, misdirection and
mystery…
o Simple
• More complexity introduces more room for error
• Don’t mistake seamless for simple
o Flexible
• Your data needs are always expanding
• Don’t build an integration that only fits your data needs right now
o Transparent
• Should have a clear understanding of what is happening with your data
• Even a fully automated system requires someone to verify the data occasionally
www.communitytech.net
16

17. 7. How Much Does it Cost?
A good solution will cost less than you might think
Avoid the following:
• Forced integrations with
closed systems
• Complex, fully-automated
systems
• Inflexible solutions that you
have to pay to update
• Poorly thought out systems
that break
And keep in mind all the costs:
• Internal time and materials
(plan for a lot)
• Initial setup
• Ongoing costs
• Maintenance costs
• Intangibles
www.communitytech.net
17

18. 8. Is it Worth It?
We think so, but what do you think?
www.communitytech.net
18