• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Tim Cooke
  • Campbell Ritchie
  • Ron McLeod
  • Junilu Lacar
  • Liutauras Vilda
Sheriffs:
  • Paul Clapham
  • Jeanne Boyarsky
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Piet Souris
  • Carey Brown
Bartenders:
  • Jesse Duncan
  • Frits Walraven
  • Mikalai Zaikin

WaveMaker - Memory usage and Performance

 
Ranch Hand
Posts: 398
Android Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

How efficiently WaveMaker handles the Memory usage and performance side?

Is there any special reason why WaveMaker uses browser as the base container?
 
Wavemaker Support
Posts: 3
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

How efficiently WaveMaker handles the Memory usage and performance side?



The resulting app created when you use WaveMaker Studio is a standard Java/JavaScript application. The backend is a Java container (Tomcat, WebSphere, WebLogic, JBoss, Glassfish, etc) running Spring. The frontend is JavaScript, leveraging Dojo. Performance and memory is comparable to apps built in that architecture.

Is there any special reason why WaveMaker uses browser as the base container?



Are you asking "Why does WaveMaker Studio run in a browser?" There are a number of reasons:

1. WaveMaker is built using WaveMaker.
Applications built with WaveMaker are deployed in a browser. Since WaveMaker Studio is build in WaveMaker, it's deployed in a browser. In other words, we eat our own dog food.

2. Shorten code, build, test cycle
The application that you build in WaveMaker will be presented in a browser. When you are building your application in WaveMaker you see what the app looks like in the browser. You don't need to go through a code-build-test cycle. It's all there in Studio. WaveMaker Studio has a LiveLayout feature that displays the information from your Java container services. If, for example, a widget gets information from a database then the Hibernate service is executed within Studio, allowing you to see the application data while you are developing. With LiveData in the development Studio you have a complete view of the visual (widgets and their interactions) and non-visual (backend service integration) behaviors of your application. All this is available within Studio.

3. Integration with other software products
WaveMaker is also embedded within other software products. These other products are build as web applications so the WaveMaker Studio architecture is a natural fit.

4. Software as a Service
Since WaveMaker Studio is a web application we are able to deliver the Studio as a SaaS solution. See WaveMaker Cloud Beta for more information.
 
Mourouganandame Arunachalam
Ranch Hand
Posts: 398
Android Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
That's really interesting Derek !

Thanks !
 
pie. tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
reply
    Bookmark Topic Watch Topic
  • New Topic