1 / 6

Slow ServiceNow Instance Performance Could be Due to Over-Customization

Slow ServiceNow instance performance is a thorn in many organizationu2019s IT service management (ITSM) strategies. Poor ServiceNow performance can cause bottlenecks that impede an organizationu2019s scalability.<br><br>A leader among ITSM vendors, ServiceNow is a highly customizable tool u2013 a key factor driving its popularity. Organizations can tailor the tool to meet their specific demands, adding custom functionality via custom-built code, applications and APIs.<br><br>However, customization u2013 or rather, over-customization u2013 is often at the heart of slow ServiceNow instance performance.

Enoch9
Download Presentation

Slow ServiceNow Instance Performance Could be Due to Over-Customization

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Slow ServiceNow Instance Performance Could be Due to Over-Customization

  2. Slow ServiceNow instance performance is a thorn in many organization’s IT service management (ITSM) strategies. Poor ServiceNow performance can cause bottlenecks that impede an organization’s scalability. A leader among ITSM vendors, ServiceNow is a highly customizable tool – a key factor driving its popularity. Organizations can tailor the tool to meet their specific demands, adding custom functionality via custom-built code, applications and APIs. However, customization – or rather, over-customization – is often at the heart of slow ServiceNow instance performance.

  3. ServiceNow Customization – Don’t Overdo It • As organizations add more and more custom functionality, ServiceNow instances become increasingly difficult to manage. • In the case of upgrades or implementing new features, organizations need to extend resources to ensure the custom functionality remains compatible. When the resources required are sourced internally, this can delay time-to-value as DIY ServiceNow integrations take, on average, 470 hours. When sourced externally, the burden of cost is financial. • Additionally, custom integrations can have a direct impact on ServiceNow performance. Organizations are often tempted into the DIY approach to building custom integrations, particularly for integrations that transfer limited amounts of data. • The DIY approach uses web services to connect ServiceNow to other apps. The web services and the channels ServiceNow users operate within shared, and limited bandwidth. • As organizations and their data volumes scale, they increase the potential for limited bandwidth leading to slow ServiceNow instance performance and impacting queries.

  4. Slow ServiceNow Performance and Technical Debt • The negative effects of the customization outlined above are often referred to as “technical debt”. One of the many hidden costs associated with DIY ServiceNow integrations. • An awareness of the hidden costs of DIY ServiceNow Integrations is a best practice for anybody managing a ServiceNow instance. • If you’d like more help understanding the hidden costs of DIY ServiceNow integrations, get the “Integration Total Cost of Ownership Toolkit”. • ‘Technical debt’, is an apt term, as organizations often fall into the pitfalls of technical debt by trying to save costs up front. The cost of slow ServiceNow instance performance is difficult to quantify. Many organizations that opt for the custom/web services approach end up out-growing their custom solution. • So if your organization is experiencing slow ServiceNow instance performance, and you are running custom-built code, applications and APIs, the root of the problem is likely technical debt.

  5. Slow ServiceNow Performance and Technical Debt So if your organization is experiencing slow ServiceNow instance performance, and you are running custom-built code, applications and APIs, the root of the problem is likely technical debt. “When we integrated ServiceNow we used an open source tool […] and that worked okay for a while. But those ETLs put a lot of stress on ServiceNow,” explained Paul Liesse – Supervisor, Managed Service Applications, CDW. “We did find another commercial product but it was also web-based. It had a lot of the features we were unable to implement [before …], but eventually we ran into the same issues,” Liesse continued. “Anybody who’s tried to do bulk web-services against ServiceNow knows that at some point you’re going to run into a scalability issue.” The issue CDW experienced is far from unique. ServiceNow themselves are aware of the impact web services can have on the solution, with Venu Malyala – Senior Director of BI, MDM & Analytics, ServiceNow – stating “most of the ETL tools in the market leverage web services, which adds a lot of load to the system.” Despite the prevalence of the issue, there is a solution …

  6. Contact Us Location: 10801 N Mopac Expressway, Building 1, Suite 100, Austin, TX 78759 Contact: +1 888 620 8880 E-mail: info@perspectium.com More information about the topic visit https://www.perspectium.com/blog/slow-servicenow-customization/

More Related