You are here

Welcome to the NuoDB Blog

  • We’re talking about a few new ideas this week here on the NuoDB techblog. We hope you’re enjoying it!

    One of those is a new kind of benchmark that we’re working on. Traditionally benchmarks tend to focus on numbers like Transactions Per Second: metrics that measure the speed or size of a database. These are definitely important, and later this spring we’ll be publishing more numbers in this vein.

    Today, however, we want to talk about a new kind of benchmark that we think is also important. These are benchmarks that try to measure something about real

  • This week we’re talking for the first time about a lot of cool things we’ve had in the pipe-line for a while. These are less about the nature of what’s inside a single database and more about the future direction of the product from a management and automation point of view.

    We’ve always believed that being “cloud-scale” means many things. It’s about scaling out databases by adding resources on-demand. It’s also about being agile, supporting the unexpected spikes that happen in the real-world and taking advantage of those on-demand

  • One thing I often get asked to describe is the development process of NuoDB’s Cloud Database . That usually comes in the form of a question as to whether we use agile methodologies, waterfall or something else.

    Our overall guiding principle to software development is simply this: “Keep It Working” . Everything we do is about

  • A few weeks back, a question came up on the NuoDB Community Forum regarding a table ID column which had been created using the “GENERATED ALWAYS AS IDENTITY” statement. The values displayed in this column had suddenly jumped from 61 to 72 and the poster was confused as to why.

  • We at NuoDB were recently given the opportunity to kick the tires on the Google Compute Engine by our friends over at Google. You can watch the entire Google Developer Live Session by clicking here . In order to access the capabilities of GCE we decided to run the same YCSB based benchmark we ran at our

  • Hi, I’m Adam Abrevaya, the VP of Engineering at NuoDB. You’ll be seeing much more from me in the way of me introducing new innovative features in upcoming releases, how we build NuoDB – i.e. insight into our engineering practices and how we test NuoDB (that gets really interesting at massive scale – 100s or 1000s of machines). Today however I’ll add my 2 cents to the caching discussion that Seth (see:

  • Absolute perfection is perhaps an unattainable goal, but continuing improvement is not. The NuoDB engineers have been focusing on performance enhancements ever since the release of NuoDB Starlings 1.0. The ensuing market demand has been impressive. We now have an enhanced product — NuoDB Starlings 1.0.2

    “With each release user engagement has increased both with respect to the core product as well as the new beta programs such as the ADO.NET Driver,“ said Duke Adamonis,

  • NuoDB Becomes One of the First Standard Technology Partners at Amazon

    Cambridge, MA –March 25, 2013 – NuoDB, Inc., the pioneer in cloud database and Cloud Data Management System ( CDMS ), today announced the immediate availability of the NuoDB Starlings release on Amazon Web Services ( AWS ) Marketplace and their selection as a member of the AWS Partner Network (APN) in the category of Standard Technology Partner.

  • Welcome, concurrency-minded nuonians, to part 3 of the MVCC overview! In part 1 , we laid out the basics of MVCC and described how MVCC enables much higher concurrency than conventional read/write locks (even per row). In part 2 , we explored how MVCC works in the presence of interleaved reads and updates. This post is going to cover visibility and the subtleties of maintaining transactional consistency with MVCC.

    What is visibility?

    The whole reason why we’re

  • Tommy and I just did a Google Developer Live thing. Great fun!! The demo hit a little snag but Tommy did great, and hey, it proves it was real.

    Big thanks to Brian & Julia for working with us and getting this pulled together!