You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "clebert suconic (JIRA)" <ji...@apache.org> on 2015/04/15 20:43:00 UTC

[jira] [Commented] (ACTIVEMQ6-27) Database Implementation

    [ https://issues.apache.org/jira/browse/ACTIVEMQ6-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14496683#comment-14496683 ] 

clebert suconic commented on ACTIVEMQ6-27:
------------------------------------------

BTW: I'm not sure it's possible to have the same implementation sharing JDBC and NOSQL... but we can certainly take that into consideration on this task.. having NoSQL being an extension or something like that.

> Database Implementation
> -----------------------
>
>                 Key: ACTIVEMQ6-27
>                 URL: https://issues.apache.org/jira/browse/ACTIVEMQ6-27
>             Project: Apache ActiveMQ 6
>          Issue Type: New Feature
>            Reporter: clebert suconic
>             Fix For: 6.1.0
>
>
> Notice that I'm not calling this JDBC. It's Database:
> The storage interface here should take in consideration NoSQL databases as possible options.
> My idea is that we should have a Callback interface optimizing locking times and using recator pattern through the OperationContext.
> Instead of using a single Executore could have multiple DB-Executors all capable of handling multiple client connections.
> If we deal this with being Database centric (not JDBC centric) features from the NoSQL could become available here for free



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)