A Cloud Methodology

From PC Break/Fix to CloudMASTER®

By G C Network | August 29, 2016

https://www.linkedin.com/in/stevendonovan It was late 2011 and Steven Donovan was comfortable working at SHI International Corporation, a growing information technology firm, as a personal computer break/fix technician. His company had been…

Is Data Classification a Bridge Too Far?

By G C Network | August 17, 2016

Today data has replaced money as the global currency for trade. “McKinsey estimates that about 75 percent of the value added by data flows on the Internet accrues to “traditional”…

Vendor Neutral Training: Proven Protection Against Cloud Horror Stories

By G C Network | August 10, 2016

Cloud computing is now entering adolescence.  With all the early adopters now swimming in the cloud pool with that “I told you so” smug, fast followers are just barely beating…

Cognitive Business: When Cloud and Cognitive Computing Merge

By G C Network | July 21, 2016

Cloud computing has taken over the business world! With almost maniacal focus, single proprietors and Board Directors of the world’s largest conglomerates see this new model as a “must do”.…

Government Cloud Achilles Heel: The Network

By G C Network | July 9, 2016

Cloud computing is rewriting the books on information technology (IT) but inter-cloud networking remains a key operational issue. Layering inherently global cloud services on top of a globally fractured networking…

System Integration Morphs To Cloud Service Integration

By G C Network | June 19, 2016

Cloud Service Brokerage is changing from an industry footnote toward becoming a major system integration play.  This role has now become a crucial component of a cloud computing transition because…

Networking the Cloud for IoT – Pt 3 Cloud Network Systems Engineering

By G C Network | June 17, 2016

Dwight Bues & Kevin Jackson (This is Part 3 of a three part series that addresses the need for a systems engineering approach to IoT and cloud network design.  Networking the Cloud for IoT –…

Networking the Cloud for IoT – Pt. 2 Stressing the Cloud

By G C Network | June 12, 2016

Dwight Bues & Kevin Jackson This is Part 2 of a three part series that addresses the need for a systems engineering approach to IoT and cloud network design. Part…

Networking the Cloud for IoT – Pt. 1: IoT and the Government

By G C Network | June 7, 2016

  Dwight Bues & Kevin Jackson This is Part 1 of a three part series that addresses the need for a systems engineering approach to IoT and cloud network design:…

Parallel Processing and Unstructured Data Transforms Storage

By G C Network | May 31, 2016

(This post originally appeared on Direct2Dell, The Official Dell Corporate Blog) Enterprise storage is trending away from traditional, enterprise managed network-attached storage (NAS) and storage area networks (SAN) towards a…

Although this was published in June, I just saw it and felt it was to good not to repeat:

A Methodology for Cloud Computing Architecture

  • Peel off the applications individually, to detangle the appliance mess (use case analysis).
    Categorize applications as batch, online, heavy transactional, or reporting – where the former two indicate likely cloud apps.
  • Think of cloud computing as a way to load balance your application demands across different grids of available resources.
  • Slide the clouds across different grids depending on costs, scheduling needs, or failover capacity.
  • Take the hit to replicate critical data across different grids, to have it ready for a cutover within minutes; that’s less expensive than buying insurance.
  • Run your own multiple data centers as internal grids, but have additional grid resources ready for handling elastic demands (which you already have, in quantity).
  • Reassure your DBAs and sysadmins that their roles are not diminished due to cloud computing, and instead become more interesting – with hopefully a few major headaches resolved.
Follow me at https://Twitter.com/Kevin_Jackson

G C Network

1 Comments

  1. Nick on March 7, 2010 at 5:52 pm

    A couple nice points made, like load balancing / HA across clouds, and assuring employees they will keep jobs. This seems more like notes or brainstorm jotted down. 6 points do not make a systems methodology.