4 ms·

How would the Service Objects approach work with Z-axis scaling?

• eeperson 12y ago
  What do you mean by z-axis scaling?
  • q4814 12y ago
    I'm guessing it's a joke. Y=vertical scaling, X=horizontal scaling, Z=? scaling
    • bullines 12y ago
      X-axis scaling: running multiple identical copies of an application behind a load balancer Y-axis scaling: splitting the application with functional decomposition (a server for account info, another for catalog, etc.) Z-axis scaling: each server runs an identical copy of the application (like X-asis) but each server is responsible for only a subset of the data - some other component of the system is responsible for routing each request to the appropriate server (Ex: sharding)
      • alexchamberlain 12y ago
        Why not just call it sharding? There's enough jargon as it is!
        • sciurus 12y ago
          Because when you treat those three aspects of scaling as dimensions of a cube, you can visualize what it means to scale on different axes. See this diagram http://akfpartners.com/techblog/wp-content/uploads/2008/05/app_cube.png http://akfpartners.com/techblog/wp-content/uploads/2008/05/a... taken from http://akfpartners.com/techblog/2008/05/08/splitting-applications-or-services-for-scale/ http://akfpartners.com/techblog/2008/05/08/splitting-applica.... For in-depth discussion, see the book The Art of Scalability. http://theartofscalability.com/ http://theartofscalability.com/
        • bkeroack 12y ago
          You get to sound smart when you compel people to ask what jargon-word X means.
• nl 12y ago
  (now that I understand Z-axis scaling means sharding: whoever thought up that term was on something)... There's no real problem with sharding using service objects: you parameterize them to determine what shard they are serving. There are issues with replacing one if it goes down, or adding in a new one, or hot shards vs unused ones, but these are all familiar with any kind of sharding.