A polyglot web framework<br />
Optimized Java Script ( JS byte code)<br />JS Generator/GWT<br />HTTP/HTTPS<br />Browser/Client<br />UI Component<br />Nat...
Motivation<br />GWT implementation is a natural fit and provides nice decupling between client side code and server side c...
Presentation Layer :<br />Java script is always browser dearer and JS got matured and optimized over the years and still e...
Web Server :<br />Web server manages the HTTP/HTTPS request and responses.<br />
Application Layer :<br />Write business rule with preferred languages like java, scala, groovy etc. to get the best of eac...
ORM Layer :<br />This layer decouples from the underlined data layer and could be talking to SQL/NOSQL databases.<br />
of 7

Native web architcture

Published on: Mar 3, 2016
Published in: Technology      
Source: www.slideshare.net


Transcripts - Native web architcture

  • 1. A polyglot web framework<br />
  • 2. Optimized Java Script ( JS byte code)<br />JS Generator/GWT<br />HTTP/HTTPS<br />Browser/Client<br />UI Component<br />NativePolyglot app<br />Service Connectors<br /> Web Server<br />SQL/NO SQL<br />App server<br />Cache Layer<br />Application Layer<br />JVM<br />ORM Layer<br />DB<br />DB<br />DB<br />DB Layer<br />
  • 3. Motivation<br />GWT implementation is a natural fit and provides nice decupling between client side code and server side code.<br />Currently it offers the Java code to generate equivalent JS code and this can be extended to any language.<br />This will be still simpler in case a polyglot ecosystem as Java components can be called from any language which runs on JVM.<br />
  • 4. Presentation Layer :<br />Java script is always browser dearer and JS got matured and optimized over the years and still evolving.<br />Taking GWT approach in converting the java code to JS byte code would allow developers to call these components and generate equivalent JS byte code which in turn rendered in browser.<br />The developers really need not to worry about JS and they can use their preferred language to manage these UI components and their life cycle.<br />GWT is based on ajax and this frees up the developer from managing ajax specific code. <br />
  • 5. Web Server :<br />Web server manages the HTTP/HTTPS request and responses.<br />
  • 6. Application Layer :<br />Write business rule with preferred languages like java, scala, groovy etc. to get the best of each language domain.<br />Polyglot provides and intuitive and elegant way to define the business problem in the language which will be more appropriate rather than trying to solve everything using a single language.<br />
  • 7. ORM Layer :<br />This layer decouples from the underlined data layer and could be talking to SQL/NOSQL databases.<br />

Related Documents