From 1861-1865, the U.S. was embroiled in a Civil War between the Confederate States of America (the Confederacy) and the Federal Government (known as the Union). The tactics employed during the conflict are best understood through a series of campaigns fought in places such as Manassas, Bull Run, Antietam, Fredericksburg, Chancellorsville and Gettysburg.
According to author and historian Stephen W. Sears, the Gettysburg campaign was the largest of the war. It lasted about 3-days (July 1 – July 3 1863) and accounted for combined losses of approximately 57,000 men. One of the actions that defined this battle, and perhaps the one that ultimately determined the outcome of the entire Civil War, is known as Pickett’s Charge.
After discussing the three levels of architecture we use at Intel, I try to impose some level of reality into the discussion by citing Pickett’s Charge as an example of a cause (think of it as a solution) that had an unforeseen effect on a broader strategy - something that’s essential to consider as you build your company’s cloud computing framework.
As always, I welcome your feedback and encourage you to share your company’s experiences about how you align top-down frameworks with cloud solutions.
For more information and any questions please feel free to contact me on LinkedIn.