Hi Dor, We're in the process of releasing Phoenix 4.7.0 which includes transaction support through Tephra. We're calling our transaction support beta because it's the first release with this support. Phoenix is used in production at many companies[1], including mine (Salesforce). Tephra (as part of CDAP) is also used in production, so it's the integration between the two that's new. Our first production usage will likely be with write-once/append-only data with secondary indexes (so that the two are transactionally consistent). We've measured the overhead of transactions in this scenario and found it to be quite low[2]. One area, at least in standalone transactional Phoenix, where you'll need to do something specific for your environment is deployment and monitoring of the transaction manager (perhaps CDAP can help here).
Every use case is different, though, so I encourage you to try representative data sets under representative load for all the systems you're considering. We have a tool called Pherf[3] which makes this kind of testing easier. Please feel free to post mail here or on the Phoenix user list [4] to get more specific feedback. Thanks, James [1] https://phoenix.apache.org/who_is_using.html [2] http://s.apache.org/p6z [3] https://phoenix.apache.org/pherf.html [4] https://phoenix.apache.org/mailing_list.html On Wed, Feb 17, 2016 at 5:55 AM, Dor Ben Dov <[email protected]> wrote: > Hi, > > > > Are any one here knows or uses the project in his production ? for how > long ? > > > > Does the Tephra integration and transactions over Hbase are working good – > can I count on it for production stress ? > > > > > > Regards, > > Dor Ben Dov > This message and the information contained herein is proprietary and > confidential and subject to the Amdocs policy statement, you may review at > http://www.amdocs.com/email_disclaimer.asp >
