activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martyn Taylor (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ARTEMIS-27) Database Implementation
Date Tue, 07 Jun 2016 16:09:21 GMT

     [ https://issues.apache.org/jira/browse/ARTEMIS-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Martyn Taylor resolved ARTEMIS-27.
----------------------------------
    Resolution: Fixed

> Database Implementation
> -----------------------
>
>                 Key: ARTEMIS-27
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-27
>             Project: ActiveMQ Artemis
>          Issue Type: New Feature
>            Reporter: clebert suconic
>            Assignee: Martyn Taylor
>            Priority: Critical
>             Fix For: 1.3.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)

Mime
View raw message