A closer look at the service oriented nature of QAFE
Different technologies communicate more and more using specific protocols or web services. At the same time, the importance of a clear separation between the presentation layer and the underlying code becomes increasingly clear. Many (browser) plug-in technologies already use this idea, such as Adobe Flex (MXML) and Microsoft SilverLight (XAML), but now non plug-in technologies are also being used, such as Google Web Toolkit with UI Binder and the ZK Framework.
Languages
All these technologies and especially the declarative presentation components are quick to learn. However, there is always an accompanying language you need to master to achieve interaction of components and back-end integration. In Adobe Flex, you need to know Action Script and for the back-end you may need to know Java or another language. The Google Web Toolkit also requires a lot of Java knowledge.
As a result, these technologies, although they define the modern web application landscape, demand a lot of prior knowledge. Oracle developers who do not want to start all over again, have to continue to use Oracle tools to bridge the gap to the web. But no matter how you want to look at it: it is patchwork on the front-end and a stalemate on the back-end.
This is because most SOAs are able to tie things together, but the services are not intelligent by definition. The data and the logic remain in the familiar (often obsolete) environment, unless you work with data orientated web applications, such as Flex and GWT. But which of the two would you choose (if it was a choice between those two only)?
Choice?
Thanks to QAFE, you do not have to choose. By developing an XML programming language, called QAML, Qualogy created, within QAFE, a data oriented business layer that offers some interesting advantages. This technique can be accessed from the QAML base, for GWT, Adobe Flex, Adobe AIR (and any other Web 2.0 standard: also keep in mind HTML5 features, such as WebSockets in the future!).
This has made the business layer truly technology independent. Besides, developers still have the option to work with services within QAFE. Developers can continue to develop in their favorite technology.
In true IT jargon, this is called ‘investment preservation’. You do not have to rebuild everything. However, and that is where QAFE distinguishes itself, if you want to you can.
