1
Data Replication –Data Replication –
Synchronization ToolsSynchronization Tools
Pradeeban KathiraveluPradeeban Kathirave...
2
Agenda
 Background and Assumptions
 Front-end
 Back-end
 Design Alternatives
 Design Choice
 Good to have
3
Background
 TCIA MySQL database is the data source.
 Users are downloading “series” or data of
higher granularity.
 C...
4
Initial Assumptions
 The existing download manager may be used
in the client side.
5
Front-End
6
Front-End
 User logs in
– Clicks the “Download Updates” option.
7
(browser)
Front-end / Back-end
8
Front-end / Back-end
 CXF/JAX-RS RESTful APIs.
– GET
– Follow the existing REST APIs in downloading.
9
Back-end
 A Pub-Sub Solution
– Update subscriptions for new downloads.
– Publish and store the new updates for the
subs...
10
Back-end: Alternatives
 The Pub-Sub solution
– CXF/JMS Transport [1]
– With Hazelcast [2]
 Database integration and q...
11
Combinations
 Entirely Hazelcast
– Except for CXF/JAX-RS RESTful invocations
 Entirely CXF
– With CXF/JMS for Pub/Sub...
12
Design Choice
 Entirely Hazelcast
– With CXF/JAX-RS RESTful invocations.
13
Why?
 Simplicity
– Pub-Sub and query management - both handled
by Hazelcast.
– Pub-Sub query updates could be stored
s...
14
Good to have
 Develop into OSGi bundles to plug into
Bindaas.
15
Thank you..Thank you..
Upcoming SlideShare
Loading in …5
×

Data Replication - Synchronization Tool for TCIA

892 views

Published on

Design alternatives and decisions of TCIA Data Replication and Synchronization Tools.

Published in: Engineering, Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
892
On SlideShare
0
From Embeds
0
Number of Embeds
460
Actions
Shares
0
Downloads
4
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Data Replication - Synchronization Tool for TCIA

  1. 1. 1 Data Replication –Data Replication – Synchronization ToolsSynchronization Tools Pradeeban KathiraveluPradeeban Kathiravelu IST – ULisboa / INESC-IDIST – ULisboa / INESC-ID
  2. 2. 2 Agenda  Background and Assumptions  Front-end  Back-end  Design Alternatives  Design Choice  Good to have
  3. 3. 3 Background  TCIA MySQL database is the data source.  Users are downloading “series” or data of higher granularity.  Collection – Patients ← same patient • Studies ← meta data – Series ← meta data » Images ← raw file
  4. 4. 4 Initial Assumptions  The existing download manager may be used in the client side.
  5. 5. 5 Front-End
  6. 6. 6 Front-End  User logs in – Clicks the “Download Updates” option.
  7. 7. 7 (browser) Front-end / Back-end
  8. 8. 8 Front-end / Back-end  CXF/JAX-RS RESTful APIs. – GET – Follow the existing REST APIs in downloading.
  9. 9. 9 Back-end  A Pub-Sub Solution – Update subscriptions for new downloads. – Publish and store the new updates for the subscribers • Till they log in again.  Database integration and query management – TCIA data store is a MySQL database.
  10. 10. 10 Back-end: Alternatives  The Pub-Sub solution – CXF/JMS Transport [1] – With Hazelcast [2]  Database integration and query management – Hazelcast distributed queries – Using CXF – [1] https://cxf.apache.org/docs/jms-transport.html – [2] http://java.dzone.com/articles/publish-and-subscribe
  11. 11. 11 Combinations  Entirely Hazelcast – Except for CXF/JAX-RS RESTful invocations  Entirely CXF – With CXF/JMS for Pub/Sub  CXF and Hazelcast – CXF/JAX-RS and CXF/JMS – Hazelcast distributed queries – Apache Camel for integration – Way too many components (?)
  12. 12. 12 Design Choice  Entirely Hazelcast – With CXF/JAX-RS RESTful invocations.
  13. 13. 13 Why?  Simplicity – Pub-Sub and query management - both handled by Hazelcast. – Pub-Sub query updates could be stored seamlessly in-memory and in database.
  14. 14. 14 Good to have  Develop into OSGi bundles to plug into Bindaas.
  15. 15. 15 Thank you..Thank you..

×