I'm a bit baffled by this latest episode. The prior episodes seemed to have a decent handle on technological aspects, but this one... . What kind of outfit would have a Jenkins server but not a CM repository? Hell, I usually see the two tied together. :| The kid fubars your entire setup... it's called you roll back. Yeesh! Problem solved, and no getting bitch slapped over it!
I'm a bit baffled by this latest episode. The prior episodes seemed to have a decent handle on technological aspects, but this one... . What kind of outfit would have a Jenkins server but not a CM repository? Hell, I usually see the two tied together. :| The kid fubars your entire setup... it's called you roll back. Yeesh! Problem solved, and no getting bitch slapped over it!
I had a bigger problem with them pretending that "Cloud", hell not even "the cloud", was some mysterious super-hard thing to develop for. It's the fucking internet and the app was already shown to be an internet app. "Cloud" was done already.
The episode was based on a "The Big Bang" level moronic "nerd" joke for a series that has so far been targeted at IT knowledgeable viewers. I still found it a pretty enjoyable episode but the technical aspects were very subpar compared to previous episodes. Not that any have been awesome in that respect really, it's just that pretty much everyone is aware that "The Cloud" equals "Internet" now.
The ending scene of tonight's episode was hilarious. So far this TV has been rock solid. I actually enjoy it more than Game of Thrones.
as far as the whole "cloud" thing, i was thinking that the kid they brought in knew specific cloud technologies like hadoop and the other guys had no clue about it. that is what i thought they meant by having him come in and "get the cloud up", not that it was just a server on the internet he was getting up.
my top two favorite scenes.
https://www.youtube.com/watch?v=oyVksFviJVE
https://www.youtube.com/watch?v=oyVksFviJVE
Moving an existing app to the cloud CAN be pretty hard, depending on how you do it.
Depending on your persistence layer, or how you handle sessions, you may need to do some pretty serious refactoring.
If you really want to set up an app to utilize the uber-scalability feature of a cloud service, you typically need to break the app into services and use a queuing or messaging architecture to tie them together.
Azure offers messaging service backplanes that can span multiple data centers with various fail over scenarios built in. That can be a lot to wrap your head around if you were used to doing single instance apps.
However, I can't really forgive the no source control.
Best episode of the season.