Today we swapped sun soaked Brisbane for rain soaked Melbourne as we continue on our 3 city Australian Exchange tour. Our final set of presentations are tomorrow (Friday) before we make the long journey back to Boston. OK, I know, you have no sympathy :)
But back to yesterday. Brisbane was completely booked with once again 50+ people attending the day long event. Brisbane certainly has it's own vibe, a little more relaxed than Sydney, but no less eager to participate. During the tour I've been fortunate enough to share the OpenEdge roadmap detailing some of our thoughts and ideas for the next generation of OpenEdge. Out of the potentially many new features, the one stand out proposal that generates the most questions & excitement is that of Multi-Tenancy. Even for those not yet considering Software as a Service (SaaS), the thought of OpenEdge as a platform having built-in Multi-Tenancy capabilities right out of the box is a game changer. Especially, if as hoped, it can be introduced in such a way that means little to no application changes for the thousands of OpenEdge applications out there today. This feature alone would consolidate OpenEdge's leadership in the SaaS space offering end-users a huge library of Multi-Tenant applications almost over night.
As we've seen from other conferences, including the recent Exchange Online, the current hot feature in the product today is the OpenEdge GUI for .NET. Shelley is constantly presenting to packed rooms, full of partners & direct customers eager to know how to make use of this great feature. I had no personal involvement in the project that created it whatsoever, but each time I sit at the back of the room and listen to Shelley go through her pitch, my mind is always blown away by the engineering triumph that basically allows the running of a Visual Studio environment in OpenEdge Architect which is based upon Eclipse. Not only that, but the fact that you can mix & match existing OpenEdge GUI with this next generation OpenEdge GUI for .NET is just a testament to the technical skills within Progress.
As with Sydney, it was also good to see by show of hands how many people are currently using OpenEdge 10 and OpenEdge Architect. I won't get on my soapbox again, but still it's good to see!
From a purely personal perspective, I'm also impressed by the number of people that have taken the OpenEdge Reference Architecture (OERA) to heart and are really embracing it's principles as they take their applications forwards. One of the challenges we always face is knowing how well our best practices materials are being received, and used, so events like this give me the opportunity to talk to partners and gauge feedback. So if you ever see me at any of our events feel free to grab me and give feedback. I won't bite, promise!
We had a fantastic time in Brisbane and certainly from the feedback at the end of day Cocktail party, the attendees were going home happy after a full days content. Or maybe that was just the free booze talking!!
So tomorrow is our final day and if it's anything like the past few days it will be a blast. We did by the way gain our hour back when we flew south from Brisbane to Melbourne, not that I still understand how it works. I had some discussions at the cocktail party about this, but again all the reasons seemed to tie back to the cows! Either that, or it's all about reducing the hours of sun light so as not to fade curtains!!
As always, thanks for reading
View all posts from Mike Ormerod on the Progress blog. Connect with us about all things application development and deployment, data integration and digital business.
Subscribe to get all the news, info and tutorials you need to build better business apps and sites
Copyright © 2019 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.