Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

The Woes of Cloud Computing Expand / Collapse
Author
Message
Posted Wednesday, August 3, 2011 9:36 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Yesterday @ 11:35 AM
Points: 33,102, Visits: 15,213
Comments posted to this topic are about the item The Woes of Cloud Computing






Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #1153974
Posted Wednesday, August 3, 2011 10:13 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Today @ 12:17 AM
Points: 36,800, Visits: 31,261
I've found that one of the biggest reasons why people originate or move databases to the cloud is so that you don't have to have a lot of hardware locally. Once that's done, it's not like people are going to have a free server with enough storage space just idling around wait for you to move something back from the cloud.

Because of that, one of two things will likely happen... either the requirement to move something back from the cloud will suddenly become a whole lot less important or there will be a huge panic tring to get equipment in place along with the funding to get it there.

My recommendation is to be very, very careful about what you migrate to the cloud to begin with because, once it's there, it's going to be a real bugger to bring back locally. To coin a phrase... "What goes up... may just stay there."


--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #1153985
Posted Thursday, August 4, 2011 6:23 AM


Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Monday, May 7, 2012 9:23 AM
Points: 304, Visits: 716
"The cloud isn't the ultimate answer, and you ought to have a backup plan, which should include the ability to move your services back to your own data center."

This is a strange and rather unrealistic statement. If a company moves to the cloud, they are (99.99% of the time) sold on the cloud from an economic standpoint. So what IT Director is going to invest in Cloud computing AND have to maintain a Data Center 'just in case'. Try pushing that one past a CEO and you will either be laughed out of the office, or worse, fired for being slightly braindead as you double or triple IT costs.

Cloud computing suffers from the same lack of vision that has plagued technology for decades. It all sounds like a great idea until you really get under the hood and realize what you are giving away, and worse, what the unknowns are. As much as it has application in some limited implementations, generally its more like the Palm Pilot or other such "change the world" inventions - that never changed the world.

Think of it this way - suppose you use an on-line backup service in your personal or professional life. Have you read the fine print in the agreement? Do you know that if they lose all your data they have lawyers who have already insured you cannot hold them liable? Does that sound like a "good idea"? Of course, they didn't tell you that when you joined up. It all sounded so good until the inevitable struck.

If you go to the Cloud, be darn sure you read the fine print - as many companies have discovered, its not worth the risk because although they are happy to sell you, at this point they are not that interested in supporting you in a crisis, because of course, there never will be any crisis. Yeah, right... That surely has never happened in technology...



There's no such thing as dumb questions, only poorly thought-out answers...
Post #1154169
Posted Thursday, August 4, 2011 6:29 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, October 18, 2013 9:05 AM
Points: 100, Visits: 179
I don't know about bring it back in-house, but you certainly want the option to be able to move to another provider, should your provider have a large price increase or go out of business.
Post #1154172
Posted Thursday, August 4, 2011 7:13 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Yesterday @ 10:40 AM
Points: 1,606, Visits: 4,599
At this point, my impression is that it makes more sense to migrate datamarts and reporting databases to the cloud, and keep in-house those transactional databases that serve their core operations. There are situations where an organization needs to stand up additional instances of reporting servers to faciliate development teams or scale out to improve performance. However, it may not make economic sense to keep spare hardware and licenses sitting around in a closet just to faciliate these occasional needs, which sometimes may even be temporary or experimental in nature. So, my thinking is: scale up the transactional databases and keep in-house, and scale out the reporting databases and datamarts, for which the cloud offers new possibilities.
Post #1154205
Posted Thursday, August 4, 2011 8:29 AM
SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: Thursday, February 21, 2013 12:39 PM
Points: 29, Visits: 120
As a financial company, we rather lock all the data in our server room than put it on internet. An old style lock could stop any hacker.
Plus , the compute power is dirt cheap nowaday. The cost of 4 nodes cluster is less than 100k, and it could serve 2000 users very well.
Why bother?!


_______________________________________________________________
Post #1154271
Posted Thursday, August 4, 2011 8:40 AM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: 2 days ago @ 10:12 AM
Points: 4,394, Visits: 3,402
... plus my favorite reminder that many industries have legal requirements to keep data on the premises (such as pharmacies) or at least in the state (brokerages). For those, cloud is DOA.
Post #1154283
Posted Thursday, August 4, 2011 8:40 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Yesterday @ 11:35 AM
Points: 33,102, Visits: 15,213
Jeff Moden (8/3/2011)
I've found that one of the biggest reasons why people originate or move databases to the cloud is so that you don't have to have a lot of hardware locally. Once that's done, it's not like people are going to have a free server with enough storage space just idling around wait for you to move something back from the cloud.

Because of that, one of two things will likely happen... either the requirement to move something back from the cloud will suddenly become a whole lot less important or there will be a huge panic tring to get equipment in place along with the funding to get it there.

My recommendation is to be very, very careful about what you migrate to the cloud to begin with because, once it's there, it's going to be a real bugger to bring back locally. To coin a phrase... "What goes up... may just stay there."


One of the issues people have found is that development costs can skyrocket in the cloud. Developers send data back and forth, test things, eat up transactions with things like cross joins, etc. So those local servers still have a place.







Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #1154286
Posted Thursday, August 4, 2011 8:42 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Yesterday @ 11:35 AM
Points: 33,102, Visits: 15,213
blandry (8/4/2011)
"The cloud isn't the ultimate answer, and you ought to have a backup plan, which should include the ability to move your services back to your own data center."

This is a strange and rather unrealistic statement. If a company moves to the cloud, they are (99.99% of the time) sold on the cloud from an economic standpoint. So what IT Director is going to invest in Cloud computing AND have to maintain a Data Center 'just in case'. Try pushing that one past a CEO and you will either be laughed out of the office, or worse, fired for being slightly braindead as you double or triple IT costs.


I'm not sure that's true. Over time, perhaps, but most of the people moving to the cloud, including MS, are doing so an application at a time. So they still have some local resources. They may even always have some local resources for things like development.

There also are applications that people move to the cloud because of a "burst" of demand that may tail off and they decide to bring it back in house.







Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #1154288
Posted Thursday, August 4, 2011 9:03 AM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: 2 days ago @ 10:12 AM
Points: 4,394, Visits: 3,402
Steve Jones - SSC Editor (8/4/2011)
. . . There also are applications that people move to the cloud because of a "burst" of demand that may tail off and they decide to bring it back in house.

For burst demand, cloud is ideal. I had a client who is running Web sites for kiddie leagues, with tools that allow create their site easily. When the registration opens, they are running 500 tps for several hours; on any other day, 1 or 2 tps.

It makes sense to keep the app serving the pages and the databases in the cloud, and have local hardware just to serve pageframes and support development. They have not migrated yet, though, because they bought their hefty iron two years ago.
Post #1154310
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse