Welcome!

Microservices Expo Authors: Stackify Blog, Aruna Ravichandran, Dalibor Siroky, Kevin Jackson, PagerDuty Blog

Related Topics: Microservices Expo

Microservices Expo: Article

SOA to the Rescue, When Drug Discovery Needs Data Fast!

Information is key to drug discovery

As the demand for new medicines grows, so does the need for better information to manage and execute the R&D processes. There is huge pressure to make informed decisions, especially during the project's early stages when the risk is high and before downstream costs are added.

Pfizer spends billions on research projects annually. At Pfizer Global R&D where the company's drug discovery takes place, research scientists and managers require vast amounts of up-to-the-minute information on lab results, submission status, and project schedules to move new research forward quickly. Management must constantly analyze the entire portfolio of new medicines in discovery to look for opportunities, trends, and areas where attention is needed. Researchers and managers strive to bring together the best in ideas, practices, policies as well as the use of information.

At Pfizer's Research Informatics Division within Global Research and Development, we seek to provide the best information possible to our R&D customers. Meeting this mission requires constant innovation. Over the past several years, we have faced a number of challenges, causing us to evolve our information delivery methods and technologies significantly. These include a new approach to real-time data integration, such as using SOA data services that lets us build new solutions more rapidly and in alignment with our SOA strategies.

Data Integration Is a Critical Requirement
At Pfizer R&D, the information required for executing and managing projects is drawn from many sources, including laboratory research, historical records, clinical trials, and business intelligence. The data is complex, diverse, and spreads across the company in various technology and application silos.

Through innovative use of analytics, reporting, and portal technology, we have made great strides toward improving how this information is presented internally. However, data integration remains the biggest challenge in effectively providing information to our researchers and managers.

Why is this critical? To properly assess a portfolio of discovery projects, Pfizer managers must pull data from sources such as packaged applications, historical data from data warehouses, document repositories, and custom systems. Each source has its own access mechanisms, syntax, and security. Few are structured properly for consumption, let alone reuse. These combined factors slow down new application development projects.

Time Is of the Essence!
To move new research forward as quickly as possible, our research scientists and managers must have critical up-to-date information from across our wide array of source systems. If information is only refreshed monthly, then necessary course corrections are typically delayed by several weeks. A few weeks may not sound like a lot, but on a 24-month project, these weeks can easily add up to six months or more.

For new IT projects, time is of the essence. Business agility requires IT agility. Pfizer's researchers and managers, like their business user counterparts, constantly make new demands on IT for new information systems to help the business perform more efficiently, effectively, and competitively. This means we must build new systems quickly. Rapid application development (RAD) techniques are highly desired. In fact, we continuously evaluate our Enterprise Development Life Cycle (EDLC) processes with a primary objective of reducing time-to-solution with faster responses to business needs.

SOA-Compliance Is an Important Requirement
Our SOA adoption has accelerated in recent years. Specifically, we use SOA approaches to increase reuse of existing components, save development time, and cut costs. So, we strive to use SOA methods and technologies whenever possible.

With respect to SOA and data integration, we've found that SOA helps break down silo-type data gathering and integration processes by standardizing how data is promoted and reused. The ability to virtualize and abstract via data services helps groups to easily understand and consume data confidently, reliably, and quickly without having to hunt for these sources or rely on manual processes for gathering and integrating them.

Old Extract & Mart-based Approaches Can't Meet New Requirements
Traditionally, Pfizer has used three approaches to data integration. The first is custom coding directly between sources and consuming applications. This works well for our simple integration problems where there are one or two defined sources and little transformation is needed. But as additional sources are added, and complex data structures are ever changing, this delivery approach has severe limitations.

Second, we've used replicated file extracts as a way to integrate data. File extracts handle data silos more efficiently than custom coding. For example, application teams that need data receive periodic file extracts from the application teams that manage the source data applications. This arms-length batch approach minimizes the impact on source systems and is useful for daily transaction summaries, shared reference data, etc. However, data integration beyond simple access - abstraction, transformation, federation, and more - requires extra work by the consuming team. This method proliferates replicated data without any controls on quality, security, and scalability.

Extract, Transform, and Load (ETL) with data marts or warehouses is our third approach to data integration. This kind of physical data replication has several advantages in terms of rationalizing and combining heterogeneous data from multiple sources. For large-scale multi-dimensional analysis, we find data warehouses are effective solutions given their ability to support the large volumes and significant schema transformations typically required. To date, this has been the data integration approach of choice for our medium and large-scale data integration projects.

