This is what came across my desk the other day from another blogger.
I haven't followed that link yet, but I'm betting it is interesting From: Virgil Bierschwale [mailto:[email protected]] Sent: Wednesday, October 09, 2013 2:33 PM To: 'Bud' Subject: RE: MUST READ! Here is the ole country boy way of developing something like this that I learned from the school of hard knocks, of which I was awarded a PHD. Developer server Test Server Production Server(s) All servers have the same engine on them down to the patch level. All development work is done on the development server, and all code is maintained in a library type system like sourcesafe When a release is ready to be released, the previous version on the test server is renamed and the release is copied to the test server. In the event that a problem shows up, the recent release is deleted immediately, and the original has its name restored and the test server is back up and running immediately. If the release passes test, the program on the production server is renamed and the release from the test server is copied up to all of the production server(s). Again, if a problem occurs, it is deleted immediately, and the renamed file is restored. Now, on a system like this, since there are 315 million people in America, you want to scale it so that you can handle 10 percent of them all at once. So, if one server could handle 1 million hits at a time, you would want 31 servers MINIMUM But hey, I'm just a dumb ole country boy that apparently can't even write a proper resume, so what do I know? From: Bud [mailto:[email protected]] Sent: Wednesday, October 09, 2013 2:19 PM To: Virgil Bierschwale Subject: MUST READ! Now that the health insurance exchanges are open, we discover they are crashing over a week later and worse, team Obama hired foreigners to design healthcare.gov --- It never ceases to amaze how just how much money is poured into bad government websites. It is truly astounding when supposedly American companies are the best in the world and there are so many unemployed with tech skills, the government cannot manage to hire Americans and American companies to do the job. When we say Americans, we do not mean IBM and other such companies who fire those with U.S. citizenship and bring in foreign guest workers. We mean those with U.S. citizenship. Now the truth is coming out on healthcare.gov. The Obama administration is still claiming the exchange website flaws is due to the large traffic visiting the site, yet American engineers are analyzing and railing against the poor design. Think about the millions of dollars and three and a half years to get a website working when most American techies can find the technical problems in a matter of minutes. This is how poorly designed the site is. Even the IEEE is pointing out the technical flaws and is mentioning the obvious security. http://www.economicpopulist.org/content/real-care-obamacare-or-no-care-5394 _____ No virus found in this message. Checked by AVG - www.avg.com Version: 2014.0.4142 / Virus Database: 3609/6735 - Release Date: 10/09/13 --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
