[erlang-questions] Framework advise
Sat Jul 14 06:33:57 CEST 2012
Good luck developing the prototype Jayson. You may want to give some
reasons why the Frankenstein middleware isn't performing to get the
most helpful responses.
Are you just want to creating an authenticated front-end for a
database? Without knowning more, I would say that facilitating single
sign-on will be the trickest part. Creating a database front end will
be pretty easy. You might want to look at Chicago Boss's Boss_DB
project (https://github.com/evanmiller/boss_db), which will allow you
to easily create an adapter for MS SQL if one doesn't already work for
On 14 July 2012 14:59, Jayson Barley <> wrote:
> I need to show a POC on a rewrite/redesign of an existing Java/CPP code
> base. From my work with Erlang I believe it is the best choice for the job.
> I am seeking some advise on what frameworks would be best to start with that
> will meet my goals. See below for the details. I am willing to listen to any
> feedback on which frameworks would be best or even if Erlang isn't the best
> tool for the job.
> Web standards based - Must support HTML 5, JS, CSS, etc. I am thinking
> Authentication - Users will need to be able to move from one server to
> another without losing their session.
> Template-able - I will need to be able to perform CRUD and retrieve data as
> HTML, XML, JSON, and possibly other formats in the future.
> Scalable - It must support at least 10,000 requests per second. It could be
> higher but based on the next requirement I am starting out small.
> Capable of streaming large amounts of data - It is possible that a REST
> request could contain millions of rows of data. This is rare but it is a use
> case that the existing Tomcat/IIS/Java Frankenstein currently does.
> MS SQL connectivity - Our existing database is MS SQL and that won't be easy
> to change so it needs to be able to connect to it.
> Testable - I will need to be able to write and run Unit, Integration tests.
> I am guessing that eunit and common test will cover this.
> Easily deployable - A new server will need to be deployed and configured in
> minutes. Something like Chef would be ideal since we are already using that
> in other areas.
> In place upgrades - When a new build is ready to deployed we should be able
> to deploy it, leave the previous version in place to roll back should an
> issue be found.
> Easy logging.
> I think that is everything I can think of. If anyone has any questions or
> recommendations on how to make this clearer please let me know.
> Thank you in advance,
> erlang-questions mailing list
More information about the erlang-questions