S
Subbu Allamaraju
subbu.org · Personal blog · on HN since 2007
Subbu Allamaraju, an engineer with experience at Yahoo and eBay, writes about APIs, cloud infrastructure, engineering leadership, and career.
What HN saysOne commenter calls him the proponent of REST who speaks the most sense; others link his posts on Node.js vs Play and API pain.
43HN people shared it
5linked it in comments
68stories submitted
418story points
6 months agolast shared
2007people per year2026
Most-shared posts
- 1Nodejs vs Play for Front-End Apps3 people · 28 points · first shared 2011 · 13 comments on HN
- 2Don't build private clouds2 people · 68 points · first shared 2016 · 73 comments on HN
- 3Taming the Rate of Change2 people · 22 points · first shared 2018 · discussion on HN
- 4OpenStack is Not Cloud2 people · 7 points · first shared 2013 · discussion on HN
- 5Automate Everything – But Don’t Ignore Drift2 people · 4 points · first shared 2014 · discussion on HN
- 6My Leadership Document – 2021 Edition2 people · 4 points · first shared 2021 · 1 comments on HN
- 7Click Ops2 people · 3 points · first shared 2013 · discussion on HN
- 8Shaping Your Authenticity2 people · 3 points · first shared 2023 · discussion on HN
- 9Mid Career Stuckness2 people · 3 points · first shared 2023 · 1 comments on HN
- 10How to Think About Multi-Cloud2 people · 2 points · first shared 2017 · discussion on HN
- 11Leading vs. Participating1 people · 67 points · first shared 2022 · 26 comments on HN
- 12Give Me Bare-Metal1 people · 47 points · first shared 2014 · 47 comments on HN
- 13Contemporary Views on Serverless and Implications1 people · 46 points · first shared 2018 · 12 comments on HN
- 14MVC may be Slowing Down Your Site1 people · 18 points · first shared 2012 · 16 comments on HN
- 15Tangled Mess1 people · 13 points · first shared 2025 · 2 comments on HN
What HN people wrote when they linked it
robinhowlett · 2011-08-22
Subbu Allamaraju (ex-Yahoo, now eBay) has been the one proponent of REST that I believe speaks the most sense.
He understands that most "RESTful" APIs out there leave HATEOS as an afterthought, but he doesn't believe there is such a thing as a 100% RESTful API - you match the architectural style to the context of the problem you are trying to solve.
http://www.subbu.org/
kls · 2012-02-24
This will go into detail far more than I can in a post. http://www.subbu.org/blog/2008/04/nouns-and-resources but the tl;dr is REST nouns are a construct in which you identify all of your objects in a system, these become your REST endpoints such as User in which you have GET, POST, PUT, DELETE each of these verbs causing a specific action on the object or noun. This works great for a large portion of the application but there are some areas such as transactions where it is very hard to logically turn the action into a noun and make it understandable. Sometimes we need the back end to orchestrate multi-step actions and the noun construct just does not convey the workflow. When this happens some people choose to use verb systematic such as generatePDF while still maintaining the REST HTTP actions while others tend to strictly adhere to making said process a noun which can effect readability.
mjs · 2011-12-04
Ah, looks like this is the library Subbu Allamaraju refers to at http://www.subbu.org/blog/2011/11/apis-are-a-pain--the aim of ql.io is to alleviate the challenges of "aggregation, parallelization, and orchestration of forks and joins." (i.e. in practice, "consistent RESTful APIs don’t matter as much as we think," nice though they may be.)
Spearchucker · 2011-12-02
OAuth is an authentication mechanism, meaning it implements a principle of logic stating that a subject is who he/she claims to be (authN), and then asserts that to a relying party (authR). In other words, OAuth establishes identity.
Your question about MITM is answered at http://www.subbu.org/blog/2010/09/oauth-2-0-and-cookie-convergence.
s3u · 2011-03-28
Point well taken - there was no such intention. I updated the charts to show req/sec and mean response time separately. See http://www.subbu.org/blog/2011/03/nodejs-vs-play-for-front-end-apps