Skip to main content

Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Dirigible » High-performance & scalable Runtime(What would be the target architecture and components for a high-performance & scalable Runtime)
High-performance & scalable Runtime [message #1713884] Sat, 07 November 2015 14:22 Go to next message
Nedelcho Delchev is currently offline Nedelcho DelchevFriend
Messages: 57
Registered: May 2013
New issue is created to track the work log:

As of now Dirigible's projects have simple structure with sub-folders separated by type of the artifacts. The main idea is to see how to have a structure like:

1. Place the static content (WebContent stuff) in the 'right; place in a Tomcat (or other) web server. To be easy optimized to CDN of choice of PaaS provider.
2. Pre-transformed wiki pages (WikiContent) to HTML content and also put to the corresponding place.
3. Pure standard Servlet to "JavaScript" engine bribge
4. Pre-compiled Java services to classes to skip the in-memory compilation at production servers.


1. this should be implemented as a standard web application (no-OSGi),
2. bundled as ROOT.war
3. should provide the standard Registry UI with all the features there (?)
4. on import of or 'registry' zip content to execute all the standard tasks - db creation from models, job starting, and what is necessary for the above
5. Injected Services integration on place
Re: High-performance & scalable Runtime [message #1714493 is a reply to message #1713884] Fri, 13 November 2015 08:22 Go to previous message
Nedelcho Delchev is currently offline Nedelcho DelchevFriend
Messages: 57
Registered: May 2013
Related to this topic is also the integration of the Google's V8 engine as execution engine for JavaScript.
The work activity can be tracked at the bug

There is a quick win option with J2V8 bridge by Ian Bull from Eclipsesource

There are a few integration have to be done:
1. CommonJS support (at least what is required by Dirigible)
2. Injected API - here should be constructed a new simplified API with only primitives as input/output parameters of the functions
3. Debug support - better to be exposed to Chrome Dev Tools (client/server unified experience), but integration with Debug Perspective in Dirigible is also an option.
Previous Topic:A/B Testing
Next Topic:NoSQL support with TinkerPop
Goto Forum:

Current Time: Wed Jan 26 12:05:52 GMT 2022

Powered by FUDForum. Page generated in 0.01913 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top