Unfortunately, these three approaches may not be entirely effective with our customers. Because our customers must make decisions based on near real-time data, they often can't afford the extra development time required for building and testing custom coding, file extracts, and data marts. Forcing our business users to wait extra months for new solutions to be developed has a huge impact on how quickly we get new drugs to market.

Further, typical data mart/replication architectures don't easily fit into our new SOA strategy. New data integration projects must be SOA-enabled from the start, so they can deliver value moving forward.

Given the accelerating business demand for new systems from the R&D groups we support, my team decided to find a new approach to data integration that lets us build additional real-time solutions more rapidly, and in alignment with our SOA strategies, while avoiding the replication downside.

To do this, we launched a project with the goal of identifying and adopting a new approach to data integration that meets the following criteria:

  1. Complex data integration across multiple heterogeneous sources without unnecessary data replication,
  2. Real-time information delivery,
  3. Rapid application development, and
  4. SOA-compliance.

More Stories By Daniel Eng

Daniel Eng has over 17 years of diverse IT experience in managing projects, leading technical teams, and developing enterprise applications within Fortune 100 companies. Currently at Pfizer Global Research and Development, Dan is leading efforts in transitioning business processes and applications into a SOA environment by using emerging technologies and agile management practices. Prior to Pfizer, he was an independent consultant helping his Fortune 500 clients in developing intranet sites, portable applications and e-commerce solutions. Dan has also worked in many e-commerce start-ups and healthcare organizations. He holds a BSEE degree from Polytechnic University and an MBA degree from Gonzaga University.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


