Display Settings:

Format

Send to:

Choose Destination
We are sorry, but NCBI web applications do not support your browser and may not function properly. More information
Curr Alzheimer Res. 2012 Feb;9(2):165-77.

Alpha-secretase cleavage of the amyloid precursor protein: proteolysis regulated by signaling pathways and protein trafficking.

Author information

  • DZNE - German Center for Neurodegenerative Diseases, 80336 Munich, Germany. stefan.lichtenthaler@med.uni-muenchen.de

Abstract

α-secretase is the name for a metalloprotease activity, which is assumed to play a key role in the prevention of the molecular mechanisms underlying Alzheimer's disease (AD). Proteases similar to α-secretase are essential for a wide range of biological processes, such as cell adhesion and embryonic development. The molecular culprit in AD is the amyloid β peptide (Aβ), which derives from the amyloid precursor protein (APP) through sequential cleavage by the two proteases β- and γ-secretase. In contrast, α-secretase, which is the metalloprotease ADAM10, cleaves APP within the Aβ domain, thus preventing Aβ generation. Additionally, it produces a secreted APP ectodomain with neurotrophic and neuroprotective properties. An increase in α-secretase cleavage is considered a therapeutic approach for AD, but the molecular mechanisms regulating α-secretase cleavage are only partly known. Protein kinase C and mitogen-activated protein kinase constitute central signaling hubs for the regulation of α-secretase cleavage. Additionally, recent studies increasingly demonstrate that the correct spatial and temporal localization of the two membrane proteins APP and α-secretase is essential for efficient α-secretase cleavage of APP. This review highlights the role of signaling pathways and protein trafficking in the control of APP α-secretase cleavage.

PMID:
21605033
[PubMed - indexed for MEDLINE]
PubMed Commons home

PubMed Commons

0 comments
How to join PubMed Commons

    Supplemental Content

    Icon for Bentham Science Publishers Ltd.
    Loading ...
    Write to the Help Desk