Best Practice: Multi-Segment Keys

Correct me if I’m wrong, but I believe I read somewhere that Backendless is a NoSQL database. Possibly Mongo. Most of my experience is with relational DBs. So I was pleasantly surprised to see the Unique Value and Indexed constraints when defining a Column. Furthermore I noticed a slew of SQL type properties in the Load Table Objects block, which included many SQL type relational constraints.

So… maybe backendless is not a NoSQ DB? In either case if multi-segmented keys are not intrinsic, to the Codeless interface, is there some SQL or API like means of defining such? Otherwise, what would be the best practice? 1- Using Filters? 2- Or maybe some kind of multi-pass logic?

image

Hi, @Townsend

You are absolutely right, Backendless uses a lot of SQL properties and type relational constraints. We support several types of SDKs, as well as the REST API and our Codeless system. So each developer can choose that one is convenient for him. You can read more about our features there https://backendless.com/developers/
And also you can find a lot of useful for you in our blog https://backendless.com/blog/

Regards,
Marina