SQL/MX Release 2.0 Best Practices

Publish and Subscribe 43
Publish and Subscribe
This section compares the use of publish and subscribe against the use of queue files.
• SKIP CONFLICT ACCESS is available through publish and subscribe, but not through queue files,
which is a performance advantage that supports scalability and avoids hotspots.
• Queue files must be accessed through Enscribe, but publish and subscribe can be accessed
through ODBC, JDBC, and embedded SQL, and is also supported through JMS.
• Queue files do not support partitioned tables, but publish and subscribe does (note that for good
performance, most publish and subscribe applications should access only one partition).
• Publish and subscribe supports nondestructive streams. You need not delete the row that is being
read, as is required for queue files.