Re:Technical Challenges Developing a Distributed SQL Database
by gigatexal on Saturday April 27, 2019 @04:32AM
(#19764531)
Before you let the hyperbole train run it’s course there’s are many distributed databases out there. Vitess+MySQL which runs YouTube, CockroachDB, YugaByte, faunaDB, bedrockDB etc
Re:Technical Challenges Developing a Distributed SQL Database
by ldng on Friday April 26, 2019 @11:50PM
(#19763660)
I always though it was one of the pursuit of Google but NoSQL was all the rage and I was never taken seriously ... until F5 that is.
Funnily enough, all what I would call "NoSQL papers" are very well known, yet F5 is hardly ever talked about. As if some people would not like to admit they might have been wrong ;-)
Re:Technical Challenges Developing a Distributed SQL Database
by ddorian43 on Saturday April 27, 2019 @03:27AM
(#19764322)
It's not talked about cause it's named F1 ;)
Re:Technical Challenges Developing a Distributed SQL Database
by ldng on Tuesday April 30, 2019 @03:55PM
(#19791316)
Yes ! Thanks for the correction.
Re:Technical Challenges Developing a Distributed SQL Database
by manigandham on Friday April 26, 2019 @09:23PM
(#19763146)
> "fully distributed db"
What do you mean by this? There are lots of examples of distributed databases.
Re:Technical Challenges Developing a Distributed SQL Database
by sidch on Friday April 26, 2019 @07:02PM
(#19762511)
happy that you liked the post. as you could infer, this simplicity is by no means a magic bullet. there are always trade-offs depending on the database type you use as baseline for comparison. we highlight them here: https://docs.yugabyte.com/latest/introduction/#what-are-the-...
regarding the tone of the post, we are always open to feedback on how we can do better. let us know through any means possible incl. github and slack.
Incredible work. And supporting full postgresql.
This does sound a lot like a marketing post. But me no cares. This is pretty awesome I'm rarely this hyped for a technology.