art, checkout the jdbc statements - there are indices https://github.com/apache/activemq/blob/d54e0d6ab590b6a6148a5e2629c45b95d3f40eb8/activemq-jdbc-store/src/main/java/org/apache/activemq/store/jdbc/Statements.java#L102
and there is nothing to stop further partitioning etc - by some knowledgeable dba a bit that is missing is batching, but the idea is to shovel the bits in as fast as connections will allow so that the db backend can batch writes. On 8 January 2015 at 00:00, artnaseef <a...@artnaseef.com> wrote: > Oh, and JDBC has been known to have issues - especially having poor > performance. There is no optimization in its interactions with the DB at > all (e.g. no indices). > > > > -- > View this message in context: > http://activemq.2283324.n4.nabble.com/Is-JDBC-still-used-tp4689546p4689628.html > Sent from the ActiveMQ - User mailing list archive at Nabble.com.
