Paul

My feedback

14 results found

  1. 1 vote
    How important is this to you?
  2. 2 votes
    0 comments  ·  Compass  ·  Admin →
    How important is this to you?
    Paul shared this idea  · 
  3. 7 votes
    0 comments  ·  Realm » Realm JS SDK  ·  Admin →
    How important is this to you?
    Paul supported this idea  · 
  4. 33 votes
    How important is this to you?
    Paul supported this idea  · 
  5. 39 votes
    How important is this to you?
    Paul supported this idea  · 
    An error occurred while saving the comment
    Paul commented  · 

    Would be good to provide folders for Services too.

  6. 4 votes
    0 comments  ·  Database  ·  Admin →
    How important is this to you?
    Paul supported this idea  · 
  7. 38 votes
    6 comments  ·  Atlas » Other  ·  Admin →
    How important is this to you?
    Paul supported this idea  · 
  8. 75 votes
    3 comments  ·  Atlas » Other  ·  Admin →
    How important is this to you?
    Paul supported this idea  · 
  9. 13 votes
    2 comments  ·  Atlas » Other  ·  Admin →
    How important is this to you?
    Paul supported this idea  · 
  10. 43 votes
    How important is this to you?
    Paul supported this idea  · 
  11. 51 votes
    How important is this to you?
    Paul supported this idea  · 
  12. 30 votes
    6 comments  ·  Database  ·  Admin →
    How important is this to you?
    Paul supported this idea  · 
  13. 50 votes
    How important is this to you?
    An error occurred while saving the comment
    Paul commented  · 

    Having suffered at the hands of XA, using WebLogic with Oracle RAC and MQ Series back in the day, I am not personally a fan of dragging modern applications back into those monolithic dark ages.

    Nowadays, XA/2PC transactions have increasingly come to be regarded as problematic, perhaps introducing more issues than they solve, such as:
    * Poor performance due to a ‘pessimistic’ locking approach, plus excessive use of network ‘hand-shaking’ between participants
    * Operational complexity
    * Interoperability issues and software bugs due to complexity in implementing the XA specification
    * Eventual consistency of the final commits fulfilled by each participant system
    * Reduced high availability, especially where the ‘transaction coordinator’ invariably becomes a potential single point of failure

    Here's some views which talk to these points:
    * Section ‘Distributed Transactions and Consensus’ in Chapter 9 of the book Designing Data-Intensive Applications by Martin Kleppmann (O'Reilly, 2016).
    * "Your Coffee Shop Doesn’t Use Two-Phase Commit" by Gregor Hohpe
    * "Myth: Why Banks Are BASE Not Acid - Availability Is Revenue" by Eric Brewer
    * "The Hardest Part About Microservices: Your Data" by Christian Posta
    * "SHOCKER: XA Distributed Transactions are only Eventually Consistent!" by Paul Done
    * "It’s Time to Move on from Two Phase Commit" by Daniel Abadi

    (I can't seem to hyperlink here, but if you google each title/author above you should hit the articles straight away)

    How can I DOWNVOTE? ;)

  14. 1 vote
    0 comments  ·  Database  ·  Admin →
    How important is this to you?
    Paul shared this idea  · 

Feedback and Knowledge Base