10.46243/jst.2022.v7.i010.pp30-34 registered
Fault Tolerance- Challenges, Techniques and Implementation in Cloud Computing
Resolves to https://www.jst.org.in/index.php/pub/article/view/875
Held by Longman Publishers (India) · prefix 10.46243 live · DOI address https://doi.org/10.46243/jst.2022.v7.i010.pp30-34
Registered 29 Sep 2026 via crossref · record version 2 · last change 29 Sep 2026, 11:59 PM · record sha256 5b2e89236c0a7fec…
Resolve ⬇ Record (JSON) ⬇ Kernel Metadata Declaration (XML) Compare with Crossref Cite (APA · BibTeX · RIS · CSL)
What the DOI identifies
JournalArticle — an article in a journal · Digital · Visual · en
Fault Tolerance- Challenges, Techniques and Implementation in Cloud Computing (PrincipalTitle)
Published 2022-12-21
Part of Journal of Science & Technology · ISSN 2456-5660 · volume 7 · issue 10 · pages 30–34
Agents
- Dr.G.Sasikanth Reddy Dr.G.Sasikanth Reddy (author)
- Longman Publishers (publisher)
Identifiers DOI 10.46243/jst.2022.v7.i010.pp30-34
Abstract
Fault tolerance is a major concern to guarantee availability and reliability of critical services as well as application execution. In order to minimize failure impact on the system and application execution, failures should be anticipated and proactively handled. Fault tolerance techniques are used to predict these failures and take an appropriate action before failures actually occur. This paperdiscusses the existing fault tolerance techniques in cloud computing based on their policies, tools used and research challenges. Cloud virtualized system architecture has been proposed. In the proposed system autonomic fault tolerance has been implemented. The experimental results demonstrate that the proposed system can deal with varioussoftware faults for server applications in a cloud virtualizedenvironment.
System metadata — ISO 26324:2025, Annex B · DOI Handbook 10.1
Each element by the standard's name (Annex B: reference elements, then administrative) and the Handbook's (in grey), read off the record above.
| Element | Value | In the record |
|---|---|---|
| DOI Name DOI name | 10.46243/jst.2022.v7.i010.pp30-34 | doi |
| Referent Type referentType | Creation | referent |
| Referent Sub-Type referentSubType | JournalArticle — an article in a journal | type |
| Referent Name(s) referentName(s) | Fault Tolerance- Challenges, Techniques and Implementation in Cloud Computing (PrincipalTitle, en) | titles |
| Basic Metadata basicMetadata | author: Dr.G.Sasikanth Reddy Dr.G.Sasikanth Reddy publisher: Longman Publishers published: 2022-12-21 part of: Journal of Science & Technology · ISSN 2456-5660 · vol. 7 · no. 10 · pp. 30–34 language: en form: Digital · Visual · Language | agents, dates, container, language, structural_type, modes, characters |
| Referent Identifier(s) alternateIdentifier(s) | none besides the DOI | identifiers, relations (IsSameAs) |
| Registration Authority registrationAuthorityCode | Crossref — issued by Crossref (member 25296); held here as a copy | record.source_agency (our code, ra_doi_name, for names issued here once appointed) |
| Created Date issueDate | 2024-02-16 | record.registered (when the DOI name was first registered) |
| relatedIdentifiers | none needed — the descriptive metadata is in this record | container, relations (only where the descriptive metadata lives at another identifier) |
complete Every System Metadata element is here, with the basic metadata a journal article needs.
The System Metadata Declaration (JSON) · the Kernel Metadata Declaration (XML) · what each sub-type needs
History — the ledger
Every change to this DOI, in order, as it was recorded. Entries are only ever added, never changed or removed.
| # | When | What | By | Changes |
|---|---|---|---|---|
| 1 | 29 Sep 2026, 10:00 PM | register registered at Crossref; record read from api.crossref.org | Administrator (admin) | 223 fields set · sha256 21204bab58e1… |
| 2 | 29 Sep 2026, 11:59 PM | update record re-read from api.crossref.org | Administrator (admin) | abstract.value: container.titles.0.value: |
Machine-readable: the history as JSON, with the full record after each change.
