Institute of Information Science - University of Miskolc

User Tools

Site Tools

Trace:
tanszek:oktatas:iss_t:software_integration

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
tanszek:oktatas:iss_t:software_integration [2026/02/15 22:14] – [When to Use Database-Based Integration?] kneheztanszek:oktatas:iss_t:software_integration [2026/02/15 22:18] (current) – [Data Sharing] knehez
Line 208: Line 208:
 ===== Data Sharing ===== ===== Data Sharing =====
  
-A simple approach to integration is data sharing. +A simple approach to integration is data sharing. Data sharing–based integration aims to transfer and share data between systems. This enables individual systems to access and utilize data stored in other systems.
- +
-Data sharing–based integration aims to transfer and share data between systems.  +
-This enables individual systems to access and utilize data stored in other systems.+
  
 Data sharing can take several forms: Data sharing can take several forms:
Line 222: Line 219:
 ===== File-Based Data Sharing ===== ===== File-Based Data Sharing =====
  
-The most fundamental method of data sharing. +The most fundamental method of data sharing. One application writes data, while another application reads data from the same file. The data files are stored in a central location — such as a shared folder (e.g., NFS) or an (S)FTP server. The information flow is unidirectional: A → B.
- +
-One application writes data, while another application reads data from the same file. +
- +
-The data files are stored in a central location — such as a shared folder (e.g., NFS)  +
-or an (S)FTP server. +
- +
-The information flow is unidirectional: A → B.+
  
  
Line 394: Line 384:
   * Platform-independent connectivity (e.g., JDBC, ODBC)   * Platform-independent connectivity (e.g., JDBC, ODBC)
   * Multiple instances of identical components may access the same database   * Multiple instances of identical components may access the same database
- 
     * Synchronization issue: Who processes the next record in the queue?     * Synchronization issue: Who processes the next record in the queue?
     * However, it can be an ideal solution for data collection scenarios.     * However, it can be an ideal solution for data collection scenarios.
Line 400: Line 389:
 ==== Limitations ==== ==== Limitations ====
  
-  * Not real-time by default.   +  * Not real-time by default. If one application writes to the database, another application does not automatically receive notification. 
-    If one application writes to the database, another application does not automatically receive notification. +    * Possible solutions: 
- +      * Database notification mechanisms (e.g., PostgreSQL LISTEN and NOTIFY) 
-Possible solutions: +      * Triggers 
- +      * Polling mechanisms
-    * Database notification mechanisms (e.g., PostgreSQL LISTEN and NOTIFY) +
-    * Triggers +
-    * Polling mechanisms +
   * Security considerations: Properly defined access rights are required (table access, permitted operations). Developers often restrict direct visibility of database structures.   * Security considerations: Properly defined access rights are required (table access, permitted operations). Developers often restrict direct visibility of database structures.
- 
   * Lack of well-defined interfaces — this approach provides only data-level integration.   * Lack of well-defined interfaces — this approach provides only data-level integration.
  
tanszek/oktatas/iss_t/software_integration.1771193670.txt.gz · Last modified: 2026/02/15 22:14 by knehez