GAE-Studio is now open source!

Some of you may already have noticed or heard me saying that GAE-Studio was going to be open sourced and I think it is past overdue to officially announce it: GAE-Studio is now open source under Apache 2 and freely available! We promise to keep working on it, and to make that possible, we’re going to add GAE-Studio support to our open source support packages. You can find the source code under our Arcbees github organization as well as on maven central. We released an official, stable version 1.0 a couple of days ago that you can see in action on our demo website. You can also read our documentation to learn more about how to install GAE-Studio in your Google App Engine application.

gae_datastore_viewer

Some may wonder why we chose to open source what was going to be our first official product. We’ve first started this venture almost 3 years ago when Arcbees was still in its inception. We were using Google App Engine heavily, and the lack of a good datastore admin console was a big problem. At the time, Google App Engine didn’t have any hooks on which we could build one, so we hacked our way around and built something useful for our own work. One year later, after finding other users were feeling the same pain as we did using Google App Engine, we set out to improve GAE-Studio user experience. It was planned to be our very first product that wasn’t going to be open sourced.

Last summer, Google IO announced a new console for Google App Engine that removed much of the pain that GAE-Studio was designed to help with. Then some time later, Objectify-Insight came out, and our visualization engine would be in competition with it. Since we love and have been using Objectify for years, we didn’t want to become their commercial competitor.

Post_gaestudio_v2

Still, we were and are hopeful that GAE-Studio will be useful for our developers. For one thing, GAE-Studio is available to all environments using the Modules, although it was initially written for the Java runtime. This is because Google now provides hooks in the Google App Engine SDK for the things we had to hack our way around to in the past. The further advantage of GAE-Studio is that it can be used locally! While Google has improved the usability of their cloud console a lot, the usability of local development tools is still weak.
Several hundred users have expressed an interest in using GAE-Studio, and we are now ready to officially release it in their hands. We hope you will find GAE-Studio useful, and will help us support the remaining runtime.

Thanks for the support and words of encouragement, and thanks for sticking with us through this venture!

About GAE-Studio

GAE Studio helps you optimize applications hosted on Google App Engine.

GAE Studio also allows datastore exploration, modification, deletion, import and export. Think of it as your swiss army knife for developing GAE applications!

Using real-time analysis of datastore requests, GAE Studio quickly highlights inefficient queries and gathers metrics that will help developers improve application performance.

15 comments

  1. Denis Reilly · March 11, 2015

    I can’t seem to get your Maven instructions to work.
    I add as specified to an my existing GAE maven app and my app works but the gae-studio is not accessible.

    • Christian Goudreau · March 11, 2015
    • Maxime Mériouma-Caron · March 13, 2015

      There was an mistake in the documentation. Please remove the line module and try again

      • dunicaboy · March 16, 2015

        You mean ‘In your appengine-web.xml file, add default’

      • dunicaboy · March 16, 2015

        I did remove default from my appengine-web.xml. It made no difference

    • mmeriouma · March 23, 2015

      Sorry some parts of my comment was cut-off. The guide at http://dev.arcbees.com/gaestudio/ is updated. Please take a look, as it’s a bit harder to put code in comments here

      • dunicaboy · March 23, 2015

        Sorry still doesn’t work

      • Christian Goudreau · March 24, 2015

        Could you add more information about your environment?

        Thanks

      • dunicaboy · March 24, 2015

        I now have it working

        This line ${webappDirectory}/META-INF was the problem
        I changed it to ${project.build.directory}/${project.build.finalName}/META-INF

      • Christian Goudreau · March 24, 2015

        Gotcha, we will change our documentation since ${webappDirectory} is a custom variable that people may not have or have a different value.

  2. Denis Reilly · March 12, 2015

    Sorry, I meant locally.

    • Christian Goudreau · March 12, 2015

      What runtime are you using?

      • dunicaboy · March 12, 2015

        Do you mean GAE version? 1.9.17

      • Christian Goudreau · March 12, 2015

        No sorry, I meant, are you using Java? Go? Php? or Python?

      • dunicaboy · March 12, 2015

        Java with Maven via Eclipse Luna

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s