> Colocated systems tend to work very well at first when the original engineers who set it up are all still at the company and it hasn't run long enough to start encountering rare failure modes. They quickly become a nightmare when your engineering staff turns over multiple times and nobody can remember who knows how to do what on the colocated system or if the documentation is up to date or not.

Everything above really sounds like it's just regurgitating AWS sales person talking points.

Sounds like a systemic management / CTO-level problem to me if a company isn't willing to put in place the hiring practices and compensation, documentation systems and operational procedures to deal with that sort of concern.

If your core engineering staff is turning over multiple times for arbitrary reasons you have other problems to deal with.

> Engineers can't set up, maintain, and do on-call for the colocated setup without subtracting from their primary working hours.

If a company can't hire datacenter techs to install hardware, cables, and swap hardware as smart remote hands, maintaining as little as a couple of 45RU cabinets of gear, you also have other management/systemic problems to deal with. I'm looking at this from the point of view of a facilities based bare metal ISP that owns/runs all of its own hardware, and can tell you it's not rocket science.

> If you core engineering staff is turning over multiple times for arbitrary reasons you have other problems to deal with.

People leave for all sorts of reasons: Moving for family reasons, becoming stay-at-home parents, moving for a spouse's job, retiring, starting their own companies, or even just getting bored and wanting to do something different. Or it could be as simple as getting promoted to a different role.

It's unrealistic to make engineering decisions with the assumption that the same engineers will be around and stuck on the same project forever.

Like the OP said: Every hour they have to spend working on the colocation setup is an hour they aren't spending on your company's competitive advantage, so you have to hire more engineers (and more managers) to compensate.

> If a company can't hire datacenter techs...

How many techs do you think you need for reasonable on-call coverage? 3? 6? Add a manager in the mix because you need someone to manage them.

The costs add up quickly.

It's weird to see people championing colocation as a cost saver and then pivoting to arguments that you just need to hire more engineers and techs and manage them.

Employees are expensive. One of the primary benefits of cloud is that you don't have to hire and manage all of these employees to do all of these things at the colo.

My team of three looks after hundreds of bits of diverse kit in dozens of locations across the world.

I can’t remember the last time I took a call outside of office hours, and even in hours it’s very rare. There’s enough resilience built in that any issues can wait until morning

The last major outage was in 2017, before we had a third member of the team. I was on the other side of the world installing a new system, the other was on leave. We had a network issue, OSPF melted and knocked out some services, we were down for about half an hour as I rebooted the core switch pair remotely.

(We’ve since redesigned so that doesn’t happen)

We get paid nowhere near six figures either.

Sure you can be ridiculous, I remember one team I worked on that employed a full time unix contractor (on 3 times the staff wage) to look after 6 servers and deploy a tar ball every few months. I replaced him with a small shell script. Another was a DBA looking after a small oracle database (oracle - which of course is that generations “just use amazon”)

I think a number of people who are taking the position of "but it's so HARD, and so EXPENSIVE!" to own and run bare metal network infrastructure may not have ever seen a proper OOB management setup, with dedicated OOB network, serial consoles on stuff, management routers and switch at site, things like cradlepoint LTE radios stuck to the top of colocation cages, etc.

And then basic other things like having remote smart hands ready to go, and common failure items like fans, power supplies, fan trays, hard drives pre-positioned and ready to swap in. With MOPs for swapping them. Stocks of basic things like fiber patch cables, commonly used transceivers, copper patch cables, stored in every cage.

> I think a number of people who are taking the position of "but it's so HARD, and so EXPENSIVE!" to own and run bare metal network infrastructure may not have ever seen a proper OOB management setup, with dedicated OOB network, serial consoles on stuff, management routers and switch at site, things like cradlepoint LTE radios stuck to the top of colocation cages, etc.

Or we have seen all of this and that's exactly why we don't want it.

Building a company is hard enough. Adding the overhead of developing, maintaining, recruiting for, and staffing our own datacenter is madness when I can click a few buttons and get the same thing from a cloud provider without hiring anyone extra to manage the datacenter.

No one is denying that a proper data center management system can exist. We all know it can exist.

The issue is that it's a huge distraction with a lot of potential pitfalls. Your network infrastructure with Cradlepoint LTE radios in the colocation cages sounds great after it works, gets set up, stays documented, and all the bugs have been ironed out. But that's a lot of hidden work that could have been allocated to launching the product faster.

I think the difference in point of view here, is that from my own perspective, owning and running the bare metal things is a basic core competency of being an ISP. Which is what I do for a living. The infrastructure I've described up thread is the product.

If the use case is somebody developing a software product that is a totally other scenario.

