Comments on: Concurrent Erlang: Watch out, API developers! http://davetroy.com/posts/concurrent-erlang-watch-out-api-developers Design, Entrepreneurship, Economics and Software Tue, 08 May 2012 16:58:00 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Dave Troy http://davetroy.com/posts/concurrent-erlang-watch-out-api-developers#comment-11 Dave Troy Mon, 12 Nov 2007 01:59:00 +0000 http://dave.popvox.com/?p=9#comment-11 Geoffrey - I agree entirely; badly designed code that stresses APIs unnecessarily makes no sense.<br/><br/>That said, a well-designed algorithm that benefits from fast, concurrent access to an API shouldn't be arbitrarily constrained in terms of number of requests per second.<br/><br/>If we need to impose limitations today because of the way that APIs are designed and implemented, that is understandable. But ultimately if Erlang gains popularity for developing client-side algorithms, I'd say it's a pretty good bet that Erlang will gain popularity on the server side as well.<br/><br/>The current Web 2.0 paradigm is not geared towards parallel, concurrent algorithms. Maybe Erlang will lead people down this path. Geoffrey – I agree entirely; badly designed code that stresses APIs unnecessarily makes no sense.

That said, a well-designed algorithm that benefits from fast, concurrent access to an API shouldn’t be arbitrarily constrained in terms of number of requests per second.

If we need to impose limitations today because of the way that APIs are designed and implemented, that is understandable. But ultimately if Erlang gains popularity for developing client-side algorithms, I’d say it’s a pretty good bet that Erlang will gain popularity on the server side as well.

The current Web 2.0 paradigm is not geared towards parallel, concurrent algorithms. Maybe Erlang will lead people down this path.

]]> By: topfunky http://davetroy.com/posts/concurrent-erlang-watch-out-api-developers#comment-10 topfunky Sat, 10 Nov 2007 17:55:00 +0000 http://dave.popvox.com/?p=9#comment-10 Hammering a server with requests has always been bad form. My general understanding has been that issuing more than one request per second is rude.<br/><br/>Some services limit API consumers to a certain number of requests per hour to discourage developers from writing programs like this. Hammering a server with requests has always been bad form. My general understanding has been that issuing more than one request per second is rude.

Some services limit API consumers to a certain number of requests per hour to discourage developers from writing programs like this.

]]>