Welcome to Scribd, the world's digital library. Read, publish, and share books and documents. See more
Standard view
Full view
of .
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1
Hypernumbers Whitepaper - Using Erlang In Web Startups

Hypernumbers Whitepaper - Using Erlang In Web Startups

Ratings: (0)|Views: 407|Likes:
Published by hypernumbers
A white paper describing the use of Erlang in a web startup
A white paper describing the use of Erlang in a web startup

More info:

Published by: hypernumbers on Jun 10, 2010
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as DOC, PDF, TXT or read online from Scribd
See more
See less





A White Paper: Using Erlang In A Web Start-Up
This White Paper was originally published anonymously on Philip Wadler’s blog
in the summer of 2005 where it was called Erlang Service Architectures.The work in it informed our previous start-up (called vixo.com) which was a social network usingSMS instead of web technology.We built the entire proposition using the precepts discussed herein. Were I to rewrite it I wouldremove the references to Eddie, but apart from that it stands up very well to the actual experience of  building a commodity-priced Google-scale application in Erlang.The business proposition behind that was that at the time Yahoo could monetize pages at 0.03¢ per  page whereas SMS services were monetising at 2¢ - 20¢ per message. So if you can find a modelthat works well on the web and make it work in SMS you can coin it.Social Networks on SMS however proved to be a dead end – at least for us – we were unable to getany uptake. If you have an immediate need for such a system tested and written in Erlang we havethe source code and are open to almost any reasonable offer 
.The irony of course is that the name vixo.com is becoming increasingly valuable. It appears to bethe only tangible output of 18 months work. But the real value came from the experience of  building software in Erlang in anger.
About The Author
Gordon Guthrie
is the CEO/CTO of hypernumbers.com
We might even open source it – better to be used than dumped. It has all the weaknesses of a firstmajor system written in a new language – particularly one that has not had the disciplines of real production rewrites.
This document outlines the service issues in the implementation of conventional n-tier physicalarchitectures.
The purpose of this document is to outline the implementation (and profitability) consequences of software design domains for the construction of enterprise software applications – with particular regard to the selection of Erlang/OTP for such a task.
The scope of this document is a 3-tier logical application architecture – subject to the followingassumption:
the client interface is a browser 
– that is to say it performs no business logic or validation
There is a clear difference between two separate domains:
-ilities-ality (ie functionality) pertains to the ability of a piece of software to perform certain tasks and is auser-facing process. “Does your software do this, enable that, allow the user to do the other…?”By contrast the –ilities pertain to the management of the whole system, they are:
 performabilityThe scope of this paper is the –ilities and
the –ality.
canonically, but not necessarily, a web browser running on some class of ‘personal computer’
web applications typically offer javascript validation of input data for the users convenience, but they revalidate allinput at the server side – the client is not trusted to provide not invalid input

Activity (3)

You've already reviewed this. Edit your review.
1 thousand reads
1 hundred reads
zorg liked this

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->