Acidbase: The Initial Performance Test

So after implementing the new architecture, I decided it is time to take the whole system out for a spin. I’ve already had chosen some dataset to accompany the system and now I want to test the system’s performance with them.

Acidbase part two – I want it all and I want it now

Picking up where we left off, in the previous post we talked about the differences between RDBMSs and NoSQLs and why there is no “one size fit all” in this product line. Now it’s time to give the good news, having some constraints set we can come up with a pattern for our dress which might not fit all but some predefined age range (from 20 to 40 seems right). And if we confine our constraints accurate enough the product could be actually useful to a wide range of customers, no one can argue the value in that! And that’s what exactly I’m going to do in this post, defining a set of constraints in a way that we can actually base a data storage system on, providing its users with features of an RDBMS and a NoSQL at the same time.

Acidbase part one – An ACID + BASE database for enterprise software

This is the first of a three-part post introducing an open source software I started, named Acidbase. In this first part I’m going to explain my motivation and the problem Acidbase is addressing; scalability without sacrificing ACID attributes, hence ACID + BASE.

Database design for enterprise software solutions

Not that database design is any different for enterprise software from other types of software solutions or anything, but a couple of requirements shared by most of them made me think of a design that I’m going to share with you here. The design introduced here is a really powerful one that can open so many doors for you but at the same time, I admit, it can be troublesome in some of the cases, but at least you’ll have a getaway route in cases where you are stuck and have got no choice. We’ll see that in a couple of minutes.