Commentary

John Foley
Editor, InformationWeek  

How Eli Lilly Taps Into The Cloud

I'm expecting 2009 to be a year in which large companies embrace cloud computing in greater numbers. But how will they do it? And why? Eli Lilly, an early adopter of Amazon Web Services, will discuss its motivations and experiences in an upcoming InformationWeek Webcast.

I'm expecting 2009 to be a year in which large companies embrace cloud computing in greater numbers. But how will they do it? And why? Eli Lilly, an early adopter of Amazon Web Services, will discuss its motivations and experiences in an upcoming InformationWeek Webcast.Eli Lilly is using on-demand servers and storage from Amazon to support its pharmaceuticals research. Dave Powers, an IT pro with Eli Lilly who is helping to spearhead that effort, says the speed of implementation, flexibility, and collaborative capabilities of cloud services are "absolutely disruptive" in how the company thinks about and deploys IT resources.

I talked to Dave yesterday, and two things became clear. First, Eli Lilly's adoption of cloud services are being driven by real business requirements to manage costs while making high performance computing available to the company's researchers. Dave says there's a "sense of urgency to change" at Eli Lilly. And second, Eli Lilly is still working through the challenges of cloud computing, including how to coordinate and manage the use of cloud services from multiple service providers.


More Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Dave will talk about these issues and more in InformationWeek's "How To Plug Into The Cloud" Webcast, which takes place Thursday, Jan. 8, at 2 p.m. Eastern. Adam Selipsky, VP of product management and developer relations for Amazon Web Services, also will be a featured speaker, and I'll be moderating it all. To hear more about how Eli Lilly is using the cloud and its plans for the future, join us. You can register 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