ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #facebook
When retrieving large collections through the Facebook Graph API, developers often increase the limit parameter to reduce the number of round‑trips. However, raising the limit can also increase server‑side processing and network transfer time, potentially creating a bottleneck before any optimization is applied. The exact point where latency begins to grow d
Facebook Login Token Refresh During User Password Changes Facebook Login for Websites issues short-lived access tokens (typically 1-2 hours) with refresh token mechanisms for extended sessions. The OAuth 2.0 implementation supports automatic token refresh when applications properly implement the refresh flow using the JavaScript SDK or server-side OAuth endp
Rollback Behavior During Staged Deployment Facebook's app upgrade process uses a staged deployment model where new versions roll out to a subset of users before full release. When an upgrade fails, the platform attempts an automatic rollback, but the admin console does not clearly indicate that a rollback is in progress. This creates ambiguity for administra
Integration Boundary The Facebook caching stack couples a distributed Memcached fleet with a globally replicated MySQL tier. Writes flow through MySQL primaries and trigger asynchronous cache invalidations that must reach every Memcached region before the next read observes the new value. Goal and Uncertainty Understand the exact window during which a Memcac
Meta's continuous profiling pipeline ingests custom trace events with high-cardinality dimensions such as request IDs and user segments. The documented architecture uses a columnar storage backend derived from Gorilla principles with label deduplication and compaction, but public materials do not characterize how compaction latency behaves when label cardina
Goal Bound a Graph API query and paginate through a large result set using cursor-based pagination without encountering the (#613) Invalid cursor error. Constraints and uncertainty Cursor tokens expire or become malformed after a short window, and the API does not disclose the total result count, making it difficult to estimate progress. Ordering stability i
Graph API Token Lifecycle A repeatable local development environment relies on consistent access token behavior. Token Expiration Constraints Development-mode apps utilize short-lived user access tokens that must be exchanged for long-lived tokens. What is the precise mechanism to ensure token validity across environment restarts without manual re-authorizat
Trade-off Context Facebook's distributed Memcached layer uses a delete-then-update invalidation pattern backed by a lease mechanism to prevent stampedes. For non-critical feed data the platform favors availability and partition tolerance, accepting a window where stale results can be served after a database write but before the invalidation propagates across
Goal Determine why a production workload intermittently hits 429 or 502 errors during bulk Graph API calls, despite retry logic and documented rate‑limit headers remaining within limits. Context The Java SDK (v12.x+) defaults to a 50‑connection HTTP/1.1 pool per host. HTTP/2 is optional and can be enabled with enableHttp2(true) . The SDK exposes maxConnectio
memcached