For an ISP, you are probably correct.

> Building a company is hard enough. Adding the overhead of developing, maintaining, recruiting for, and staffing our own datacenter is madness when I can click a few buttons and get the same thing from a cloud provider without hiring anyone extra to manage the datacenter.

“Building a company is hard enough, adding the overhead of actually building a company is madness”

> But that's a lot of hidden work that could have been allocated to launching the product faster.

The topic of this thread isn't about a brand new start-up with no resources trying to build their product as much as possible, it's about a company that spends millions in cloud invoices.

Building a company using AWS, totally legit. Scaling this usage up to millions of dollars because you don't want to manage the hassle, fair enough it's your money, I don't mind if all your profit goes to Amazon really…

^^^ 1000x

One big pain that no one seems to mention are the mundane details that come with running your own DC. Even in our fairly small operation we had half of a person dedicated to maintaining the warranties on the hardware, sourcing replacement hard drives for 10yo servers, disposing of retired hardware, purchasing new hardware, etc.

These things take a huge amount of focus and don't contribute to your product at all. The "cloud" has removed all of this busywork and I wouldn't go back to the old way for almost any amount of money.

Been there, done that. No thanks. Every place that has their own hardware also has a huge bureaucratic process to get more hardware for your project. Not to mention almost always the software stack is old as dirt. For example mongo might be two or three major versions behind current… and IT wants nothing to do with supporting the new version.

People move to the cloud to escape their company’s IT process… there might be some unicorn company out there that does infrastructure “right” but I’ve yet to work there.

^^ This 1000x.

Humans are incredibly expensive and notoriously unreliable when compared against “machines”; or in this case an API.

It’s usually worth paying 2-3x the cost to have someone else manage something for you with a given SLA, because that’s what it will end up being when you decide to bring it in house when you take into account the time and effort needed as well.

A “good” & “reliable” Systems Engineering team, that can offer 24/7 support will take around a year to hire and setup, and they need roughly the same amount of time to transition you off AWS in to your system. They probably need closer to 3-5yrs to give the same level of documentation, API’s, tooling, processes, UI’s and training that AWS already provides.

Let’s call it 5 years to get to the level of AWS when you started the transition.

A decent team of 5-7, including engineers + PO/PM + UX and so forth, is at least $1.5M/yr. That’s $7.5M over 5 years, not including your new hardware and networking costs. Let’s call it $10M. You’re also 5 years behind AWS now, and over that transition you’re still paying AWS, and your development speed has halved as you wait for your new team to build or transition infrastructure.

You can trade cost and quality for speed and have everything ready in 2-3 years by setting up a few teams. Add HR support, more contractors etc etc. you’re looking at a $10M+ outlay again, regardless.

Or you can keep paying AWS $5M/yr, renegotiate fees often and literally not worry about that headache and focus on your product.

You act like AWS doesn't require you to have a team, or carefully transition infrastructure. Because of that your cost estimate is much higher than the couple additional people you should actually need.

> They probably need closer to 3-5yrs to give the same level of documentation, API’s, tooling, processes, UI’s and training that AWS already provides.

You don't need to build an internal AWS to manage your own servers.

You are an ISP, and managing that hardware is your core competency. For every other CTO, saving money by moving to on-prem is picking up pennies in front of steamrollers. Just because you spend $3 million/year on AWS doesn't mean that same organization can turn around can hire 10 sysadmins and do everything themselves; anyone who thinks they can simply execute well just because they have a big checkbook is in for a rude awakening.

For a growing company I would always weigh the organizational overhead of moving on-prem to the actual cloud costs. If your goal is in the next year to grow revenue from 50MM to 100MM, then a company wide engineering effort to move to bespoke platform to save 5-10MM just isn't a good use of time (keep in mind you are trying to hire and release new features).

It's not that it's impossible; it's that trying to both scale up your business and provide infrastructure to yourself is just unnecessarily increasing the difficulty on your businesses execution.

I worked at a company that migrated a 100 PB Hadoop cluster to GCP for assorted reasons despite many years of success with colocation. I wasn't involved in any of this, but the team's decision process makes sense. You can read through their decision making in these blog posts:

* https://liveramp.com/developers/blog/google-cloud-platform-g... * https://liveramp.com/developers/blog/migrating-a-big-data-en...

One big point was challenges of maintaining multiple colocation sites, with cross replication, for disaster recovery. Since Hadoop triple replicates all data within one DC, this requires 6 times the disk storage capacity of data size for dual DCs. In contrast, cloud object storage pricing includes replication within a region with very high availability such that storing once in cloud storage may be acceptable. Further, you also need double the compute, with one of the DCs always standing by should the other fail.

