Re:ZenQuery: Enterprise Backend as a Service
by finnh on Wednesday April 23, 2014 @01:10PM
(#7635350)
If it's "entirely hosted on premise" ... how is it "as a service"?
This sounds snarky, but it's not. From reading the site my understanding is that your code is an appserver that I deploy on my hardware, sitting in front of my DB & providing rest-based API access to it.
When I hear "Enterprise Backend as a Service", I understand that to mean something more like FireBase.
Re:ZenQuery: Enterprise Backend as a Service
by finnh on Wednesday April 23, 2014 @03:29PM
(#7636338)
Sure!
This is actually something I could use - I have a few different half-baked API endpoints in front of my DB. Before I would provide my email addr, though, I would need to know more:
1. closed or open source?
2. free or paid / how paid?
funny - I had literally this exact same idea in 2001 when I was considering what the next company I started was going to do. Back then it was XML in both directions, though. I'm pretty sure it would have failed back then, but the world is a different place today - best of luck!
Re:ZenQuery: Enterprise Backend as a Service
by BjoernKW on Wednesday April 23, 2014 @03:57PM
(#7636513)
Thanks a lot.
To answer your questions:
1. The code will be open source in some way. Paying customers will definitely get the source code.
2. I haven't figured out an exact model yet. There'll likely be a free version (with limited features / RDBMS options / concurrent connections) alongside paid tiers with more additional features.
Re:ZenQuery: Enterprise Backend as a Service
by BjoernKW on Wednesday April 23, 2014 @12:16PM
(#7634930)
Thanks for the feedback.
The domain name is intended as a play on the commonly used 'qry_' prefix but you're right this could be confusing.
The versioned queries are currently implemented as views. ZenQuery will also have a 'snapshot' feature soon that'll allow you to store query results as materialized views.
This sounds snarky, but it's not. From reading the site my understanding is that your code is an appserver that I deploy on my hardware, sitting in front of my DB & providing rest-based API access to it.
When I hear "Enterprise Backend as a Service", I understand that to mean something more like FireBase.
I understand that the phrases "as a service" and "on premise" might be conflicting, though. I'll think about how to express this more clearly.
Thanks for your feedback.
This is actually something I could use - I have a few different half-baked API endpoints in front of my DB. Before I would provide my email addr, though, I would need to know more:
1. closed or open source?
2. free or paid / how paid?
funny - I had literally this exact same idea in 2001 when I was considering what the next company I started was going to do. Back then it was XML in both directions, though. I'm pretty sure it would have failed back then, but the world is a different place today - best of luck!
To answer your questions:
1. The code will be open source in some way. Paying customers will definitely get the source code.
2. I haven't figured out an exact model yet. There'll likely be a free version (with limited features / RDBMS options / concurrent connections) alongside paid tiers with more additional features.
The stored/versioned queries and views discussed - are these essentially just views or stored procedures?
The domain name is intended as a play on the commonly used 'qry_' prefix but you're right this could be confusing.
The versioned queries are currently implemented as views. ZenQuery will also have a 'snapshot' feature soon that'll allow you to store query results as materialized views.