Enginio: The Qt Cloud Backend Hits Beta

Published Thursday September 5th, 2013 | by

It is my absolute pleasure to announce that Enginio, our very own Qt cloud backend, has reached Beta status today. We have developed Enginio to make it easy for Qt developers to set up a backend for Qt applications. You can use Qt/C++ or QML and connect your application to the Qt cloud in less than 3 minutes. You don’t have to think about servers, databases, scalability, up-time, user management and many other aspects of the technical and repetitive work surrounding the backend.

Enginio removes the pain-staking efforts of setting up a server backend for your connected Qt app, regardless of software and hardware for desktop, embedded or mobile. With Enginio, the backend creation is completely abstracted, letting you focus on what matters: a perfect application for your users. Any connected and data driven applications require a server-side backend. You can now easily code, create, deploy and maintain a multi-screen user experience, content storing, user management, logging or any other cloud functionality in your Qt application with one framework and one Qt cloud backend. Keep it in the Qt family.

Check out this video made by one of our Qt Enginio developers and find out how easy it is to get started: http://youtu.be/7NheiHdg5Hg

What Does Enginio Beta Mean?
Well, we know how serious you are about applications and software built with Qt, and the last thing we would want to do is to cause any form of trouble for you. We are committed to ensure the same service quality in this Beta as  in a production version from this point on. Enginio is based on years of experience from building robust backends for both enterprise and consumer applications and has been in active customer use since the first technology preview.

Thank you very much for the comments and questions so far. You can contact us and other developers via the Enginio discussion forum on qt-project.org or by email: mailus@engin.io  at any time. We can’t wait to see what projects you will develop with this Beta and coming releases.

Try Enginio now!

Did you like this? Share it:
Bookmark and Share

Posted in Announcements, Cloud, Enginio, Network

13 comments to Enginio: The Qt Cloud Backend Hits Beta

DavidB says:

Very powerful but had a question about security. I only could view the video and not hear it so apologies if my question was addressed in the audio.

The server key and secret (I think it was secret) were stored in plain text in a QML file. Would not this be easy for any hacker to read. As I understand it QML files cannot be resource files so they are always exposed. Am I wrong on this ?

Jari Kolehmainen says:

You can also use user authentication and access control lists for more security.

Justin says:

Also QML files can be placed in resource files. Though authentication would be the better route anyway.

Nierob says:

Qrc files are not secure, because they are not encrypted. Backend id and backend secret are used only to pick the right backend. Authentication needs to be done on the server side. Enginio provides full ACL based security model that can be used for that purpose.

https://engin.io/documentation/overview/security

Kurt Pattyn says:

Very nice! Is there any information about the back end? What technologies are used? What guarantees are there that this service will be still available over 5 years for instance?

Mika Myllymaki says:

@Kurt, Thanks! The current information is available at http://engin.io. There will be more details in the documentation as things move on. Stay tuned.

We are committed to the long term plan to create and maintain cloud-based services that can be used in conjunction with Qt. As said, the last thing we would do is to cause any form of trouble for you. Our top priority in Enginio is to make customers’ lives easier in a long term.

Fabio says:

Will Enginio be part of LGPL Qt?

Mika Myllymaki says:

Yes, Enginio Qt library will be licensed also under LGPL.

Will Stokes says:

Are there any plans to enhanced the client side Enginio code so that it can use alternative backend services like Amazon S3? The reason I ask is that if the Enginio service was pulled in 5 years time it would be nice if client side code didn’t need to be rewritten to support a different hosting service.

Mika Myllymaki says:

At the moment the client side focuses on the Enginio backend. It is actually worth mentioning that the Enginio backend is currently running in Amazon.

Bill petersen says:

Why create your own service instead of supporting existing services like parse, dynamo db et al.

This is taking NIH to next level :/

Mika Myllymaki says:

We saw that there was room for improvement, as we wanted to provide Qt developers with an uncomplicated and stress-free development experience. In this way, we can provide the best and deepest integration with Qt. This approach is also better for driving stronger business architecture of Qt.

Felicitas says:

Excellent article! We are linking to this great content on our website.
Keep up the good writing.

Commenting closed.