Not looking for any code snippets here, so here goes:Let's say 100,000 users on my web app have authorized my application to connect to facebook (with or without offline_access). I want to build a sort of pull mechanism, whereby when a user posts to their facebook wall, I can grab it from the Graph API and store it locally on my server.I would assume that this would require a call to the Graph API every n minutes to pull their latest wall posts.Ideally, this would be done for Twitter as well. I know LinkedIn does this, but I am not sure of the exact details.Question 1: I'd need to make an individual Graph API call for each user, right?Question 2: If I suddenly bombard the Graph API with 100k Graph API calls, wouldn't I run head-first into the rate limiter?Question 2b: If not, what if I had a million users? Surely...
Conceptually speaking, how would I pull facebook wall posts from 100k users?
design;api;facebook
There's not really any need to build the pull mechanism when you can have Facebook POST you graph updates. I'm not entirely sure about limits on this service.As for your individual questions:Question 1: I'd need to make an individual Graph API call for each  user, right?No. You can issue requests for multiple users. See the Selection section in this doc. However, I'm sure that there's a limit to the number of users that you can query at once (not sure about the number though).Question 2: If I suddenly bombard the Graph API with 100k Graph API  calls, wouldn't I run head-first into the rate limiter?Yep, which is probably why you'd want to have the data pushed to you rather than pulled.Question 2b: If not, what if I had a million users? Surely...Don't build for what you think, or hope you might have.. Build for what you know you have. Refactor and optimize when the time comes. Not now.