Home > Articles > Networking > Storage

  • Print
  • + Share This
Like this article? We recommend

Consolidating Applications

Understanding which server resources applications use and understanding usage patterns is essential to the process of consolidating servers. This process is explained in detail in the chapters about assessment and architecture.

Everywhere we go to talk about consolidation, people always ask which applications they should or should not consolidate. There is no easy answer to this question, and you need to evaluate each application individually. The people who know the applications best are the developers, database administrators, and system administrators who take care of them on a daily basis. Talking with these people usually identifies good and bad consolidation candidates rather quickly.

Eliminating Consolidation Candidates

While it is not easy to make specific recommendations about which applications are good consolidation candidates, there are some general guidelines you can follow to eliminate candidates from consolidation.

First and foremost, consider eliminating all servers and storage that are deliberately isolated for other servers. This includes:

  • Firewalls

  • Intrusions detection servers

  • Sensitive databases

  • Geographically separated servers

Isolation and separation are vital attributes of many security-related servers. Unless you are specifically targeting these machines, they are probably too complex to consolidate without a complete reevaluation of the security architecture. After you have consolidated the rest of your environment, you can come back and look for opportunities for security consolidations. The same is true for servers or storage that are geographically separated. For instance, if you have separated servers for redundancy or wide area network (WAN) reasons, it hardly makes sense to try to consolidate these together.

Third-party applications developed and sold by independent software vendors (ISVs) may be problematic as consolidation candidates. In many cases, ISVs specify that their applications run in standalone mode on their own servers. If this is not done, they usually do not provide support for the application. Make sure you check with your vendors for their support requirements.

Other applications that do not qualify for consolidation include those that lock up system resources such as physical memory. If you aren't sure about an application's suitability for consolidation in this respect, make sure you analyze it with a performance tool such as TeamQuest or BMC's Patrol-Perform and Predict.

Applying Backward and Forward Consolidation Strategies

When most people begin their consolidation efforts, they often focus on existing applications. This process is known as a backward consolidation. In many cases, these consolidations are hugely successful. In others, organizational issues prevent them from achieving their goals. There is no doubt that some of the largest and most successful consolidations we have seen have been backward consolidations.

To avoid future server sprawl, it is also important to begin to develop new applications in a consolidated environment, referred to as forward consolidation. It's interesting to note that applications that are developed in a consolidated environment usually behave with each other, and can be moved into production in a consolidated environment.

Consolidating Application Sets

When you analyze a group of servers for consolidation, it is important to identify the applications that run on them. It is equally important to identify the servers and applications with which the consolidation candidates interact. It's very common to find groups of applications that receive data from other applications or that supply data to other applications. Because these applications process information sequentially, they are often excellent candidates for consolidation. These application sets don't usually compete for the same resources at the same time, and when you group them within a single instance of the OS, you often find that they perform better because of intra-domain communications. A decrease in network traffic is often a side benefit of consolidating application sets.

When deciding which application sets to consolidate, we generally categorize them as being tightly coupled or loosely coupled. In tightly coupled application sets, applications actively interact with each other. In loosely coupled sets, a group of applications acquire and process data and then pass them on to the next server.

As an example of a successful consolidation of tightly coupled applications, consider a situation where a customer gathered home-grown Enterprise Resource Planning applications, Tuxedo messaging, and an Oracle database server and moved them into a single instance of the OS. The results were extremely successful. Application throughput increased, and network usage decreased. From a scalability viewpoint, the transaction volume of the application set increased from roughly 40,000 sales order lines per day two years ago to over 400,000 sales order lines per day. This was obviously a successful consolidation and a successful application of vertical scalability.

As an example of a loosely coupled application set, consider a situation where a server runs an online transaction processing (OLTP) application during the day, then at night, passes the transaction information to a batch server for further processing and reporting. The batch server would then update a data warehouse server, which would, in turn, update multiple data mart servers. Each server depends on another, but not simultaneously.

Consolidating Multiple Database Instances

A very common example of server and application consolidation is to put multiple instances of a database in a single instance of the OS. This is a very common tactic with most major databases. It's important to note that you don't want to mix these two databases on the same instance of the OS; doing so may cause fatal application conflicts.

The success of this consolidation strategy depends heavily on development standards and practices. Where strict naming conventions are followed and each instance of the database is unique, consolidations are successful. However, on an occasion when we worked with a customer who wrote multiple Oracle applications and chose to use default naming conventions, multiple conflicts resulted between database instances. Obviously, this consolidation was not successful.

Consolidating Similar Workloads

Another consolidation technique that some consultants recommend is to consolidate similar workloads with like resource usage and time scheduling. If you do this, you need to understand the application's resource usage very clearly. When using this consolidation technique, the key to success is that you must offset the timing of resource usage for each workload. Otherwise, you simply end up with overlapping peaks and valleys of resource usage.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020