In this final post in our series investigating the growing importance of quantum computing, dunnhumby Data Scientists David Hoyle and Ross Williams look to the future and share their views on how the events of the next few years will influence how commercial organisations can capitalise on the quantum revolution.
Throughout the previous posts (here and here) in this series, we’ve been keen to point out some of the current limitations that hamper quantum computing’s (QC) ability to tackle the commercial challenges that organisations face today. While a huge amount of progress has been made, particularly in the past few years, we aren’t yet at the point at which the average business can easily capitalise on the inherent potential of quantum computing.
What exactly needs to change, then, to get us past that hurdle? And just how far away are we from a future in which QC is a ubiquitous tool?
While it isn’t possible to answer either of these questions without resorting to some degree of speculation, we can at least make some educated guesses based on the current trajectory of development. There are five key areas to focus on when considering the point at which QC becomes a genuinely viable commercial tool.
These are:
Here are our thoughts on the developments that we’ll see in each of those fields in the near future.
Hardware: Advances will be driven by QaaS and external investment
Stating that we expect investors to flock around quantum startups that have partnered with the likes of Amazon and Microsoft, probably isn’t going to surprise too many people. It remains an important point to make however, since that investment is likely to drive the hardware improvements necessary to increase the computational power on offer to QaaS customers.
As that investment continues, we’re likely to see significant advances in both the qubit capacity of QaaS machines and a reduction in the noise afflicting those computers.
Software: More developers means faster progress
While the creation of quantum hardware is likely to remain exclusive to a select group of well-resourced tech giants and startups, software development has a much lower barrier to entry. As a result, and as the QaaS market continues to expand, we expect that we’ll see continued growth in the numbers of start-up companies specialising in QC software solutions.
The most important aspect of this trend is that it will likely lead to the creation of a greater number of high-level language abstractions. Compared with fine-grained controls, these tend to reduce the level of skill required to operate a quantum computer, ensuring that QC can be exploited by a wider audience than just highly-trained specialists.
Algorithms: Applications to practical problems will drive development
Today, many QC solutions draw from a relatively small pool of algorithms. Because new algorithms have traditionally emerged at a slow pace, it is likely that QC will continue to rely on these core methods for the foreseeable future.
What is likely to change is that these algorithms will be applied to more realistic and challenging problems. As this happens, we’ll see a gradual revolution in QC’s ability to tackle issues that are much closer to those faced by commercial entities. This will in turn bridge the gap between theoretical possibility and practical application.
Applications: As the industry learns “what works”, QC application will broaden
As with any developing technology, much of the discourse around QC tends to be filled with unrealistic ideas about its potential. That hype is likely to dwindle over the next few years, leaving us with a much more realistic picture of what quantum computers can actually accomplish.
On the road to this more pragmatic future, one of the things that we are likely to develop is a more nuanced understanding of the application of QC to commercial optimisation problems. This will enable us to tackle a wider range of operational challenges, broadening the potential appeal of QC.
QaaS: Growing adoption will fuel further advances
In many ways, progress in this fifth area is dependent largely on some of the above predictions coming to fruition. If investment slows and development falters, QaaS will clearly end up on a longer path towards widespread commercial adoption.
Theoretically, though, as QaaS-based QC becomes more relevant, effective, and easy-to-use, a growing number of corporate users should be drawn to the technology. A key turning point to look out for will be if and when users are able to integrate quantum solutions into a wider workflow. This will require and drive enhancements in the capacity, stability, and performance of QaaS.
As with QC as a whole, though, the real test for QaaS will come in its ability to combine ease of use with real, near-term competitive advantage for commercial customers.
All of this is, of course, merely speculative analysis. One thing that is particularly important to bear in mind is that while we believe that many of the possibilities outlined above will come to pass within the next three to five years, there is no guaranteed timeline for QC.
However, the promise of a paradigm shift in computation tomorrow requires a shift in your organisation’s mindset and capabilities today. It is an exciting time to embrace quantum computing.
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 |
---|---|
passster | Set by Passster to remember that a visitor has entered a correct password, so they don’t have to re-enter it across protected pages. |
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 |
---|---|
fs_cid | Set by FullStory to correlate sessions for diagnostics and session consistency; not always set. |
fs_lua | Set by FullStory to record the time of the user’s last activity, helping manage session timeouts. |
fs_session | Set by FullStory to manage session flow and recording. Not always visible or applicable across all implementations. |
fs_uid | Set by FullStory to uniquely identify a user’s browser. Used for session replay and user analytics. Does not contain personal data directly. |
VISITOR_INFO1_LIVE | Set by YouTube to estimate user bandwidth and improve video quality by adjusting playback speed. |
VISITOR_PRIVACY_METADATA | Set by YouTube to store privacy preferences and metadata related to user consent and settings. |
vuid | Vimeo installs this cookie to collect tracking information by setting a unique ID to embed videos to the website. |
YSC | Set by YouTube to track user sessions and maintain video playback state during a browser session. |
_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. |
_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. |
_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. |
__Secure-ROLLOUT_TOKEN | YouTube sets this cookie via embedded videos to manage feature rollouts. |
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 | Set by LinkedIn, used for routing from Share buttons and ad tags. |
lidc | LinkedIn sets the lidc cookie to facilitate data center selection. |
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. |
yt-remote-connected-devices | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
_gcl_au | Set by Google Tag Manager to store and track conversion events. It is typically associated with Google Ads, but may be set even if no active ad campaigns are running, especially when GTM is configured with default settings. The cookie helps measure the effectiveness of ad clicks in relation to site actions. |