Concurrent web scripting language without database access?
My webapp will need to use multiple database turtles and sometimes have to query these shards in parallel. Are there any web scripting languages with mature stable concurrency support without database access? If so, can you point me in the right direction? Free open source source is preferred, but I basically want something that works.
The themes work great for me, but I don't need real multi-threaded support. All I want is five queries with a 10 second database to five different database servers to take 10 seconds, not 50. I don't care how many processors it actually used.
source to share
In fact, it looks like you want parallel non-blocking I / O - you want parallel non-blocking database access, which is usually handled through a different API.
For example, in Java, common I / O is handled through components in java.io and java.net, but database access is handled using java.sql and vendor-specific drivers. Similar characteristics are typical for other platforms / languages.
It would seem that your main problem would be to implement some kind of multiprocessing / multithreading from which you could make separate queries for parallel database access. I believe this is the main area you should explore.
There is a lot of material on this thread, but for most of the details you need to focus on a specific platform / language. Note that this is traditionally a very difficult area of software development.
Regards...
source to share
A possible work-around is to split the web page so that each piece only falls on one shard. The browser has to fire a separate AJAX request for each part and create the client side of the page.
This solution will not be language / framework dependent, but requires client-side JavaScript to be enabled.
Performance may vary depending on each guest OS, browser and settings ( more info ). However, the page will render gradually as soon as data from each part of the page is available.
As disadvantages compared to a server side solution, this technique shifts the complexity from the server to client-side JavaScript and increases the load on the web server.
source to share