Open source, resilient, scalable, geo-distributed & runs anywhere, YugabyteDB is the ideal modern #distributedSQL DB for transactional #cloudnative apps!
Share the love & nominate #YugabyteDB for BEST #CLOUD DATABASE in the DBTA Reader's Choice awards!🚀
https://t.co/a08S0WNf08
Excellent thread by Franck debunking false claims by @CockroachDB. Essentially, their only defense against @Yugabyte seems to be "started with Postgres, so cant be cloud native" without waiting to think that they are being asked by users to build UDFs, a core Postgres feature 😉
🪳A recent announce from CRDB was plain wrong about how @Yugabyte re-uses @PostgreSQL and here are the facts: https://t.co/GmuzTgXWGD
🧵that's the occasion to look back at their "CockroachDB in Comparison" full of 🤡 claims on all DB compared. I'll detail the ones about YB 👇🏻
Spot the @Yugabyte logo in the @satyanadella keynote
...working across our entire partner ecosystem to ensure category-leading solutions are deeply integrated with everything...
https://t.co/cC52FOi6dd
PostgreSQL is in the news this week.
1. Google continues enhancing Postgres compatibility for Spanner (+ AlloyDB changes): https://t.co/m1DaN1aIlE
2. Microsoft introduced a Postgres interface for CosmosDB:
https://t.co/sOU93UXtYE
YugabyteDB was and is on the right track!
@vlad_mihalcea@rponte@FranckPachot@Yugabyte +1 that the words "optimistic" and "pessimistic" just add to confusion. However, note that in YB's optimistic locking doesn't detect conflicts at commit time, they are detected immediately. So it is not optimistic like "optimistic concurrency control"
@rponte@vlad_mihalcea@FranckPachot@Yugabyte A correction to the blog post @vlad_mihalcea - both pessimistic and optimistic locking schemes implicitly take locks in YugabyteDB to avoid the dirty write issue. However, they differ in whether to "wait" or "abort" txns when a conflicting lock mode acquisition is attempted.
@denismagda@rponte@vlad_mihalcea@FranckPachot@Yugabyte Correction here -- YDB locks at the finer col level even without pessimistic locking and locks are used at isolation levels. I think what you mean to say is a txn "waits" on locks only when YDB is run in pessimistic locking mode (which is at the moment only for read committed)
This is actually very much inline with what the Yugabyte community says too. We actually had to add read committed because that is the most often used isolation level.
This is actually very much inline with what the Yugabyte community says too. We actually had to add read committed because that is the most often used isolation level.
Join us today at DSS 2022 to hear me and Rob Sami talk about two recent additions to YugabyteDB's distributed transactional layer that increase parity even further with PostgreSQL: read committed isolation and pessimistic locking
🚀 @Yugabyte#DSS22
"It's easier than retraining #PostgreSQL devs, says distributed relational database startup."
Check out the article by @TheRegister's @datadictum which discusses new #YugabyteDB 2.15 features, including dev-friendly read-committed isolation levels. ⬇️
https://t.co/CYnB53WEbt
Discover what @Yugabyte's Principal Pre-Sales Engineer, Rick Michaud is most looking forward to at this year's Distributed SQL Summit (DSS) and why YOU won't want to miss it! 🚀
🗓️ONLINE: September 14th, 2022🗓️
Watch the video & register for free!⬇️ https://t.co/SselSVogR6
Interested in discovering more about #yugabyteDB and #distributedsql?
Join our active Slack community of users, experts, and enthusiasts here!
https://t.co/AwdUnPKtlI
Drop a note in the yb-users thread to say hello! 🚀
I have come across way too many people to count who are gainfully employed, committed to making next decade about climate, & unable to do a public search.
Surfacing these people and connecting them quietly to specific companies is a huge opportunity, and can make a huge impact.