HDFS supports RS/XOR erasure coding which gives you same fault tolerance guarantees as 3x at much lower replication factor. This is essentially the same method aws/gcp use under the hood - there’s no magic involved here

Can I use this over NFS or samba or is it just for Java and Hadoop?

Yes you can* for new projects I would go with ceph+nfsv4

*) https://hadoop.apache.org/docs/r2.8.0/hadoop-project-dist/ha...

ceph+nfs was actually what i was going to do.

Probably some learning pains but at least i don't have to "lose" half my storage because the sizes aren't paired with anything.

If I have to pay the same amount of money and I can choose to deal with people or deal with a decent sized company (and leave them to deal with their people), I always choose the later.

Sorry, that's bullshit.

It all depends on the size of the investment and how you need to run it. I built a "new" environment on a company premises due to some compliance requirements that would be cost-prohibitive in AWS or GCP. The gear was procured through a leasing vehicle, and the hardware vendor had an SLA for delivering compute and storage. HPE happened to win the bid.

There is very little difference operationally. From a costing perspective, it's about 40% less than an AWS solution. But in fairness, the customer had an existing investment in a facility - you'd reduce the savings if you had to lease appropriate space in a colo. There are some differences in terms of headcount, but those staff aren't in NYC/SFO/BOS, so they are very cheap -- senior level engineers for $80-120k, fully loaded.

Startups do stupid shit like buy supermicro computers and cobbling together hardware that gets them into trouble when the mad scientist moves on to a new gig. Makes sense when you're drowning in VC money and need to hire people, but doesn't make sense in most other ways. You avoid that by doing competitive procurements and paying marginally more for HPE/Dell/Lenovo/etc.

> cobbling together hardware that gets them into trouble when the mad scientist moves on to a new gig.

If you think that standards based x86-64 hardware running Linux and ZFS, or FreeBSD and ZFS is something that is super unreliable and requires a "mad scientist", then yes, you are definitely in HPE and Dell's target market.

I laughed at the “mad scientist” comment because every startup I’ve worked for has had a “mad scientist”. They are always very opinionated and have a lot of political capital because of seniority. The weird concoctions they create… the minute they leave all the remaining engineers immediately replace most of it with off the shelf stuff.

Home built web frameworks (which apparently aren’t “bloated” and “slow”), piles of bash scripts because they never heard of Salt (or whatever is the latest config management tool)…

Almost always they think they are “saving money” by doing what they do, rarely do they ever consider the opportunity costs to rolling the entire software stack from the hardware to web stack on their own.

Good times.

There is a survivorship bias at play here. You experienced the startups that survived long enough to need to evolve their tech stack, and presumably the 'mad scientist' tech stack had some part to play in that.

> Home built web frameworks (which apparently aren’t “bloated” and “slow”)

Well, let me show you something: https://code.djangoproject.com/ticket/31624

This is a performance regression of Django's ORM for deleting rows from a table, a query that should be about as simple as it gets:

    delete from tbl;

And yet it's orders of magnitude slower because it somehow generates a bloated query. So yeah, let me tell you, the frameworks that people are using off the shelf–there's a pretty good chance that they're 'bloated' and 'slow'.

> piles of bash scripts because they never heard of Salt (or whatever is the latest config management tool)…

Well, that's kind of the point, isn't it? If you're trying to get a project off the ground as quickly as possible, you kinda don't care about 'whatever is the latest config management tool', you will use what is already in your toolbox that will get the job done.

the op was talking about hardware, I think. but you are spot-on on the mad scientist. we are just in the process to de-clutter all the non standard, hand made, highly customized, never documented, stuff produced buba coworker that, unfortunately, passed away.

btw, we also wrote a HA cluster software for sun solaris in year 2000...

I run 10 years old HP servers, something like DL580G5, with care-packs (extended, paid warranty). We needed to flash firmware, 2 motherboards broke and they sent spare parts to replace. Probably with less enterprise-y server firms it may be difficult to find spare parts after 10 years..

> Colocated systems tend to work very well at first when the original engineers who set it up are all still at the company and it hasn't run long enough to start encountering rare failure modes. They quickly become a nightmare when your engineering staff turns over multiple times and nobody can remember who knows how to do what on the colocated system or if the documentation is up to date or not.

And AWS systems do not have to face the same problem? Is it easier for a new staff to come in and modify a millions worth of AWS system than a colo system?

This all sounds like excuses. Insert that two dog meme, one builds a freaking datacenter using commodity hardware in a barn and the other uses AWS and complains about lock-in and expenses.

As an example, imagine if the founders and engineers of Backblaze thought like that.