By Sarah M. McBrideThe answer, according to a recent survey of over 1,400 computer systems architecture professionals, depends on the kind of computer system that the designer intends to build.
And while it may seem obvious that the most efficient systems design would be based on the most optimal hardware design, there’s plenty of room for creativity when it comes to building systems.
The survey found that nearly half of the experts surveyed believed that the best systems design could be achieved by building systems that were simpler, faster, and cheaper than the average consumer’s.
“The key thing to remember when thinking about systems architecture is that the architecture that the system designer wants to build is going to have to scale well,” said Brian Schiller, an architect at the architecture firm Arup who participated in the survey.
“It has to be fast.
It has to have a good cache for the data.
It needs to be cheap.
The survey found designers were more likely to focus on cost than on speed. “
I’m sure there are many systems that would be a good choice for the consumer because they are simple, cheap, and fast.”
The survey found designers were more likely to focus on cost than on speed.
For instance, nearly half (49%) of the respondents said they were willing to pay up to $50,000 to build a system that would perform as well as an average consumer computer system, compared to only 13% who said they would pay less than $50.
“If I want to build an entire new business that’s running in a high-volume environment, and I want it to be more efficient, I’m more likely than not to have more than a couple of hundred servers and I don’t want to have thousands,” said one of the survey participants, who wished to remain anonymous because they did not want to reveal their true identity.
“The system is going the same way in the consumer market.
If you want to make it cheap, you’re going to need a lot of data centers, lots of storage, and lots of RAM.”
The second survey, conducted by the architecture practice Wargaming, also found that the majority of respondents believed that systems architecture was a good fit for the most expensive and complex consumer applications.
“I don’t think you should be doing anything like the consumer applications,” said Daniel K. Ziemba, CEO of Wargames, the company that designed the Battletech universe in Star Wars: Battlefront II.
“If you’re doing a high performance game, you want an architecture that can support that.
If your game is something that’s going to run in the cloud, you probably don’t need a system architecture for that.
I think the consumer is a different kind of market.”
Some of the questions in the second survey were more subjective than others.
A few respondents thought it was important to be able to build systems that could be used by multiple companies and even to create entirely new ones.
“What do you want the system to do?
What do you need the system for?” asked one respondent, who wishes to remain unnamed for security reasons.
“You want a system for the entire world to use, not just the people that need the game.
That’s what I want.
The consumer is going different things than the consumer.”
For instance, one respondent said he wanted a system to be used as a gateway to a larger number of devices for a single user.
“You want the systems to be simple, efficient, and secure,” said another.
“There’s a lot that can be done to make that happen, and if the consumer wants that, then that’s what we need.”
A few respondents also thought it important to make sure their system was simple enough that a user could create a new one for himself.
“This is going in to a world of data, and it’s going into a world where there’s going be billions of data points that are coming into a system and there’s not going to be a system you can build for that,” said an employee who wishes not to be named for privacy reasons.
“When I was designing the Star Wars universe, I wanted to build this very simple system,” said the employee, who wanted to remain unidentified because he did not wish to reveal his true identity in case he was fired.
“All the systems that we designed had to be very easy to build, and simple enough for a consumer to build for themselves.
The system is built for the average user, and they can build a new system for themselves if they want.”
Some respondents were concerned about the cost of their system designs, but not necessarily the amount of money they wanted to spend.
“When I look at this system, I think of it as a system, but I don-I don-think of it like a business.
If I have $10,000 and I’ve got to build something for $1,000, that’s fine.
I’ll do that, but for a $10 million