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. Both Phoenix (see [1]) and Tephra (as part of CDAP) are used in production today at many companies, 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