Discovering context is the end game of curation The need to filter social networks to create value is a natural reaction to the raw value and size of the networks themselves. via...
I do think the rise of alternative notification channels; sms, mobile push notifications, direct messages on twitter, facebook messaging, etc are going to move some of this kind of thing off of email over time. But today, if you want to drive retention and repeat usage, there isn’t a better way to do it than email. via...
In last few months, we has been developing and iPhone / iPad apps that pull JSON data from an web API frequently. We used Ruby on Rails to do the first version for both website and API service. After trying the first version, customers complained about loading speed. They said that data loading on the mobile app was SLOW. There are two reasons that make Rails based API calls slow: Rails is heavy and blocking (after an API call we do some logging and system shouldn't have wait for logging to return data to clients) Need to join four SQL tables to query data, combine data then convert to JSON Let optimize them! Solutions for (1) are: Rack Apps + Job Queues (Delayed Jobs, Resque …) Non blocking server (Node.js, Goliath …) to fire an action to log info to database, forget it and return JSON to clients Non blocking was chosen because it's fast, it handles more requests and help to avoid managing additional job queues. For (2), de-normalize and pre-calculate JSON is the first step. But there is a table that cannot be de-normalized using SQL. It's listings table that state which item will be showed on which month and in which category. Let say item I will be showed in category C in month M1 and M2 then two rows (I, C, M1) and (I, C, M2) must exist in listings table. After de-normalization and JSON pre-calculation, only it need to join only two tables to get items give a category and a month then combine pre-calculated item JSON and return it to clients. Second step for...
Because vendors of RDBMS technology have little incentive to disrupt a technology generating billions of dollars for them annually, application developers were forced to take matters into their own hands. Google (Big Table) and Amazon (Dynamo) are two leading web application developers who invented, developed and depend on their own database technologies. These “NoSQL” databases, each eschewing the relational data model, are a far better match for the needs modern interactive software systems. via couchbase.com A nice introduction to...
mobile application developer singapore,mobile application development singapore,web development singapore,singapore web design,website developer singapore,graphic designer in singapore,singapore mobile application developer,singapore web development,ruby on rails developer singapore,ios developer singapore,android developer singapore,web application singapore,web design singapore,web development company singapore,app development singapore,singapore mobile app developer,app developer singapore,web design company singapore,ios app development singapore,mobile app development singapore,mobile game developer singapore,web designer singapore,singapore website design,mobile app developer singapore,mobile developer singapore,design agency singapore,website designer singapore,singapore app developer,developers in singapore,developer in singapore,mobile apps singapore,singapore web design services,website development singapore,design firms in singapore,website design singapore,web design services singapore,mobile apps development singapore
