• Imaginos
    link
    English
    181 year ago

    Looks like the app wasn’t developed with a scalable architecture from the start, then they strapped some caching out of desperation when users started flocking, and didn’t consider the invalidation parameters for private pages correctly.

    • @StateMachine
      link
      Interlingua
      11 year ago

      It’s a little bit baffling. It’s not like they couldn’t have predicted this server load. I know it’s tricky to foresee bottlenecks in some situations but them adding caching (a very basic thing for scalability) at the last minute belies a lack of either experience, forethought, or knowledge, I am not sure which.