Live data from Hacker News

Keep your CRUD off the Internet

ericsink.com

21–24 of 24 posts

Re: Keep your CRUD off the Internet

#21

Like others have stated, I think it depends. Look at your target market. If the market is the USA, mobile connections are getting more reliable and really fast (LTE) and this isn't much of a problem. OP should market this to devs focusing on countries where mobile networks stink.

And where would that be? I thought it was the U.S. which was backwards !! :) (and I live in Uruguay, South America). That said, I'd love it if more of my apps worked offline with sync.

Where? I don't know, but according to the speed test I just ran on my Verizon iPhone 5 I have 30 mbps down and 12 mbs upstream plus 70ms response time. With that speed/latency combo, poor network connection quality and offline syncing just isn't a problem that needs to be solved.

Re: Keep your CRUD off the Internet

#22

Earlier quoted context omitted.

And where would that be? I thought it was the U.S. which was backwards !! :) (and I live in Uruguay, South America). That said, I'd love it if more of my apps worked offline with sync.

Where? I don't know, but according to the speed test I just ran on my Verizon iPhone 5 I have 30 mbps down and 12 mbs upstream plus 70ms response time. With that speed/latency combo, poor network connection quality and offline syncing just isn't a problem that needs to be solved.

I was agreeing with you, I just was saying that it was the U.S. which often lagged in cell phone standards adoption, so if the U.S. has great conectivity, and even South America has good connections (I have a slower connection but it's at least 1 mbps, more than enough for a CRUD app !!! ), where do they need that cache? Africa? And I've read that they have pretty decent cellphone infrastructure there, having bypassed landlines entirely, so maybe not even there.

Summary: with good cellphone connections everywhere, one of the points is not as strong. There still are dead spots, but enough to warrant the extra complexity of sync?

Re: Keep your CRUD off the Internet

#23

Earlier quoted context omitted.

Where? I don't know, but according to the speed test I just ran on my Verizon iPhone 5 I have 30 mbps down and 12 mbs upstream plus 70ms response time. With that speed/latency combo, poor network connection quality and offline syncing just isn't a problem that needs to be solved.

I was agreeing with you, I just was saying that it was the U.S. which often lagged in cell phone standards adoption, so if the U.S. has great conectivity, and even South America has good connections (I have a slower connection but it's at least 1 mbps, more than enough for a CRUD app !!! ), where do they need that cache? Africa? And I've read that they have pretty decent cellphone infrastructure there, having bypasse…

Good points.

Re: Keep your CRUD off the Internet

#24
post #3

Nice approach; I like going through the SQLite API.

cough WebSQL cough So many apps, HTML5 or native, could benefit from an offline sync story. That wheel doesn't need to be re-invented over and over again. This reminds me a lot of WebSQL, which I've always been sad was killed.

The cool thing about using SQLite as a basis for sync is that it leverages all that we know re: RDBMS merging, syncing and conflict resolution at scale. And, from a skills perspective, leverages our team's existing knowledge in SQL.

We have use cases where mobile devices may be offline for minutes at a time (in hotels and conference halls where wireless is either sketchy or un-usably slow). I can definitely see us using this. I may check out the Couch thing as well, although we use Cassandra for NoSQL scenarios.

Post reply on HN