Return to Newsletters

Exigo has made open system communication infrastructure more efficient by modifying its API format to update connections, making them faster and more secure. We have empowered our clients by allowing them to create a single API that helps determine a direct path for their secure connections. BGP pathing has been a point of interest among our clients that require speed and accuracy when dealing with actionable data. BGP pathing can inherently create multiple pathways to the same location, but we created a singular API key for our clients so that BGP pathing can become pinpoint accurate and less adaptive when choosing the end location. By filtering out routes that take longer to connect to, we allow our customers the ability to connect to the fastest route possible.

1. API Format Change

Historically, everyone has gone to our API prefix: api.exigo.com as our single API source. Globally, all the webmasters have programmed to that endpoint. We are changing it to have the company key before that so it would be: company.api which allows us to route specifically on a per-company basis. This provides us important information such as the nationality of the company so we can increase route speed. This can significantly increase performance for the company, especially for our international clients. We can select preferred networks that will offer the best performance to each client.

2. API Count

A lot of companies throw together sites without thinking through the architecture or adding caching. Their developers might make hundreds of calls on a single page that needs to be consolidated down to one. We are trying to educate and train on best practices and think through how often they hit the API. We put fairly high caps where it would be difficult to hit them unless your site is not optimized. We don’t want to be sustaining billions of hits for poorly written code.

3. SQL Server 2016

We have updated to SQL Server 2016 Enterprise Edition. This new edition has added several performance enhancements to features including Column Store Indexes and In-Memory OLTP. Those two features were first introduced in SQL 2014 Enterprise, but did not perform well. Microsoft improved these features with this update and we encourage all of our clients to upgrade to SQL Server 2016 Enterprise so they can also take advantage of the new features.

More on SQL Server 2016 Enterprise features and benefits

Return to Newsletters