high level componentization as a way of efficient server
play

High-level Componentization as a Way of Efficient Server-side Logic - PowerPoint PPT Presentation

High-level Componentization as a Way of Efficient Server-side Logic Implementation in Ubiq Mobile Platform Alexandra Grazhevskaja s.grazhevskaja@ubiqmobile.com Saint-Petersburg National Research University of Information T echnologies,


  1. High-level Componentization as a Way of Efficient Server-side Logic Implementation in Ubiq Mobile Platform Alexandra Grazhevskaja s.grazhevskaja@ubiqmobile.com Saint-Petersburg National Research University of Information T echnologies, Mechanics and Optics Valentin Onossovski Dmitriy Timokhin v.onossovski@ubiqmobile.com dmitriy.timokhin@ubiqmobile.com Saint-Petersburg State University Saint-Petersburg State University

  2. Mobilization of business applications MBaaS emergence Problems in business applications’ mobilization. • The importance of easy-to-develop backend and its mobile access. Emergence of MBaaS (StackMob, FeedHenry, AppEngine, • etc.). Insufficient abstraction level of MBaaS systems’ • functionality.

  3. Modern mobile application • Simple application. • Average complexity application. • Distributed mobile application for business: Full variety of platforms, devices and screen resolutions support Versioned and customizable applications High reliability and fault tolerance

  4. Application constructors-based approach • Simple UI - “ready to wear” components. • Simple business logic - “screen flow” transitions description. Conclusion: Development and deployment of simple applications. Business applications - fast prototyping only .

  5. Existing MBaaS tools-based approach Client-side – standard developments tools. Server-side backend - MBaaS systems. • Third-party UI libraries. • Low-level business problems – MBaaS systems. Conclusion: Simple and average complexity applications. Business logic complexity is limited by MBaaS functions abstraction level.

  6. Enterprise level solution and web services-based approach Business logic backend - enterprise-level solution. Connection protocol – web services. • UI – Web technologies. • Business logic – any abstraction level. • Externals easy integration. Conclusion: Connection protocol is limited. Resulting applications are too “heavy”. No content generation and server-side event management. Web UI is inefficient and poor .

  7. Our proposal - “High level integration” approach Business logic backend – server components: • Big, universal, highly integrated, customizable. • Any abstraction level. • “Building blocks” encapsulating self -sufficient fragments of business logic.

  8. Our proposal - “High level integration” approach Opportunities of enterprise-level approach + usability of MBaaS. • Complex business logic of any abstraction level. • Server components implement business process items. • Integration of any business verticals. • No unnecessary traffic consumptions. • Creating components “in one click”.

  9. Basic requirements to the “host” environment Platform-level support of relatively big server-side • independently running components. Mechanism of components’ interaction. • As addition - IDE-level support of integrated • components.

  10. Implementation in Ubiq Mobile platform Platform features: Ultra-thin client-based architecture. • Safe disconnections – saving users’ sessions. • Cross-platform deploy. • Applications: custom and services. • Server core: • Communication with mobile devices Applications’ management and interactions Services over server core through API. • Plug-in for Microsoft Visual Studio. •

  11. Implementation in Ubiq Mobile platform Database service Dispatcher service Auth. service Server core

  12. Case study - Dispatcher Component Componentization of users’ interactions : Authentication; • Interactions’ management; • Storing persistence data. • Logical model of users’ interactions: users and dialogs.

  13. Dispatcher-application interaction • One Dispatcher – one application type. • DispatcherAPI object - locally instantiated in application. • API methods wrap messaging to Dispatcher. • Result – meaningful data or error code.

  14. DispatcherAPI DispatcherAPI functionality: User authentication and registration; • Obtaining information about users; • Dialogs processing; • Inter-user communications. •

  15. Dispatcher usage

  16. Conclusion • High- level integrated “building block” for server side backend. • Libraries of components – fragments of business processes. • Effectiveness of particular implementation. • Components’ extending directions. • Not Ubiq-Mobile locked.

  17. Thank You for Your attention!

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend