Review of deep learning: concepts, CNN architectures, challenges, applications, future directions
In the last few years, the deep learning (DL) computing paradigm has been deemed the Gold Standard in the machine learning (ML) community. Moreover, it has gradually become the most widely used computational approach in the field of ML, thus achieving outstanding results on several complex cognitive tasks, matching or even beating those provided by human performance. One of the benefits of DL is the ability to learn massive amounts of data. The DL field has grown fast in the last few years and it has been extensively used to successfully address a wide range of traditional applications. More importantly, DL has outperformed well-known ML techniques in many domains, e.g., cybersecurity, natural language processing, bioinformatics, robotics and control, and medical information processing, among many others. Despite it has been contributed several works reviewing the State-of-the-Art on …
More importantly, DL has outperformed well-known ML techniques in many domains, e.g., cybersecurity, natural language processing, bioinformatics, robotics and control, and medical information processing, among many others.
Historical research candidate. An editor must verify study design, population, effect size, and whether later evidence changes the reading before publication.
Evidence
- Peer-reviewedJournal of Big Data2021-03-31
- Peer-reviewedSoftware2025-06-28
- Peer-reviewedApplied Sciences2025-04-02
- Peer-reviewedArtificial Intelligence Review2023-04-17
Truvace Impact Record TRV-2026-0048, v5: “Review of deep learning: concepts, CNN architectures, challenges, applications, future directions.” Truvace, 2026-07-12. /record/TRV-2026-0048 (accessed at citation time). sha256 928a97b4cda9f867…
Calibration history
Every change to this record since certification, in the open.
Retracted from the live record
Source set updated
Source set updated
Source set updated
Certified into the record
How to verify without trusting this page
Fetch the canonical text of any version from /api/record/TRV-2026-0048 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.