News for hackers. Stuff that matters.
Re:Google nabs Apple as a cloud customer by bsder on Wednesday March 16, 2016 @09:08PM (#11301946)
> Can someone explain to me why traffic is still so damn expensive with every cloud provider?

Because The Cloud(tm) IS cheaper--when you start and don't have any real bandwidth or CPU usage.

Whereas, every colocation facility I have quoted wants you to commit to a minimum of $500 for some partial cabinet. So, The Cloud(tm) wins the contract and gets to bill in increasing amounts when usage finally goes up.

Finally, how many real system administrators still exist who can provision your systems, configure the network, and understand how to connect everything to the network without getting p0wn3d? If you don't have that person, you can't escape The Cloud(tm) even if you wanted to.

Re:Google nabs Apple as a cloud customer by manigandham on Wednesday March 16, 2016 @09:22PM (#11301995)
> Finally, how many real system administrators still exist

... a lot? Has there been some shortage of network/infrastructure people lately?

Re:Google nabs Apple as a cloud customer by tracker1 on Wednesday March 16, 2016 @11:23PM (#11302384)
Well, considering how many small/startup shops expect the developers to also do IT chores, "the cloud" makes the most sense... spending time learning the insides of systems they don't care to truly maintain comes at a cost... time to do other things, or cost to pay someone else to do it.

In the end, the cloud makes sense in a lot of scenarios.

Re:Google nabs Apple as a cloud customer by vidarh on Thursday March 17, 2016 @05:59AM (#11303464)
"The cloud" does not mean you don't need real system administrators. I see time and time again companies get bitten by this. Overall devops efforts to run this well on AWS or GCE in my experience tends to be higher than provisioning dedicated systems because you have so many artificial limits imposed on you by the providers that makes things harder.

E.g. your example: Understanding how to connect everything to the network without getting hacked is far easier when your private network is physically wired to a separate switch, and your public network is physically behind a firewall and there's no configuration mistake in the world you could do that would change that, so the problem-space to get basic levels of security is reduced to configuring the firewalls correctly.

Still plenty of room to shoot yourself in the foot, but in my experience far less so than having people configure their own networking on AWS.

As or pricing, yes, if you want to do colo, the initial costs are higher. But dedicated rented servers with monthly contracts are also typically far cheaper than AWS for anything that stays up for more than ~1/3 or so of the time (obviously depends on the hosting povider). If you regularly spin up lots of instances for a short period of time, you should use AWS. But the moment you stop spinning them down again, it's time to rent capacity somewhere else.