@MicroservicesExpo Stories
How is DevOps going within your organization? If you need some help measuring just how well it is going, we have prepared a list of some key DevOps metrics to track. These metrics can help you understand how your team is doing over time. The word DevOps means different things to different people. Some say it a culture and every vendor in the industry claims that their tools help with DevOps. Depending on how you define DevOps, some of these metrics may matter more or less to you and your team.
For many of us laboring in the fields of digital transformation, 2017 was a year of high-intensity work and high-reward achievement. So we’re looking forward to a little breather over the end-of-year holiday season. But we’re going to have to get right back on the Continuous Delivery bullet train in 2018. Markets move too fast and customer expectations elevate too precipitously for businesses to rest on their laurels. Here’s a DevOps “to-do list” for 2018 that should be priorities for anyone w...
If testing environments are constantly unavailable and affected by outages, release timelines will be affected. You can use three metrics to measure stability events for specific environments and plan around events that will affect your critical path to release.
In a recent post, titled “10 Surprising Facts About Cloud Computing and What It Really Is”, Zac Johnson highlighted some interesting facts about cloud computing in the SMB marketplace: Cloud Computing is up to 40 times more cost-effective for an SMB, compared to running its own IT system. 94% of SMBs have experienced security benefits in the cloud that they didn’t have with their on-premises service
DevOps failure is a touchy subject with some, because DevOps is typically perceived as a way to avoid failure. As a result, when you fail in a DevOps practice, the situation can seem almost hopeless. However, just as a fail-fast business approach, or the “fail and adjust sooner” methodology of Agile often proves, DevOps failures are actually a step in the right direction. They’re the first step toward learning from failures and turning your DevOps practice into one that will lead you toward even...
DevOps is under attack because developers don’t want to mess with infrastructure. They will happily own their code into production, but want to use platforms instead of raw automation. That’s changing the landscape that we understand as DevOps with both architecture concepts (CloudNative) and process redefinition (SRE). Rob Hirschfeld’s recent work in Kubernetes operations has led to the conclusion that containers and related platforms have changed the way we should be thinking about DevOps and...
While walking around the office I happened upon a relatively new employee dragging emails from his inbox into folders. I asked why and was told, “I’m just answering emails and getting stuff off my desk.” An empty inbox may be emotionally satisfying to look at, but in practice, you should never do it. Here’s why. I recently wrote a piece arguing that from a mathematical perspective, Messy Desks Are Perfectly Optimized. While it validated the genius of my friends with messy desks, it also gener...
The goal of Microservices is to improve software delivery speed and increase system safety as scale increases. Microservices being modular these are faster to change and enables an evolutionary architecture where systems can change, as the business needs change. Microservices can scale elastically and by being service oriented can enable APIs natively. Microservices also reduce implementation and release cycle time and enables continuous delivery. This paper provides a logical overview of the Mi...
The next XaaS is CICDaaS. Why? Because CICD saves developers a huge amount of time. CD is an especially great option for projects that require multiple and frequent contributions to be integrated. But… securing CICD best practices is an emerging, essential, yet little understood practice for DevOps teams and their Cloud Service Providers. The only way to get CICD to work in a highly secure environment takes collaboration, patience and persistence. Building CICD in the cloud requires rigorous ar...
The enterprise data storage marketplace is poised to become a battlefield. No longer the quiet backwater of cloud computing services, the focus of this global transition is now going from compute to storage. An overview of recent storage market history is needed to understand why this transition is important. Before 2007 and the birth of the cloud computing market we are witnessing today, the on-premise model hosted in large local data centers dominated enterprise storage. Key marketplace play...
The cloud revolution in enterprises has very clearly crossed the phase of proof-of-concepts into a truly mainstream adoption. One of most popular enterprise-wide initiatives currently going on are “cloud migration” programs of some kind or another. Finding business value for these programs is not hard to fathom – they include hyperelasticity in infrastructure consumption, subscription based models, and agility derived from rapid speed of deployment of applications. These factors will continue to...
Some people are directors, managers, and administrators. Others are disrupters. Eddie Webb (@edwardawebb) is an IT Disrupter for Software Development Platforms at Liberty Mutual and was a presenter at the 2016 All Day DevOps conference. His talk, Organically DevOps: Building Quality and Security into the Software Supply Chain at Liberty Mutual, looked at Liberty Mutual's transformation to Continuous Integration, Continuous Delivery, and DevOps. For a large, heavily regulated industry, this task ...
Following a tradition dating back to 2002 at ZapThink and continuing at Intellyx since 2014, it’s time for Intellyx’s annual predictions for the coming year. If you’re a long-time fan, you know we have a twist to the typical annual prediction post: we actually critique our predictions from the previous year. To make things even more interesting, Charlie and I switch off, judging the other’s predictions. And now that he’s been with Intellyx for more than a year, this Cortex represents my first ...
"Grape Up leverages Cloud Native technologies and helps companies build software using microservices, and work the DevOps agile way. We've been doing digital innovation for the last 12 years," explained Daniel Heckman, of Grape Up in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
The Toyota Production System, a world-renowned production system is based on the "complete elimination of all waste". The "Toyota Way", grounded on continuous improvement dates to the 1860s. The methodology is widely proven to be successful yet there are still industries within and tangential to manufacturing struggling to adopt its core principles: Jidoka: a process should stop when an issue is identified prevents releasing defective products
We seem to run this cycle with every new technology that comes along. A good idea with practical applications is born, then both marketers and over-excited users start to declare it is the solution for all or our problems. Compliments of Gartner, we know it generally as “The Hype Cycle”, but each iteration is a little different. 2018’s flavor will be serverless computing, and by 2018, I mean starting now, but going most of next year, you’ll be sick of it. We are already seeing people write such...
Defining the term ‘monitoring’ is a difficult task considering the performance space has evolved significantly over the years. Lately, there has been a shift in the monitoring world, sparking a healthy debate regarding the definition and purpose of monitoring, through which a new term has emerged: observability. Some of that debate can be found in blogs by Charity Majors and Cindy Sridharan.
It’s “time to move on from DevOps and continuous delivery.” This was the provocative title of a recent article in ZDNet, in which Kelsey Hightower, staff developer advocate at Google Cloud Platform, suggested that “software shops should have put these concepts into action years ago.” Reading articles like this or listening to talks at most DevOps conferences might make you think that we’re entering a post-DevOps world. But vast numbers of organizations still struggle to start and drive transfo...
Let's do a visualization exercise. Imagine it's December 31, 2018, and you're ringing in the New Year with your friends and family. You think back on everything that you accomplished in the last year: your company's revenue is through the roof thanks to the success of your product, and you were promoted to Lead Developer. 2019 is poised to be an even bigger year for your company because you have the tools and insight to scale as quickly as demand requires. You're a happy human, and it's not just...
"Opsani helps the enterprise adopt containers, help them move their infrastructure into this modern world of DevOps, accelerate the delivery of new features into production, and really get them going on the container path," explained Ross Schibler, CEO of Opsani, and Peter Nickolov, CTO of Opsani, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.