Commentary

John Foley
Editor, InformationWeek  

Eli Lilly On What's Next In Cloud Computing

Eli Lilly's Dave Powers talks compellingly about how the pharmaceuticals company is using cloud computing services to support its scientists with on-demand processing power and storage. What's even more interesting, however, is what Eli Lilly has planned next.

Eli Lilly's Dave Powers talks compellingly about how the pharmaceuticals company is using cloud computing services to support its scientists with on-demand processing power and storage. What's even more interesting, however, is what Eli Lilly has planned next.An associate information consultant with Eli Lilly and 13-year company veteran, Powers gave an overview of his experiences with cloud computing last week in an InformationWeek Webcast. In late 2007, he said, the mindset among Eli Lilly's IT team was to take a wait-and-see approach to the emerging cloud services model. By early 2008, however, pressure was growing to reduce fixed IT costs without compromising on IT services, and cloud computing proved to be the answer.

Eli Lilly uses Amazon Web Services and other cloud services to provide high-performance computing, as needed, to hundreds of its scientists. With AWS, Powers said, a new server can be up and running in three minutes (it used to take Eli Lilly seven and a half weeks to deploy a server internally) and a 64-node Linux cluster can be online in five minutes (compared with three months internally). "The deployment time is really what impressed us," Powers said. "It's just shy of instantaneous."


More Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Looking ahead, Powers foresees the possibility of using cloud services from a half dozen different vendors, and he wants to head off a scenario where Eli Lilly has to configure and manage each of those separately. He describes the need for an "orchestration layer" that sits between Eli Lilly and the various cloud services to which it subscribes. That layer, provided by an intermediary company and not Eli Lilly itself, would comprise algorithms that determine the best cloud service for a particular job based on lowest cost, highest performance, or other requirement. Such an approach would make it possible for Eli Lilly and other users to write to a single API rather than many, while optimizing service usage.

He also talks about the potential to use cloud computing for external collaboration. Eli Lilly already is doing some of this, but Powers envisions going further, to the point where the cloud becomes "a point of integration" between Eli Lilly and outside researchers. "We have work going on right now that starts to fit into this collaborative scheme," he said.

To hear more about what Eli Lilly is doing with cloud computing and where it goes from here, log in to our recent Webcast, which is available for replay. In addition to Dave, I give an overview of cloud services in the Webcast, and Amazon VP Adam Selipsky describes Amazon Web Services. You can sign in here.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links