recentpopularlog in

mcherm : apidesign   30

Adrian Sampson: FPGAs Have the Wrong Abstraction
FPGAs can be used for more than circuit emulation (just as GPUs can be used for more than graphics). But of the language for expressing such programs does not yet allow this kind of use.
hardware  programming  APIDesign  via:reddit 
june 2019 by mcherm
OpenAPI Specification | Swagger
The specification for APIs (formerly swagger, now OpenAPI).
refs  standards  REST  APIDesign 
may 2019 by mcherm
How not to design a wire protocol | Armed and Dangerous
Wire protocols can be binary or readable. The binary ones save space; the readable ones are self-documenting. Personally, I wonder if something like protocol buffers can do both... saves space AND once identified the documentation is complete and available. Only the last point is missing.
EricRaymond  via:HackerNews  APIDesign  networking 
march 2019 by mcherm
REST is the new SOAP – Pakal De Bonchamp – Medium
REST is a bunch of overly complicated and inconsistent conventions that get in the way of simple remote procedure calls without adding any real benefit.
via:reddit  REST  APIDesign  api 
december 2017 by mcherm
API design: Choosing between names and identifiers in URLs
Use fixed but meaningless URLs for permalinks and readable URLs for more of a "search" functionality.
REST  APIDesign  api  via:HackerNews 
october 2017 by mcherm
Roy Fielding on Versioning, Hypermedia, and REST
Roy Fielding says "Don't" version your APIs. Use "hypermedia" instead. And if you really MUST version them, just use a new server. Interesting viewpoint, but not an appropriate solution for the problems that *I* solve which are mostly internal to a single company.
via:HackerNews  REST  APIDesign  versioning 
june 2017 by mcherm
Scaling your API with rate limiters
When building APIs, you should create rate limiters. This article describes why Stripe thinks this is so important, and how they build theirs.
APIDesign  api  programming  via:HackerNews 
march 2017 by mcherm
REST APIs must be hypertext-driven » Untangled
Roy Fielding complaining about people using his term "REST" the wrong way.
REST  RoyFielding  programming  api  APIDesign 
february 2017 by mcherm
API Design Guide  |  Cloud APIs  |  Google Cloud Platform
Google's API Design document. Their section on Resource Names and Standard Methods, in particular, are a pattern I strongly endorse.
google  APIDesign  via:HackerNews 
february 2017 by mcherm
A Localization Horror Story: It Could Happen to You
A story of just how hard it can be to build in support for localization (support for multiple languages) and an approach to creating a library which will do it.
programming  APIDesign  i18n  via:HackerNews 
january 2015 by mcherm
I don't need your permission!
The need for certain android permissions can be avoided by using intents to let a system app handle it.
APIDesign  android  programming 
december 2014 by mcherm
Simplicity and Utility, or, Why SOAP Lost
JSON over REST was simpler than SOAP so it won. I will note that it is LESS elegant in many ways... but that didn't matter. So I think deep-set dislike for SOAP was part of it also: people were HOPING to get rid of it.
soap  JSON  APIDesign  via:HackerNews 
december 2014 by mcherm
The Worst API Ever Made
No, really: it's a serious contender for worst API design ever.
APIDesign  programming  via:reddit 
august 2014 by mcherm
It is okay to use POST » Untangled
Roy Fielding, the inventor of REST says "It's OK to just use POST for stuff."
api  APIDesign  programming 
august 2014 by mcherm
Write libraries, not services | David R. MacIver
"Services are not so easily refactored, so build things as code libraries at first until the interfaces have evolved and hardened somewhat, THEN expose as APIs if you find that you want to."
api  APIDesign  via:DavidMacIver  DavidMacIver 
march 2014 by mcherm
Fanout Blog » How to safely invoke Webhooks
Web hooks could direct you to a malicious URL that's inside your own network, causing your (privileged) machine to make a possibly destructive request. To prevent this, check the IP address before calling the web hook.
security  webdevelopment  programming  webhooks  api  APIDesign  via:HackerNews 
january 2014 by mcherm
Enterprise Integration Using REST
Some thoughts on REST API design from Brandon Byars of ThoughtWorks.
REST  APIDesign  via:MartinFowler 
october 2013 by mcherm
OAuth of Fealty - Facebook's APIs - Ian Bogost
Why Facebook's APIs are so bad: they don't really care about the developers and, as a result, the APIs are poorly designed and worst of all they change constantly.
api  APIDesign  facebook  via:HackerNews  programming 
august 2013 by mcherm
Ponderous Programmer: Forward compatible data consumption
Ignore things you can't process and it'll make room for people to extend your format later.
APIDesign  via:JoeCampbell 
december 2012 by mcherm
Discovering a Major Security Hole in Facebook's Android SDK
How the Facebook SDK had a serious security bug. How someone found it, reported it, and it was handled well. And how it was particularly difficult to fix because it was a bug in an API.
security  api  APIDesign  bug  facebook 
april 2012 by mcherm
Don't Skimp on Documentation
You need good docs for your API.
api  APIDesign 
january 2012 by mcherm
REST worst practices
Some thoughts on REST, particularly what's BAD to do.
APIDesign  REST  via:HackerNews  programming 
january 2012 by mcherm
Twitter’s poor API documentation practices
Twitter's documentation didn't say that when a certain value get over 100 they return the string "100+". I should make all of our API designers read this.
APIDesign  twitter  progamming  via:HackerNews 
january 2012 by mcherm
The OAuth Chronicles: I am not Stupid
OAuth is hard for client apps, especially on iOS.
APIDesign  api  OAuth 
december 2011 by mcherm
Daring Fireball: Twitter's Shit Sandwich
Twitter will now force all clients to use oauth. That's a crummy user experience for native apps.
twitter  authentication  oauth  security  APIDesign 
may 2011 by mcherm

Copy this bookmark:





to read