Re:Considerations When Planning Endpoints for your RESTful API
by traveldotto1 on Wednesday October 19, 2011 @02:55AM
(#3129055)
Not sure why would you recommend SSL from day one. If the API needs to entertain high throughput and low response time, adding SSL means adding overhead.
[ Parent
| on HN ]
Re:Considerations When Planning Endpoints for your RESTful API
by plq on Wednesday October 19, 2011 @07:29AM
(#3129623)
Avoiding SSL on the grounds of its overhead is premature optimization. Unless profiling reveals that the SSL overhead introduces significant delays (and the cost of getting a proper SSL Certificate is affordable) there's no reason to go without SSL.
Re:Considerations When Planning Endpoints for your RESTful API
by DomreiRoam on Wednesday October 19, 2011 @09:27AM
(#3130012)
If you want to use caching for multiple clients; I don't think you can use SSL. So it depends a lot about the purpose of the API.
Re:Considerations When Planning Endpoints for your RESTful API
by traveldotto1 on Friday October 21, 2011 @03:47PM
(#3141346)
it's all depending on use cases.. that is why I don't think an API should be secured through SSL from day one.. here is an example how SSL can be unnecessary, if i am processing billions of ad request daily with a response time of less than few milliseconds, and operates in a secured environment, why would i need to add a layer of SSL on all the requests..
Use cases drive requirements, not buzz words drive requirements, and that's my whole point