BT

Facilitating the Spread of Knowledge and Innovation in Professional Software Development

Write for InfoQ
News Articles Presentations Podcasts Guides

Topics

Choose your language

QCon London

Adopt the right emerging trends to solve your complex engineering challenges. Register Now.
QCon New York

Find real-world practical inspiration from the world's most innovative software leaders.
The Software Architects' Newsletter

Your monthly guide to all the topics, technologies and techniques that every professional needs to know about. Subscribe for free.

InfoQ Homepage News Article: RESTful Services with Erlang and Yaws

Design Patterns for Distributed Streaming Data Environments (Live Webinar February 9, 2023) - Save Your Seat

Article: RESTful Services with Erlang and Yaws

Bookmarks

Mar 31, 2008 less than one minute

Write for InfoQ

Join a community of experts. Increase your visibility.
Grow your career.Learn more
In a new InfoQ article, Steve Vinoski, known as one of the world's leading authorities on middleware, takes a look at how to build RESTful web services using the Erlang programming language and the Yaws web server.

Erlang has seen a renewed interest because it is, together with the accompanying Erlang/OTP framework, built specifically to exploit parallel computing resources. In the article, Steve shows how Erlang's features are a match for implementing RESTful services, specifically discussing how to map an application's URI space to Erlang program code.

Check out the full article here.

Inspired by this content? Write for InfoQ.

Becoming an editor for InfoQ was one of the best decisions of my career. It has challenged me and helped me grow in so many ways. We'd love to have more people join our team.

Thomas BettsLead Editor, Software Architecture and Design @InfoQ; Senior Principal Engineer
Write for InfoQ

Rate this Article

Adoption
Style

This content is in the Architecture topic

Related Topics:

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Community comments

  • Repeatability

    by Erik Onnen,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    Hey Steve,

    Thanks for the article. In my own testing, I've seen Yaws fall over and die under a load of ~20 concurrent requests. This really begs the question, what can we do to repeat Joe's tests? The documentation and code of "the test" are sparse, and they aren't public so it's impossible for anyone to reproduce the same numbers. Given that, I can only assume the Yaws numbers don't take into account dynamic content, something that is important to most developers. Any thoughts there?

    -erik

    Back to top
  • Re: Repeatability

    by Erik Onnen,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    Also, I'm curious about your mention of Erlyweb. How many people are maintaining Erlyweb? For those of us who are interested in the comminity there, how many people actively contribute to Erlyweb?

    Back to top
  • Apples And Oranges

    by Paul Tiseo,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    While I am learning Erlang because it seems to be an emergent language I should have in my toolset as a developer, I fear the "famous graph" at the start of the article, used as a teaser, is perhaps misleading.

    First, are Apache and Yaws comparable? How much of Apache's functionality set is found in Yaws? Second, what was the test configuration for that graph? Also, no mention is made of the follow-up benchmarking

    I mean, if a writer starts an article with: "Whether or not you should use X, here's how you'd use X...", shouldn't the "whether or not" part be well-established rather than open to debate?

    Back to top
  • Missing hypermedia

    by Guilherme Silveira,

    Your message is awaiting moderation. Thank you for participating in the discussion.

    Hi Steve,

    Although the example almost reaches REST in a really simple way, it is just missing the HATEOAS point when leaving the hypermedia aspect behind. It is much easier to develop thatn SOAP based solutions, but without hypermedia support, both clients and servers are coupled in a way that REST systems should not.

    Regards

    Back to top

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

BT