Case Studies New Relic supports Next Update as it expands its Sifter bug and issue tracking application and improves availability

Edit This Case Study Record

	New Relic supports Next Update as it expands its Sifter bug and issue tracking application and improves availability

New Relic supports Next Update as it expands its Sifter bug and issue tracking application and improves availability

Technology Category	Application Infrastructure & Middleware - API Integration & Management
Applicable Industries	Software
Applicable Functions	Discrete Manufacturing Quality Assurance
Use Cases	Predictive Maintenance Real-Time Location System (RTLS)
Services	Software Design & Engineering Services System Integration
Challenge	Next Update, a small company founded in 2008, developed a SaaS-based bug and issue tracking application called Sifter. The application was designed to simplify the bug tracking process and make it accessible to both technical and non-technical team members. However, the entire Sifter application and database initially ran on a single virtual server. This meant that even minor issues could impact performance or take the application offline. With customers in almost every time zone, this was unacceptable. The team’s initial objective was to improve availability, avoid downtime, and have more time and resources to enhance the application. Read More
About Customer	Next Update is a small company founded in 2008 by Garrett Dimon. The company is focused on making work less tedious and more fun. Its product, Sifter, is a SaaS-based bug and issue tracking application that simplifies the bug tracking process. The application is designed to be simple enough to be used by both technical and non-technical team members in an organization. The company believes that not all teams need the complexity inherent in larger bug tracking systems. In some cases, problems are frequently unreported in traditional systems because the logging interface and process is too imposing. Next Update’s goal is to make Sifter more accessible for wider use across companies. The company has experienced steady growth, primarily driven by word of mouth. Read More
Solution	Next Update installed New Relic, an application monitoring and management system, in 2009 to monitor their single virtual server environment with the aim of improving overall application availability. With the insight gained from New Relic, the team realized that higher availability meant moving to a more complex environment. Next Update evolved their single virtual server to seven virtual servers at Rackspace. During and after the transition, Next Update relied on New Relic Server Monitoring to monitor the application performance across the different application servers, helping them prevent any problems before they were noticeable to customers or could result in an outage. The team also used New Relic to identify and make improvements to the slowest pages during their upgrade to Rails 3 and Ruby 1.9.3. Read More Log in to view content
Contents

Technology Category

Application Infrastructure & Middleware - API Integration & Management

Applicable Industries

Software

Applicable Functions

Discrete Manufacturing

Quality Assurance

Use Cases

Predictive Maintenance

Real-Time Location System (RTLS)

Services

Software Design & Engineering Services

System Integration

Challenge

Next Update, a small company founded in 2008, developed a SaaS-based bug and issue tracking application called Sifter. The application was designed to simplify the bug tracking process and make it accessible to both technical and non-technical team members. However, the entire Sifter application and database initially ran on a single virtual server. This meant that even minor issues could impact performance or take the application offline. With customers in almost every time zone, this was unacceptable. The team’s initial objective was to improve availability, avoid downtime, and have more time and resources to enhance the application.

About Customer

Next Update is a small company founded in 2008 by Garrett Dimon. The company is focused on making work less tedious and more fun. Its product, Sifter, is a SaaS-based bug and issue tracking application that simplifies the bug tracking process. The application is designed to be simple enough to be used by both technical and non-technical team members in an organization. The company believes that not all teams need the complexity inherent in larger bug tracking systems. In some cases, problems are frequently unreported in traditional systems because the logging interface and process is too imposing. Next Update’s goal is to make Sifter more accessible for wider use across companies. The company has experienced steady growth, primarily driven by word of mouth.

Solution

Next Update installed New Relic, an application monitoring and management system, in 2009 to monitor their single virtual server environment with the aim of improving overall application availability. With the insight gained from New Relic, the team realized that higher availability meant moving to a more complex environment. Next Update evolved their single virtual server to seven virtual servers at Rackspace. During and after the transition, Next Update relied on New Relic Server Monitoring to monitor the application performance across the different application servers, helping them prevent any problems before they were noticeable to customers or could result in an outage. The team also used New Relic to identify and make improvements to the slowest pages during their upgrade to Rails 3 and Ruby 1.9.3.

Impact #1	New Relic provided the insight needed to improve overall application availability.
Impact #2	New Relic Server Monitoring helped monitor the application performance across different application servers, preventing problems before they were noticeable to customers or could result in an outage.
Impact #3	New Relic helped identify and make improvements to the slowest pages during the upgrade to Rails 3 and Ruby 1.9.3.

Impact #1

New Relic provided the insight needed to improve overall application availability.

Impact #2

New Relic Server Monitoring helped monitor the application performance across different application servers, preventing problems before they were noticeable to customers or could result in an outage.

Impact #3

New Relic helped identify and make improvements to the slowest pages during the upgrade to Rails 3 and Ruby 1.9.3.

Benefit #1	After modifying how Sifter delivered the issues page, customers experienced a 30% page performance improvement.
Benefit #2	Customers also received two times the information on each page, saving them time.

Benefit #1

After modifying how Sifter delivered the issues page, customers experienced a 30% page performance improvement.

Benefit #2

Customers also received two times the information on each page, saving them time.

Download PDF Version

Overview

New Relic supports Next Update as it expands its Sifter bug and issue tracking application and improves availability

Operational Impact

Quantitative Benefit