Please wait while flipbook is loading. For more related info, FAQs and issues please refer to DearFlip WordPress Flipbook Plugin Help documentation.
Businesses face increasing pressure to stay relevant and competitive, mainly driven by the consumers that they serve.
Customers expect your business to be available, at any time and from anywhere. This expectation of accessibility and on-demand consumerism is driving change in eCommerce.
TrafficDefender, powered by Netacea, was founded on the principle that for many business, technical ability and performance mark the difference between success and failure. That’s why we seek to meet the world’s demand for scalable technology with our virtual waiting room.
TrafficDefender’s founders designed and implemented several bespoke online waiting systems for high demand retail and ticketing organizations, before productizing their unique approach to providing a world-leading, non-bypassable, secure queuing solution.
Foreword Our adaptive API architecture supports a wide range of infrastructure from leading product vendors, allowing you to integrate our machine learning risk reduction into your existing platform of choice.
The adaptive data model and micro-services API approach gives huge power and flexibility to ensure that even the most complex of visitor requirements can be elegantly and reliable handled at volume, using the existing infrastructure that enterprise customers already maintain and own.
We complement existing controls such as WAF rulesets, rate limiting and threat databases, to provide deep analysis of all website visitors., through a practical use of A.I. to understand human and bot behaviours and adjust their website journey in real-time.
Any design decision must deliver both core requirements for a successful virtual
waiting room, the queue must be:
TrafficDefender works with some of the world’s largest eCommerce organizations and is well-equipped to help businesses prepare for surges in online traffic, while being your first line of defence against malicious bots.
The cloud-hosted Virtual Waiting Room operates at a DNS level and is implemented in front of your web-based application where it manages all incoming traffic therefore covering all aspects of the web application infrastructure, not just specific pages.
Using DNS enables an easy and rapid implementation as it does not require any code changes to the website. By utilising a single redirection, TrafficDefender covers all aspects of the web infrastructure, enabling larger enterprise customers to deploy to 10,000’s of sites in a single implementation.
As with any enterprise-class solution, the Virtual Waiting Room is not only secure, it’s completely scalable. Any requests that pass through the system are HTTPS encrypted and never stored, enabling us to be PCI compliant.
The solution is hosted on highly available, distributed cloud infrastructure (with complete fail overprotective) this has enabled it to achieve 100% availability since inception in 2014 and has been load tested to over 1 million concurrent users with no performance degradation.
Sitting in front of the infrastructure allows the Virtual Waiting Room to provide additional protection for load balancers, Web Application Firewalls (WAFs) and app and database servers; not just the website. Inspecting all requests that pass in and out of the webserver ensures full visibility and control of all traffic and therefore ensures an accurate number of visitors on any part of a site at any one time.
Only a DNS based approach will ensure full visibility and control of all traffic. All requests passing in and out of the system are inspected, enabling an accurate number of visitors on any part of the site at any one time
Being in-line at a DNS level improves security by allowing you to restrict access to your system to only the IP addresses of the TrafficDefender platform. This means that no one can bypass the Virtual Waiting Room.
By positioning the solution in the cloud in front the infrastructure you can provide protection for load balancers, WAFs, application and database servers, not just the website.
In-line DNS integrates as a seamless layer into the customers purchasing journey. Our customers do not have to worry about their buyers becoming suspicious of being directed to external URLs, e.g. www.VirtualWaitingRoom.CustomerWebsiteName.com
DNS does not require any code changes to the website, a single redirection covers all aspects of the web infrastructure, enabling our larger customers to deploy to 10,000’s sites in a single, rapid implementation.
Requests pass through the solution as encrypted HTTPS traffic, but are not stored, enabling the solution to be both PCI and GDPR compliant.
Hosting the solution on a highly available, distributed cloud infrastructure with complete fail over protection has enabled a DNS solution to achieve 100% availability since inception.
The ability to whitelist specific users or locations ensures that no in-store or call centre employee is placed within a waiting room when trying to place a customer order or access stocking information.
Returning or high-spend customers can be rewarded with guaranteed direct access to the website in any given situation, rewarding those loyal to your business.
The DNS based solution, combined with TrafficDefender’s passive mode functionality, allows for the Virtual Waiting Room to be instantly added or removed to your website at the click of a button.
Proven to perform all interactions sub 1ms in front of some of the world’s busiest websites
Further to customer reports, DNS solutions have been load tested to over 2 million concurrent users with no sign of performance degradation or instability.
While this is a perfectly valid way to establish if a waiting room is needed, there are some fundamental flaws with this methodology:
In the event of a flash sale or a huge spike in traffic, the webservers could very easily buckle under the load before the client-side scripts have chance to execute and the users re-directed to the waiting room page.
By design, CDNs are distributed systems and, because of this, they cannot offer a unified view of the current user levels on a system or manage a potential waiting room scenario fairly.
Virtual waiting rooms based in the CDN layer tend to use a “next returning user” rather than a “first in, first out” approach to processing waiting users. Meaning, unfortunately, that the first person in the queue isn’t always the first person out of it and onto the website.
CDN based virtual waiting rooms do not use a fixed waiting room threshold, instead they use a percentage ruleset whereby a set percentage of traffic is always re-directed to a waiting room regardless of the visitor numbers. The result of this approach is that as the amount of traffic hitting your website increases, so does the amount of traffic that hits your webserver. In other words, the amount of traffic being allowed to hit your site is flexible depending on load whereas your servers have a fixed capacity regardless of load.
The upshot of this is that in the case of a traffic spike, an administrator would need to constantly monitor and (where necessary) reduce the percentage of traffic allowed though to the website during peak loads, and then continue monitoring to increase that percentage again when the amount of traffic reduces.
Configuring your web application(s) and/or load balancers to deal with a waiting room scenario can potentially yield mixed results. Issues will more than likely still occur as all traffic is hitting your existing infrastructure without the flow control at the perimeter, that a DNS-based solution would provide.
By implementing the virtual waiting room in this manner, it’s all too common for the solution to end up behind the bottleneck(s) that are causing the problem and will therefore compound the issue, without solving the problem.
With in-house implementations differing in customisation and configuration, a larger amount of time and resources will be required. For example, website owners will need to manage additional failure points within the deployment increasing risk, therefore adding more complexity than is necessary and reduces the overall effectiveness of the solution.
It has never been more important to ensure 100% website availability. In a digital world of streaming, consumers are accustomed to gaining access to information, entertainment and items of desire in near real time. Failure to provide immediate access to website shops, limited edition product ranges and discounted sales events can be detrimental to brand reputation and repeat custom.
Even a one-second delay in load time can result in a 7% loss in conversions and a two-second delay during a transaction results in shopping cart abandonment rates of up to 87% as customers fear something has gone wrong with the transaction and abandon their purchase. It is vital that your virtual waiting room solution makes the waiting process as fair, transparent and pain-free as possible.
Selecting a proven, scalable virtual waiting room solution will protect the uptime, availability and performance of web applications. Therefore, maximizing customer transactions and safeguarding brand reputation through customisable access rules during spikes in traffic.
When the maximum number of visitors is reached, TrafficDefender delivers a waiting page to all additional visitors without any access to your servers. Your servers only ever see visitors that you know they can handle so the TrafficDefender’s Virtual Waiting Room offers genuine protection for your servers and quality of service to your site visitors.
TrafficDefender’s Virtual Waiting Room solution controls the flow of website visitors allowing through only the visitors your website can handle. By putting all additional visitors into a fair, first-in-first-out waiting room we ensure that all visitors get the best possible experience and you make the most money.
In short, TrafficDefender’s Virtual Waiting Room ensures that your site remains available 24/7 no matter how busy it gets.
Try TrafficDefender today and see the virtual waiting room in action.