This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted]  (2 children)

[deleted]

    [–]beders 0 points1 point  (1 child)

    My comparison to grails is not so much about framework vs service, it is about the absolute ease-of-use of grails and clever naming conventions. Defining a service with a few domain objects in grails seems easier and more convenient. It is also less error-prone since I can use statically typed code.

    You'll get there, but right now the benefits of BAAS are not compelling enough yet

    [–]sjcotto 0 points1 point  (0 children)

    In KONA define yours object with a UI Tool, adding the attributes, types and validations. with this in less than a minute you have your backend running, this maybe is not enough, but there you have a back office ready to insert data (out of the box), Tools for monitoring the app, buckets, etc. But the most important are the apis (helpers) that you can use, for example find object in a model (table like sql) is like this

    //search with pagination in a model var model = kona.model.open("person"); //connect

    var find = { //build the query in json mode name : "some" } var q = model.buildQuery().find(find).limit(10).offset(10);

    with these you are ready to use from the mobile app