Slashdot Mirror


Low Redundancy Data Centers? Providers Adapt As Tenants Seek Options (datacenterfrontier.com)

1sockchuck writes: Data center providers are offering space with less power infrastructure than traditional mission-critical facilities, citing demand from customers looking to forego extra UPS and generators in return for more affordable pricing. The demand for "variable resiliency" space reflects a growing emphasis on controlling data center costs, along with a focus on application-level requirements like HPC and bitcoin mining. Data center experts differed on whether this trend toward flexible design was a niche, or a long-term trend. "In the next 12 months,data center operators will be challenged to deliver power to support both an HPC environment as well as traditional storage all under one roof," said Tate Cantrell, CTO at Iceland's Verne Global. "HPC will continue the trend to low resiliency options." But some requirements don't change. "Even when they say they're OK with lower reliability, they still want uptime," noted one executive.

57 comments

  1. Variable resiliency? by sinij · · Score: 5, Insightful

    Now that variable resiliency data centers are finally available, I can run my sometimes available services in the partially secure cloud space I am building.

    1. Re:Variable resiliency? by ls671 · · Score: 2

      Yeah, planning in advance for quantum computing where everything is relativistic, including up time, I just provisioned 8 identically configured cloud nodes with different variable resiliency providers with every provider guaranteeing a 75% uptime.

      This allows me to have 99.9984800% uptime given the probability that all nodes are down at the same time.

      --
      Everything I write is lies, read between the lines.
    2. Re:Variable resiliency? by Hognoxious · · Score: 1

      You're building one? I'm only thinking about building it. Well, more like sort of thinking about it.

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
  2. "OK with lower reliability,they still want uptime" by Anonymous Coward · · Score: 0

    Great, now they just have to pick one of those.

    Problem solved.

  3. Re:"OK with lower reliability,they still want upti by Anonymous Coward · · Score: 0

    Why? Failover keeps high uptime even if you have less reliable hardware.

  4. Wait, what? by HideyoshiJP · · Score: 3, Insightful

    I'm reading this as.. "Well, we need to have redundancy, and we're already ponying up this much money, but how can we spend less and still say we're "redundant?" I'm not faulting the datacenters for offering such a service, but the customers should really have a hard look in the mirror.

    1. Re:Wait, what? by R3d+M3rcury · · Score: 2

      Again, a particular service is not mission critical, so we don't need to spend the money to make it so. Things like test servers and the like could fall into this category. After all, you really don't need 99.999997% uptime for this.

      At least until the power goes out at the data center and you've got a room full of testers and developers sitting around waiting for it to come back on and there's a deadline looming. Then you don't look so smart for saving an extra few bucks a month.

      I wonder how dynamic the services like that are. I could see, say, going with the less reliable service for 10 months and, as I approach crunch time, telling them "reliability is key" and paying the extra money for those couple months.

    2. Re:Wait, what? by Anonymous Coward · · Score: 1

      Again, a particular service is not mission critical, so we don't need to spend the money to make it so. Things like test servers and the like could fall into this category. After all, you really don't need 99.999997% uptime for this.

      At least until the power goes out at the data center and you've got a room full of testers and developers sitting around waiting for it to come back on and there's a deadline looming. Then you don't look so smart for saving an extra few bucks a month.

      I wonder how dynamic the services like that are. I could see, say, going with the less reliable service for 10 months and, as I approach crunch time, telling them "reliability is key" and paying the extra money for those couple months.

      It's a bit more than that. First of all, back in the old days when you had your dev and test using on-site equipment, you took those outages in stride and didn't pay for redundancy. Has there been a change in mindset? If so, why? This article suggests that some companies are still willing to give up some redundancy, so apparently the mindset hasn't changed everywhere.

      Second, when it comes to dev and test, how much redundancy do you really need? You've got your source code in a git repo, right? If you've got 10 developers then you have 10 redundant copies in addition to the main hosted copy. Do you really need to pay for 6 cloud copies in 3 data centers for the main hosted copy? Really. Do you need to pay extra money for that? Are your test cases similarly stored in a git repo? Perhaps you don't need to keep redundant copies of them, either.

    3. Re: Wait, what? by Anonymous Coward · · Score: 0

      You don't do much enterprise development...

    4. Re:Wait, what? by ottothecow · · Score: 1
      I see this being used for more distributed tasks and for tasks not tied to the core business.

      I can't quite envision exactly why you would need this, but lets say you have a compute cluster spread out across many locations. Additionally assume that you are using this for something internally on-demand rather than automated or in response to customer/user interaction. Things you might use AWS for like ad-hoc queries and machine learning exercises being run by your analytics team instead of whatever it is your company actually does for money..

      If some of your systems are down, it doesn't have a real impact on the bottom line. Your data scientists might be delayed (or temporarily halted), but not your customer facing systems. Perhaps you can even mix and match within the same datacenter. Storage and processing for your core business go in the $$$ high-redundancy racks. Toys for the PhDs go in the cheaper low redundancy racks.

      --
      Bottles.
    5. Re:Wait, what? by grahamsz · · Score: 1

      We're slowly working towards building out a genetic algorithm to plan factory resources. It works on some small tasks but scaling it up to plan our whole operation is going to require more compute power than a single server can provide and is also well suited to being processed in a distributed environment.

      The nature of the task is that there's no "right" answer so I can see us doing something where we have 10 servers that run for 4 hours at night making a plan for the next few days, then after 4 hrs is over we take the best candidate and run with it. If one of those servers goes offline at some point, the chances are good that we'll still find the same solution and even if we don't it'll probably only be slightly-more-sub-optimal

    6. Re:Wait, what? by tlhIngan · · Score: 3, Insightful

      I'm reading this as.. "Well, we need to have redundancy, and we're already ponying up this much money, but how can we spend less and still say we're "redundant?" I'm not faulting the datacenters for offering such a service, but the customers should really have a hard look in the mirror.

      If you're using ONE datacenter, then yes, you need to take a good hard look at trying to save a few bucks.

      But if you've got datacenters geographically spread out, or even have multiple data centers, do you need 99.999% uptime? If you implement your switching and load balancing correctly, then the failure of one datacenter means you shift to another one and go on. Maybe a bit of extra latency, but if you're geographically distributed, then it really doesn't make sense.

      Sure, maybe one of your datacenters, your primary one is 99.999% reliable. But your auxiliary ones that serve to provide faster service to local clients, doesn't have to be - at the worst, they then have to wait more milliseconds to hit your primary.

      There's plenty of opportunity for non-highly-redundant services as well - perhaps you have a personal website - save a couple of bucks a month to host it on a less reliable hosting service, because you don't necessarily need it up 24/7.

      So it's good for operations that are already redundant and operations that can tolerate downtime.

      Maybe you have a data center and use Amazon AWS to handle overload. Well, you can downgrade the reliability of the data center knowing you can spin up more AWS instances if the primary goes down. You're already paying for both services, and they can backup the other.

      It's basically RAID - redundant array of independent datacenters.

    7. Re:Wait, what? by BitZtream · · Score: 1

      ... they're talking about saving a few bucks by not having redundant power supplies, not because a hard disk isn't redundant.

      You're devs aren't doing shit with their git repo if your CI machine and environment are down because the power went out, and that killed interop and your big data clones of the production machines you use for integration testing are silent.

      You don't need 3 copies of them cause you can rebuild if need be, but you still need the thing to work. The likelihood of a power failure is considerably larger than that of a hard disk failure. You're going to replace the test server to get a faster one before the hard disk fails or some other component that was never redundant anyway.

      My current test data set is almost 4TB, and its not even close to a 'large' one here ... and you want me to put that in my git repo? Are you that stupid?

      As was said elsewhere ... you don't do much large size development.

      --
      Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
    8. Re:Wait, what? by KGIII · · Score: 1

      In this day and age, how hard is it to spin up a new VM instance "in the cloud" and just run with it as a functional equivalent of a different network share?

      --
      "So long and thanks for all the fish."
    9. Re:Wait, what? by Anonymous Coward · · Score: 0

      Err... Sorry - forgot to add, that's a serious question. I do not know the answer.

    10. Re:Wait, what? by rudy_wayne · · Score: 1

      The real problem is illustrated in the last paragraph:

      "Even when they say they're OK with lower reliability, they still want uptime,"

      In other words, no matter how many times a customer says they will accept lower reliability in exchange for a lower price, the first time things go down, they are going to be screaming at you for not keeping things running perfectly all the time.

    11. Re:Wait, what? by Anonymous Coward · · Score: 0

      really really hard. first get your management to sign off putting data in the cloud. then try to spend a few weeks uploading a couple of TB. then try and get the cloud instance to say up without breaking the bank.

    12. Re:Wait, what? by mlts · · Score: 1

      I can see having a redundant data center at a lower uptime rate, positioned for a few tasks:

      1: For a smaller company, it can be "good enough" as a place to stash machines.

      2: It could be useful for a disaster recovery center, especially if it had compute nodes ready to go, a SAN that took async replications from the main site, and other items. This helps provide geographic redundancy, although the diminished uptime might be an issue if the site becomes the primary.

      3: This might be ideal for relative low priority tasks like archiving. Replicate a SAN, have a tape silo pull data too keep off with NDMP, and this would fulfill the need to keep records offsite.

      4: Do like Facebook, and put the redundancy in the backup application. If a data center goes down, the backend application redirects traffic to another one until it is back up. By having the redundancy handled in the backend application and database, it can mean that hardware on the datacenter and individual machine level can be less reliable and cheaper.

    13. Re:Wait, what? by KGIII · · Score: 1

      You can't just have one sitting idle at AWS waiting for you or have some sort of CDN-esque creature where you just failover to a new DC where you've already got everything setup and spin up a VM as you need with data already synced from a main image somewhere? This seems like it'd be pretty easy to have ready and waiting and you should probably be relying on multiple data centers now if you're using the network to do your computing. Maybe I'm missing something?

      --
      "So long and thanks for all the fish."
    14. Re: Wait, what? by Anonymous Coward · · Score: 0

      Of course there's been a change in mindset. It used to be that tech people ran tech stuff. Now we have idiot business managers wanting everything in 'the cloud' because reasons. Then they freak out when they see what it really costs because the in flight magazines in first class say that cloud stuff is super cheap, so you get this.

    15. Re: Wait, what? by guruevi · · Score: 1

      I build systems that reside in data closets and centers. With modern clustering and virtualization systems you don't need to worry too much about local redundancy. Local redundancy (dual power, network, storage, everything) is expensive for the off chance something might happen.

      Then you still need a backup elsewhere for the time actual physics intervenes (a lightning bolt or other natural disaster to the building). And usually double everything doesn't help much with user errors, load issues, DDoS, in fact setting up redundancy incorrectly or across systems that aren't built for it is often the cause of the issue (packets out of order due to multipathing).

      So setting up redundancy by hosting 3 or 4 cheap units across different cheap data centers gives you more global resiliency than paying the same or more to 1 or 2 ultra iso certified bunkers.

      Sure if you actually need local resilience (eg local lan file server) you're still wanting dual power supplies and bonded networks to dual sas controllers. But those things are slowly going away (for now) to make place for slightly more trendy (and more expensive) cloud services.

      --
      Custom electronics and digital signage for your business: www.evcircuits.com
    16. Re:Wait, what? by Goetterdaemmerung · · Score: 1

      That sounds like a lot of footwork and configuration and synchronization projects required up-front - above and beyond the cost savings (meaning getting rid of your IT staff) of going to a cloud service in the first place. Hardly automatic "ready and waiting".

    17. Re:Wait, what? by KGIII · · Score: 1

      LOL I think I get it now. So, instead of this being something that, you know, doesn't really much matter it's likely to be a bundle of crap because people are unwilling to pay? I mean, if I were already hosting in a variety of data centers (which I would be, if I were to move stuff "to the cloud") then I'd not care if one fell over - the rest can pick up the slack and that was kind of the point of having multiples.

      I am really glad that I'm retired. It sometimes, literally (true sense of the word), makes me cringe when I read about some of the stuff that people go through.

      --
      "So long and thanks for all the fish."
  5. Bitcoin mining? by PCM2 · · Score: 1

    Bitcoin mining is still an in-demand data center application?

    Makes you wonder ... just how much fossil fuels will have been burned by the time we've "created" all of the Bitcoin there is to make?

    --
    Breakfast served all day!
    1. Re:Bitcoin mining? by ls671 · · Score: 2

      My bitcoin mining rig is on a satellite orbiting mercury and is powered exclusively by the sun. I am currently the top world wide (galaxy wide?) producer of bitcoins.

      --
      Everything I write is lies, read between the lines.
    2. Re:Bitcoin mining? by Chrisq · · Score: 1

      My bitcoin mining rig is on a satellite orbiting mercury and is powered exclusively by the sun. I am currently the top world wide (galaxy wide?) producer of bitcoins.

      I'm planning a dyson sphere and diverting all the energy to mining bitcoins. That should give me enough money to invest in a Kardashev type III level bit-mining operation. It might result in the unfortunate extinction of a few planetary systems, but this is capitalism.

  6. My data center.. by Anonymous Coward · · Score: 0

    is ahead of the curve. They adopted that policy years ago. We've had three power outages so far this year.

  7. Maturing service tends toward commoditization. by Stolpskott · · Score: 1

    As with a lot of other services (in fact, all other services that I can think of) that reach a certain level of maturity and ubiquity in the market place, one of two things seem to happen. Large-scale consolidation reducing the number of competitors until a small number of actors, or a single monolithic entity, remain; or reduced perceived value of aspects of the service leading to a bare-bones offering because customers decide they are less willing to pay for services they are not going to use very often (but when they need them and they are not there... oh boy, will they scream and harass the provider who told them they were sacrificing redundancy and potential uptime for lower costs).

    1. Re:Maturing service tends toward commoditization. by ls671 · · Score: 1

      You mean, like the fact that we now have to fill up our cars by ourselves nowadays at the gas station? Next, we will go to the data center by ourselves to turn the power back on...

      --
      Everything I write is lies, read between the lines.
    2. Re:Maturing service tends toward commoditization. by KGIII · · Score: 1

      You have obviously never been to New Jersey or Oregon. Or at least not gone to a gas station in either of those two states.

      --
      "So long and thanks for all the fish."
    3. Re:Maturing service tends toward commoditization. by Stolpskott · · Score: 1

      You mean, like the fact that we now have to fill up our cars by ourselves nowadays at the gas station? Next, we will go to the data center by ourselves to turn the power back on...

      To a large extent, yes. Although the example I initially had in mind was the airline industry - flying in the 1950's was a little bit dangerous, but also very glamorous. As it grew and became more of a mass-market thing through the 70's and 80's, competition on price became the norm, while it had previously been competition based on added value services and the prestige of travel. The current state, with low-cost carriers and "cattle class" in every sense of the phrase, is not where we are with data centers yet, but we will get there. In data center terms, that probably would be not much more than off-site hosting, and if you want extras like UPS, power/network/server failover, data backup or on-the-spot warm body technicians with the skill to do more than press a button, you will pay for it.
      As the service itself becomes less valued, price becomes very important. Price is always important to PHBs and other MBA idiots, but at least with cloud services at the moment the more technically-minded can point to the hype and caché of the cloud as a justification of the cost.

    4. Re:Maturing service tends toward commoditization. by Stolpskott · · Score: 1

      You have obviously never been to New Jersey or Oregon. Or at least not gone to a gas station in either of those two states.

      I went to New Jersey once... it smelled funny. ok, I lied and spread terribly bad geographical stereotypes. Never been to NJ other than as a layover stop at Newark when flying between Europe and San Francisco.
      If NJ and Oregon are still using Gas Station pump attendants, I suspect that is more about padding employment figures than service levels. Because if an attendant were adding value, they would be common in other states too.
      Hmm, just heard a whooshing sound. Was that the point of the comment, flying over my head? :P

    5. Re:Maturing service tends toward commoditization. by KGIII · · Score: 1

      It's the law in those two states. I have no idea why it is the law in Oregon but I suspect it's mob-related in NJ.

      --
      "So long and thanks for all the fish."
    6. Re:Maturing service tends toward commoditization. by Anonymous Coward · · Score: 1

      That's cachet, you imbecile. Unless you mean it's hidden.

  8. Cost? by BitZtream · · Score: 1

    Because a few generators, transfer switches and UPSes are such a large portion of data center costs ... Its not like they are outweighed by just a single months power bill or anything in most cases.

    --
    Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
  9. I can see a real business need for this by Krishnoid · · Score: 1

    Maybe it's a new business venture from the same guys who run Jiffy Express?

  10. advertising vs reality by Gravis+Zero · · Score: 2

    why would you want to pay for 99.99% uptime when it's rarely provided?

    --
    Anons need not reply. Questions end with a question mark.
    1. Re:advertising vs reality by Anonymous Coward · · Score: 0

      [lionel hutz voice]
      They made a mistake at the printers, let me fix that for you.

      9.999% uptime guaranteed!

  11. Re:"OK with lower reliability,they still want upti by acoustix · · Score: 3, Insightful

    Why? Failover keeps high uptime even if you have less reliable hardware.

    Unless the unreliable hardware is your power source.

    --
    "A plan fiendishly clever in its intricacies"- Homer Simpson
  12. Depends by Anonymous Coward · · Score: 1

    Depends on the service. Many things can easily be distributed over a few datacenters. 10 cheap servers with so-so uptime may be better than one with a very high uptime from a cost point of view.

  13. Windows proves the demand by raymorris · · Score: 1

    Some people still run Windows on -servers-. This proves that reliability isn't always the most important thing.

    1. Re:Windows proves the demand by Anonymous Coward · · Score: 0

      Some people still run Windows on -servers-. This proves that reliability isn't always the most important thing.

      How would you know?

  14. Increase infrastructure costs 200%-400% by raymorris · · Score: 2

    The cost is two to four times higher. The basic idea is you can choose:

    ___Non-redundant A-only power____
    1 router (1 amp) + 1 switch (1 amp) = 2 amps.
    You need one power plant capable of providing 2 amps.

    ___Redundant with A/B power___
    2 routers (2 amps) + 2 switches (2 amps) = 4 amps
    You need two sets of power, each capable of providing the 4 amps, so 8 amps total.

    Note you need not twice as much power capacity, but FOUR TIMES as much in order to have full A/B redundancy. Plus the more complex (expensive) design with more transfer switches, etc.

    Twice as many PDUs feeding twice as many routers and twice as many switches take up twice as many racks, which means twice as many square feet, and almost twice as much power and cooling cost.

    1. Re:Increase infrastructure costs 200%-400% by Anonymous Coward · · Score: 0

      Capacity != usage. Yes you need 4 times capacity, but the actual power usage shouldn't be that much more. If a server is going to draw 600 watts on one PSU, with two it is still going to need about 600 watts.
      Yeah there will be some losses, but not 4 times. So the power bill itself might be 1.1 times higher, not 4 times higher.

      Cooling usage shouldn't change much either. UPS systems will be at least double the cost for redundancy sake though.

  15. Really? by Anonymous Coward · · Score: 0

    That'll end in tears.

  16. Cheaper does not have to mean less reliable by Anonymous Coward · · Score: 0

    The space provider should provide AC that is guaranteed to be generally up, but may have limited gaps while their gensets come on-line.

    If the gaps are predictable with N+1 gensets, then that should provide both cheap and reliable space.

    Riding through the gaps is a batteries in my-space issue.

  17. Re:"OK with lower reliability,they still want upti by Anonymous Coward · · Score: 0

    Then power it via the cum dribbles from timothy's micropeen.

  18. Cloud by Anonymous Coward · · Score: 0

    Maybe I'm just looking at it wrong, but wouldn't this fit the bill for cloud setups ?

    Have X lower cost data centers spread about the regional area, mirror the data over, provide multiple paths to get to it and voila.

    Though I'm not sure that X unprotected cloud sites would cost less than 1-2 properly setup redundant sites.

  19. Actually they are by dbIII · · Score: 1

    I looked into it a while ago when I had unreliable power and outages lasting more than an hour so well beyond UPS capacity. Once you get beyond just having to fill in for a few minutes the generators get expensive, and then you need a plant mechanic to keep the generators in working order, fuel storage, a test regime heaps of electrical work etc etc. A purpose built large scale data centre can be expected to have such things and absorb the cost but adding it in after the fact with something that is not huge, especially on a site without room to put those generators and fuel storage outside, is not a trivial thing.

    Ironically now that the place I work for actually has a plant mechanic, electricians and the space for generators plus storage the power supply is stable enough that I no longer need them.

    I comes down to the cost of downtime versus all that messing about - in my case a few days downtime of the site can be coped with and absorbed into moving schedules. There really are not that many businesses that are 24/7/365 no matter how important they think they are. A few days out due to flood or hurricane/cyclone will confirm that for most people.

    1. Re:Actually they are by mlts · · Score: 1

      Don't forget the transfer switches. If those hose up, the generator can start on time to pick up the load... but if the ATS doesn't hand those kilo-amps over to the genset PDQ, it can cause an outage, as the UPS thinks the load has moved, so goes back into bypass mode.

      Of course, transfer switches can fail so it may not even shunt the load over, come time it is needed. Learned that the hard way, and you can't even get near them unless you are wearing full arc-flash gear.

      Generators are not cheap. They need oil changes, the diesel fuel sits a long time, so one has to add both anti-gel as well as a biocide. They also need run weekly to ensure that they will actually work when they are needed.

      On the other hand, I think there may be a market for data centers that are not top tier. For example, there is a lot of interest in people running their own Internet infrastructure on machines they physically control, especially with compromises a common item with E-mail providers. So, a SMB or even a SOHO renting out a half rack to place a 10gigE NAS/SAN (DS2015xs for about $1400, diskless), a few 1U PCs as compute nodes, a firewall appliance, and a router could do a decent job at receiving E-mail securely on a fast connection.

      In general bad guys are not going to spend much time attacking some small coloc appliance as opposed to something that will give a juicy payoff.

      Heck, if one wants to do it on the cheap, a Synology DS215j can do E-mail, seedbox, and VPN services for about $200 + two mirrored internal hard drives. For additional protection, a small firewall appliance can be placed in as well. For this use, a network outage for a few hours a year wouldn't be a deal breaker. If one wanted to pack their own parachute, an APC UPS is a few C-notes and will ensure a proper shutdown. For further control, one can add a remote console and power box.

      I'm actually surprised there are not more "sub-prime" data centers out there. I'm sure there is money to be made by taking a vacant building, adding a CRAC, UPS, PDU or two, a backhaul, and then offering locking server cabinets. This way, someone who wants to, can pack their own parachute. With virtualization so relatively cheap, including virtual firewalling, one can do a lot with a third rack of cabinet space.

    2. Re:Actually they are by Anonymous Coward · · Score: 0

      Test that theory by doing a "DR Test." Turn everything off for two days and see what happens.

    3. Re:Actually they are by dbIII · · Score: 1

      Test that theory by doing a "DR Test." Turn everything off for two days and see what happens.

      What would happen is the bill for fuel would go through the roof and a lot of people would complain about that noise - and that's if everything works perfectly. Running for a few hours is a different situation.

      On the point of tests there's a 20MW generator I saw (old jet engine) which was tested every month for about 20 years without many problems. On the one day in it's life that it was needed (to get coal conveyers and sootblowers running on a small city based power station unit when the local grid had gone down) it didn't work. You need two of everything. Fortunately stuff in the kW range is nowhere near expensive to duplicate (and about 100 times less noisy!).

  20. Disaster Recovery by mcrbids · · Score: 1

    We spend big bucks at a tier 1 data center to host our data. Our application cluster is fully redundant, and we serve large amounts of high-value data. (think: business intelligence and workflow information, not video streams)

    We have a DR cluster, a back-stop for when all else has failed. Although it is a redundant copy of our production cluster, it itself is, by design, non-redundant. Where our production cluster has at least two physical machines (and often more) providing any specific service, the DR cluster has just one.

    It's there as insurance against the rare, once-in-a-lifetime event that has been known to shutter companies. I've experienced one such event when the data center I was hosting at went dark after they went insolvent - it took weeks to get all services resolved, because, while I had backups, they were onsite. (doh!)

    While I've never since had backups that weren't automatic, daily, and off-site, I see no reason to demand the same power redundancy for the DR cluster that I do at the primary data center. Cost is more of a factor.

    --
    I have no problem with your religion until you decide it's reason to deprive others of the truth.
  21. Re:"OK with lower reliability,they still want upti by Firethorn · · Score: 1

    Unless the unreliable hardware is your power source.

    That's why you put your failovers in different data centers. If you spread the load over 5 different data centers, with 20% extra capacity, losing one isn't a big deal.

    Especially if you go with some of the more modern plans that let you scale within moments.

    --
    I don't read AC A human right
  22. Still better than the mop closet? by swb · · Score: 1

    This seems like the kind of thing that would benefit some SMBs I've worked with.

    I've worked with several that have awkwardly architected homegrown applications or very low-quality vertical market applications that they're highly dependent on. The net result is applications which don't translate well to cloud-hosted scenarios for various reasons, or at least not at cost levels that make any sense.

    Colocation would work, but datacenters' relentless focus on being super duper redundant makes them too expensive, so the clients are stuck hosting their own systems on premise, often in facilities not much better than the proverbial mop closet.

    Low cost colocation facilities that might not fit some kind of top-tier datacenter definition may not be a great choice for others, but I can see these kinds of clients going for them. It would be a reliability improvement over what they do now and probably at a cost they would afford.

  23. Re:"OK with lower reliability,they still want upti by Anonymous Coward · · Score: 0

    Unless the unreliable hardware is your power source.

    That's why you put your failovers in different data centers. If you spread the load over 5 different data centers, with 20% extra capacity, losing one isn't a big deal.

    Especially if you go with some of the more modern plans that let you scale within moments.

    But then you're paying for network connectivity between the sites which negates any savings.