Haxe vs Lua in building a heavy traffic web application

After spending a couple of hours reading on Lua and Haxe I am still unsure of which would be a better choice to use on the development of a heavy traffic web application.

Which one would give us better server performance if our web-app will be working heavily on the server's side? We also want to keep server's resources at a minimum to avoid suffering heavy lag spikes.

Our first thought was using Java/Spring/Hibernate but we read about how it drains a server's resources fast as its usage grows, so we are trying to figure out an architecture that would allow us to handle heavy traffic and give out a good user experience efficiently on the server's side.

By heavy traffic we are talking of 500+ users at the same time requesting da开发者_开发百科ta back and forth from our servers.

Any suggestions outside Lua and Haxe are also appreciated and will be taken into consideration.

Thanks for your time in reading this. =)

You can use Haxe to generate JavaScript with the Node.js type signatures, (here https://github.com/blackdog66/bdog-node). This gives all the great features of Haxe on a very well regarded backend. It's my primary platform.

bd

I've tried Lua as in a self coded WSAPI/Orbit application and it just works nicely. I haven't got a clue about how it scales, but it just works(TM) out-of-the-box with LuaJit, so I guess you can make things blazingly fast.

You can find more information on this on the Kepler project Github site.

You should try Nginx Lua Module that can handle ~30k (yes, thirty-thousand) requests per second, Redis and Nginx Redis Module.

You'll find several Lua web frameworks here: http://lua-users.org/wiki/LibrariesAndBindings

I don't think any particular language is a solution to the problem of "draining a server's resources fast as its usage grows."

Does this application exist already? If so, what is it written in now? If not, how do you know you will have 500 concurrent users?

I don't think 500+ simultaneous users is that big a deal, and it's likely that it will make little difference which technology you choose, so you should choose one that uses a language (or at least paradigm) you understand well. If you like Java, go ahead and use it.

I've used Lua (not Haxe); I like it but it does not have the widespread third-party library availability that other languages like Java or C++ or C or Perl or Ruby or Python enjoy, which is a substantial downside for making web apps.