The End of Safe Harbor and a Scary Path Forward

Re:The End of Safe Harbor and a Scary Path Forward by tlarkworthy on Wednesday October 07, 2015 @01:34AM (#10344327)

No it isn't, average page load is much higher. It's a huge struggle to get below 300ms. Adding 100ms on its own is not insanely bad, but the head of line blocking would probably be terrible and that's what would annoy you most.

EDIT: to those downvoting try cold loading google.com, I get > 200ms within San Francisco. 100ms is not "insanely" bad, and maybe a good price to pay for regulated data privacy

[ Parent | on HN ]

Re:The End of Safe Harbor and a Scary Path Forward by bobfunk on Thursday October 08, 2015 @12:30AM (#10350902)

But it's 100ms each way for every database request while rendering the page! There's not a lot of apps out there that can do with 1 request to their database during an average page load.

[ Parent | on HN ]

Re:The End of Safe Harbor and a Scary Path Forward by Retric on Thursday October 08, 2015 @10:20AM (#10352919)

If you actually had that limitation you could redesign the overwhelming majority of apps to only need 1 DB request/response. EX: Stored procedure or map reduce

[ Parent | on HN ]

Re:The End of Safe Harbor and a Scary Path Forward by tlarkworthy on Thursday October 08, 2015 @02:00AM (#10351151)

I think we would adapt. GraphQL and http/2 are steps in the right direction but I expect we would move faster with a strong incentive :)

[ Parent | on HN ]