Word of the Day: dependency hell

Word of the Day Daily updates on the latest technology terms | February 15, 2019 dependency hell Dependency hell is a negative situation that occurs when a software application is not able to access the additional programming it requires in order to work. In sofware development, additional programs that software requires are called dependencies. Sometimes known as JAR hell or classpath hell, dependency hell's common outcomes include software performing abnormally, bugs, errors messages when trying to run or install software, or the software ceasing to function. Many times, these software dependencies are developed by third parties. The cause of dependency hell is varied, but it usually happens for one of four reasons: The main software relies on a multitude of large software libraries, causing lengthy downloads and decreasing the portability of the software. Even if an application requires only a small portion of a large library, the whole library must be downloaded. The main software creates a chain of dependencies, where the software relies on product A, but A relies on product B to function, and B needs product C to work properly. Conflicting programs that require different versions of software or libraries to work. Application X requires software FF version 2.0 to work, while application Y requires software FF version 2.5 to work, and both versions of FF cannot be installed at the same time. The software's requirements create circular dependencies. Application Y version 3.1 requires software EE. Software EE requires application W to work. Application W depends on software HH. And software HH relies on Application Y version 2.6. These dependencies can be a major headache for users and software creators alike, hence the hell designation. However, package managers and automated testing have incorporated dependency checking tools to alleviate some of these dependency hells. Advanced application development and deployment environments such immutable infrastructures are a great means of avoiding these kinds of dependency problems and uncontrolled change. The IT team can package and deploy an app in a self-contained manner. When a change is made, the entire image is recreated and redeployed, not patched in-place. Quote of the Day "Most stories of a migration to microservices start with developers yearning for more application stability during frequent code updates, or the ability to scale without resource compromises, or a route out of dependency hell." - Meredith Courtemanche Trending Terms dependency checking immutable infrastructure JAR file continuous integration DevOps continuous software development Learning Center Developer search prompts a migration to microservices Ibotta's software team kicked off a migration to microservices to build a modern, skilled development team. Here's what they want other application teams to know. RHEL 8 promises relief from dependency hell, more integration The RHEL 8 roadmap is headed for a streamlined deployment and management process, more integration with other vendors and a matured enterprise server OS. When DevOps and requirements gathering techniques collide Requirements gathering techniques can and should vary from Agile to DevOps. Expert Christopher Ward sees it as an opportunity for collaboration. Five approaches to IT resiliency that don't need new hardware IT resiliency goes beyond N+1 hardware clusters, relying instead on cloud design, snapshots and containerization, among other technologies. ALM best practices for advanced DevOps organizations This guide on ALM best practices compiles the important considerations for organizations transitioning from Agile to DevOps. Quiz Yourself If you?re not _______ well-versed in microservices and containers, you?re running at the back of the pack. A. already B. all ready Answer Stay in Touch For feedback about any of our definitions or to suggest a new definition, please contact me at: mrouse@techtarget.com Visit the Word of the Day Archives and catch up on what you've missed! FOLLOW US About This E-Newsletter This e-newsletter is published by the TechTarget network. To unsubscribe from Whatis.com, click here. Please note, this will not affect any other subscriptions you have signed up for. TechTarget, Whatis, 275 Grove Street, Newton, MA 02466. Contact: webmaster@techtarget.com Copyright 2018 TechTarget. All rights reserved.