Quantum computing has rapidly become a matter of major importance for technology experts and business leaders alike. What’s responsible for this surge in momentum, and just how quickly do Retail organisations need to start preparing for a quantum future? In the first of a three-part series, dunnhumby Data Scientists Ross Williams and David Hoyle set out to shed more light on the issue.
Like many technologies, quantum computing (QC) is something that goes back much further than we might expect. Just as the origins of the internet stretch back many decades before it entered the wider public consciousness, QC can be traced back to the 1980’s, when the conceptual foundations of the field were conceived.
The exact nature of QC and how it works is something that we explore in the next post in this series. For now, if you’re not familiar with the concept of a quantum computer, there are several things to bear in mind.
Firstly, quantum computers aren’t “better” regular computers – they’re dramatically different systems that excel at solving very specific problems. The reason for that superior performance lies in the fact that these machines utilise some of the strange behaviours demonstrated by quantum particles as part of their information processing capabilities. What this results in is a computer that is almost purpose-built for the express intention of tackling exponentially large mathematical calculations that traditional machines would struggle with.
If you’ve begun to hear more about QC over the past few years – or, indeed, have only just discovered that it exists – you’re not alone. There has been a recent marked increase in interest in QC amongst the tech community and investors. Six years ago private investment into the QC space was essentially non-existent. Today, multiple startups have raised hundreds of millions of dollars of venture capital each. What then, is driving this newfound fixation?
One of the most likely answers is the (relatively) recent launch, and continued growth, of Quantum-as-a-Service (QaaS). QaaS essentially allows commercial entities to “lease” time on a quantum machine, paying for access through the cloud rather than investing in their own dedicated quantum computer. Vendors include Amazon (Braket), Microsoft (Azure Quantum), Google (Quantum Computing Service), and IBM (Quantum Services). The latter of these led the way in the QaaS market, launching the first cloud-based offering in the form of the IBM Quantum Experience in 2016.
With a growing number of big name companies joining the QaaS charge, a virtuous circle is likely to begin building around the market. As QaaS proliferates and becomes easier to access, investment is likely to flood in as a result. Some of that will go to smaller providers and start-ups who can help to improve both the hardware and software that underpins the QaaS market. With performance rising as a result, demand will continue to grow.
That’s what should happen in theory, at least. Real progress in QC will of course depend on its ability to deliver results for the companies that choose to venture into this nascent field.
So when will this day arrive? The honest answer, today at least, is that we’re not entirely sure. While use cases and practical applications for quantum do continue to develop – something we’ll discuss in our next post in this series – we’re still some way away from a world in which the average company can tap into QC and expect to achieve overnight advantage. Retailers shouldn’t be expecting to magically discover a new way of routing their delivery fleet simply by throwing QC at the problem. Not yet, at least.
If quantum isn’t yet at the stage at which commercial companies can easily derive clear value from it, then, just how seriously should we be taking it? The answer, vague though it may be, is that your mileage is likely to vary. As with any emerging technology, there is a risk of buying in too early, only to find that many of the promises made go unfulfilled. On the other hand, given the complex subject matter, first-mover advantage will be particularly strong for QC, and getting ahead of the game can have a transformative effect.
At this stage, the best advice that we can give to any Retailer is to have a clear understanding of the potential of QC. Retailers are no strangers to cutting-edge data science, and the prospect of a platform that can tackle challenging calculations should be immediately appealing. As that virtuous circle that we mentioned earlier continues to gather pace, the odds that some forward-thinking start-up develops a killer QC app for Retail will continue to shrink, too.
Now is the time for Retailers to be in learning and exploration mode, and our report on quantum computing will help you get started. As with any new technology, the focus must be on what it can help you achieve, not how powerful it is. Don’t jump on the bandwagon simply because it’s there; do so because you know exactly where you want it to take you.
If this post sounds at all pessimistic, we’d ask you to substitute that sensation for one that’s a touch closer to realistic. QC is a hugely exciting field, and one that dunnhumby is already exploring in earnest. In the next post in this series, we’ll be looking at some of the ways in which QC could be applied to commercial challenges, and the current “state of the possible”.
This blog discusses themes covered in greater depth in our new report on quantum computing: “Demystifying quantum computing for commercial companies.” Download a complimentary copy of the report here.
Cookie | Description |
---|---|
cli_user_preference | The cookie is set by the GDPR Cookie Consent plugin and is used to store the yes/no selection the consent given for cookie usage. It does not store any personal data. |
cookielawinfo-checkbox-advertisement | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
cookielawinfo-checkbox-analytics | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Analytics" category . |
cookielawinfo-checkbox-necessary | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
CookieLawInfoConsent | The cookie is set by the GDPR Cookie Consent plugin and is used to store the summary of the consent given for cookie usage. It does not store any personal data. |
viewed_cookie_policy | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
wsaffinity | Set by the dunnhumby website, that allows all subsequent traffic and requests from an initial client session to be passed to the same server in the pool. Session affinity is also referred to as session persistence, server affinity, server persistence, or server sticky. |
Cookie | Description |
---|---|
wordpress_test_cookie | WordPress cookie to read if cookies can be placed, and lasts for the session. |
wp_lang | This cookie is used to remember the language chosen by the user while browsing. |
Cookie | Description |
---|---|
CONSENT | YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data. |
vuid | Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos to the website. |
_ga | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognise unique visitors. |
_gat_gtag_UA_* | This cookie is installed by Google Analytics to store the website's unique user ID. |
_ga_* | Set by Google Analytics to persist session state. |
_gid | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
_hjSessionUser_{site_id} | This cookie is set by the provider Hotjar to store a unique user ID for session tracking and analytics purposes. |
_hjSession_{site_id} | This cookie is set by the provider Hotjar to store a unique session ID, enabling session recording and behavior analysis. |
_hp2_id_* | This cookie is set by the provider Hotjar to store a unique visitor identifier for tracking user behavior and session information. |
_hp2_props.* | This cookie is set by the provider Hotjar to store user properties and session information for behavior analysis and insights. |
_hp2_ses_props.* | This cookie is set by the provider Hotjar to store session-specific properties and data for tracking user behavior during a session. |
_lfa | This cookie is set by the provider Leadfeeder to identify the IP address of devices visiting the website, in order to retarget multiple users routing from the same IP address. |
Cookie | Description |
---|---|
aam_uuid | Set by LinkedIn, for ID sync for Adobe Audience Manager. |
AEC | Set by Google, ‘AEC’ cookies ensure that requests within a browsing session are made by the user, and not by other sites. These cookies prevent malicious sites from acting on behalf of a user without that user’s knowledge. |
AMCVS_14215E3D5995C57C0A495C55%40AdobeOrg | Set by LinkedIn, indicates the start of a session for Adobe Experience Cloud. |
AMCV_14215E3D5995C57C0A495C55%40AdobeOrg | Set by LinkedIn, Unique Identifier for Adobe Experience Cloud. |
AnalyticsSyncHistory | Set by LinkedIn, used to store information about the time a sync with the lms_analytics cookie took place for users in the Designated Countries (which LinkedIn determines as European Union (EU), European Economic Area (EEA), and Switzerland). |
bcookie | LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognise browser ID. |
bscookie | LinkedIn sets this cookie to store performed actions on the website. |
DV | Set by Google, used for the purpose of targeted advertising, to collect information about how visitors use our site. |
ELOQUA | This cookie is set by Eloqua Marketing Automation Tool. It contains a unique identifier to recognise returning visitors and track their visit data across multiple visits and multiple OpenText Websites. This data is logged in pseudonymised form, unless a visitor provides us with their personal data through creating a profile, such as when signing up for events or for downloading information that is not available to the public. |
gpv_pn | Set by LinkedIn, used to retain and fetch previous page visited in Adobe Analytics. |
lang | Session-based cookie, set by LinkedIn, used to set default locale/language. |
lidc | LinkedIn sets the lidc cookie to facilitate data center selection. |
lidc | Set by LinkedIn, used for routing from Share buttons and ad tags. |
li_gc | Set by LinkedIn to store consent of guests regarding the use of cookies for non-essential purposes. |
li_sugr | Set by LinkedIn, used to make a probabilistic match of a user's identity outside the Designated Countries (which LinkedIn determines as European Union (EU), European Economic Area (EEA), and Switzerland). |
lms_analytics | Set by LinkedIn to identify LinkedIn Members in the Designated Countries (which LinkedIn determines as European Union (EU), European Economic Area (EEA), and Switzerland) for analytics. |
NID | Set by Google, registers a unique ID that identifies a returning user’s device. The ID is used for targeted ads. |
OGP / OGPC | Set by Google, cookie enables the functionality of Google Maps. |
OTZ | Set by Google, used to support Google’s advertising services. This cookie is used by Google Analytics to provide an analysis of website visitors in aggregate. |
s_cc | Set by LinkedIn, used to determine if cookies are enabled for Adobe Analytics. |
s_ips | Set by LinkedIn, tracks percent of page viewed. |
s_plt | Set by LinkedIn, this cookie tracks the time that the previous page took to load. |
s_pltp | Set by LinkedIn, this cookie provides page name value (URL) for use by Adobe Analytics. |
s_ppv | Set by LinkedIn, used by Adobe Analytics to retain and fetch what percentage of a page was viewed. |
s_sq | Set by LinkedIn, used to store information about the previous link that was clicked on by the user by Adobe Analytics. |
s_tp | Set by LinkedIn, this cookie measures a visitor’s scroll activity to see how much of a page they view before moving on to another page. |
s_tslv | Set by LinkedIn, used to retain and fetch time since last visit in Adobe Analytics. |
test_cookie | Set by doubleclick.net (part of Google), the purpose of the cookie is to determine if the users' browser supports cookies. |
U | Set by LinkedIn, Browser Identifier for users outside the Designated Countries (which LinkedIn determines as European Union (EU), European Economic Area (EEA), and Switzerland). |
UserMatchHistory | LinkedIn sets this cookie for LinkedIn Ads ID syncing. |
UserMatchHistory | This cookie is used by LinkedIn Ads to help dunnhumby measure advertising performance. More information can be found in their cookie policy. |
VISITOR_INFO1_LIVE | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. |
YSC | YSC cookie is set by YouTube and is used to track the views of embedded videos on YouTube pages. |
yt-remote-connected-devices | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt-remote-device-id | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
yt.innertube::nextId | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |
yt.innertube::requests | This cookie, set by YouTube, registers a unique ID to store data on what videos from YouTube the user has seen. |
_gcl_au | Set by Google Analytics, to take information in advert clicks and store it in a 1st party cookie so that conversions can be attributed outside of the landing page. |