Comments on: To scale web services, devops devotees should consider economics

By: developers

developers — Mon, 19 Nov 2012 11:12:22 +0000

Devops is an industry buzzword that arose to describe the collaboration of
development and operations teams to obliterate the silos that impede projects.
Along the same lines, continuous delivery is the automated implementation of
the build, deploy, test, and release processes. As more teams embrace the
devops philosophy and implement continuous delivery on their projects, more
platforms and services will move toward a self-service model that encourages
this collaboration. A traditional product development approach with a thorough planning stage
and several years long delivery is no longer acceptable. Efficiency today means receiving maximum profit from each resource unit as early as possible. In the same time, development process should be perfect from both technological and business side. That’s why DevOps aims to build effective teams and configure systems, which lead to the delivery of reliable software and business benefit. Agile developers to provide agile support by giving developers production access to their applications, servers, and databases to improve their ability to do application support and troubleshooting.

By: str0nglytyped

str0nglytyped — Thu, 08 Nov 2012 16:52:44 +0000

This is good insight, especially for people who think this stuff is easy :) Managing web services on a large scale for companies the size of Amazon requires a lot of outside the box thinking. If you’re ever interested in learning more, this is a great resource that I’ve been reading at my library: http://www.igi-global.com/journal/international-journal-web-services-research/1079

By: Marlon Feld, WebINTENSIVE Software

Marlon Feld, WebINTENSIVE Software — Thu, 04 Oct 2012 22:08:46 +0000

This strikes me as excellent advice, though I’m not sure the takeaway is that CS majors need to take more econ and business courses – it’s more that developers need to be aware of the business impact of what they may think of as purely technical decisions. Your company’s specific business goals for the system being developed should be shaping the tradeoffs that you make. And any decision that has the potential to add or subtract overhead – as with the fit of your architecture to your hosting solution – needs to be considered very carefully.

By: Mike Condy

Mike Condy — Thu, 04 Oct 2012 21:05:54 +0000

We are still in trial mode so anyone that has the same problems can get some help at
http://www.foglight-on-demand.com/content/en/index.html

By: Mike Condy

Mike Condy — Thu, 04 Oct 2012 21:04:40 +0000

Stacey, great points, they very much match experience. When first we started to build cloud based application we were regularly had unexpected rises in our costs. When we designed and built originally there was some ignorance regarding the choices and so we did what we’d normally do, we built the app. Then we came to the initial deployment and what we really cared about was the availability not cost. We improved on what we had and recruited a few trial users and became interested in response time. We recruited more users and needed to know about quality of service. Only when you start to recruit users in numbers do the implications of the performance / architecture / cost trade off become apparent. Now we care about cost again.
Odd really since the tools we were building were to help identify and ameliorate just these problems.

By: sandeepsabir

sandeepsabir — Wed, 03 Oct 2012 18:04:09 +0000

Thanks for posting this. Today I watched documentary film that deals with the subject of Economic Calculation, Market Rationale and its effects, along with considerations of the Scientific Principles of Sustainability titled ‘Culture in Decline: Economics 101′. I recommend you to watch this, if you did n’t watch yet.

http://www.thegreatplanet.com/culture-in-decline-economics-101-2012/

By: Vinod Shintre

Vinod Shintre — Wed, 03 Oct 2012 03:57:23 +0000

great point & certainly there is a need for a recommendation service which would seamlessly fit into existing devops processes. As cloud consumption grows beyond few 1000 $, this will see a new challenge in enforcing the CLOUD IT consumption policy one may want to put in place. Attribo is solving this piece of the puzzle which will avoid friction in devops & offer real-time view into your amazon cloud infra. more at http://www.attribo.com

By: 28

28 — Tue, 02 Oct 2012 11:49:37 +0000

Application optimization is definitely the first place to start. Without a speedy app, other things such as DNS and network will have much less of an impact. But DO LOOK at those items later. Many organizations underestimate how poor DNS impacts performance, and that’s something we specialize in at Total Uptime: http://totaluptimetech.com/solutions/cloud-dns/