New Relic supports Next Update as it expands its Sifter bug and issue tracking application and improves availability
公司规模
Startup
地区
- America
国家
- United States
产品
- Sifter
- New Relic
技术栈
- Ruby
- Rails3
- MySQL
- Sphinx
实施规模
- Enterprise-wide Deployment
影响指标
- Productivity Improvements
- Customer Satisfaction
技术
- 应用基础设施与中间件 - API 集成与管理
适用行业
- Software
适用功能
- 离散制造
- 质量保证
用例
- 预测性维护
- 实时定位系统 (RTLS)
服务
- 软件设计与工程服务
- 系统集成
关于客户
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.
挑战
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.
解决方案
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.
运营影响
数量效益
Case Study missing?
Start adding your own!
Register with your work email and create a new case study profile for your business.
相关案例.
Case Study
Infosys achieves a 5–7 percent effort reduction across projects
Infosys, a global leader in consulting, technology, and outsourcing solutions, was facing significant challenges in application development and maintenance due to its distributed teams, changing business priorities and the need to stay in alignment with customer needs. The company used a mix of open source, home-grown and third-party applications to support application development projects. However, challenges resulting from distributed teams using manual processes increased as the company grew. It became more and more important for Infosys to execute its projects efficiently, so they could improve quality, reduce defects and minimize delays.
Case Study
Arctic Wolf Envelops Teamworks with 24x7 Cybersecurity Protection and Comprehensive Visibility
Teamworks, a leading athlete engagement platform, faced rising cyberthreats and needed enhanced visibility into its network, servers, and laptops. With software developers connecting from all over the world, the company sought to improve its security posture and position itself for future growth. The company had a secure platform but recognized the need for a more proactive solution to identify gaps within its technology infrastructure. Data exfiltration and malicious access were top concerns, prompting the need for a comprehensive security upgrade.
Case Study
Sawback IT and Datto Save Client From a Costly Mistake
Ballistic Echo, a software development house, faced a critical challenge when human error led to the deletion of thousands of lines of unique code. This incident occurred before the code was pushed to source control, resulting in significant loss of time, revenue, and work. The previous file-level backup solution they used was slow and inefficient, making it nearly impossible to manually recreate the lost work. The need for a more reliable and efficient business continuity solution became evident to avoid such disasters in the future.
Case Study
Opal Helps Customers Shine Thanks to Datto
SP Flooring & Design Center faced a ransomware attack that encrypted and locked their files. The attack was initiated through a compromised service account set up by an outside vendor. The ransomware infection was isolated quickly, but there was a concern about the extent of the data at risk. The company had backups in place but was unsure of how much information was compromised. The situation required immediate action to prevent further damage and restore the affected data.
Case Study
Zapier Aggregates Multiple Analytics in a Single Dashboard with the New Relic Platform
Zapier, a company that enables non-technical users to push data between hundreds of web applications, was facing a challenge in automating and provisioning servers for optimal performance. The company's environment consisted of 50 Linux servers on the Amazon Elastic Compute Cloud (EC2), a Django application split across several servers, and a backend consisting of a dynamic number of celery task workers fed by messages published to a RabbitMQ cluster. They also maintained a number of internal web services on nginx in front of Gunicorn and Node.js processes. Redis handled simple key and value stores, with logging handled by Graylog2 and ElasticSearch. However, they realized that no level of automation would be sufficient without an effective monitoring solution in place. They needed a tool that could provide immediate alerts when something was breaking and could be easily implemented into their environment.
Case Study
Pipeline Insight Case Study: YARCDATA
YarcData faced challenges in determining the conversion rates of prospects into customers through various marketing efforts and identifying the source of its leads. They wanted to know the percentage of opportunities in the sales pipeline that came from different marketing events, web downloads, or self-sourced sales opportunities. Additionally, they needed the ability to drill down into the data to guide where to allocate more marketing dollars based on the success of previous efforts. Previously, YarcData relied heavily on spreadsheets and Salesforce.com reports, which made it difficult to extract the exact information they needed. This reliance on spreadsheets represented about 70% of their data presentation.
