Comparing redundancy models for high availability middleware
Abstract Highly available systems are fault tolerant systems with no single point of failure. Thus the failure of a system component does not imply the outage of the service (i.e. the functionality) provided by the component. This is achieved by deploying redundant components that resume the service...
Ausführliche Beschreibung
Gespeichert in:
| Autor*in: |
Kanso, Ali [verfasserIn] |
|---|
| Format: |
Artikel |
|---|---|
| Sprache: |
Englisch |
| Erschienen: |
2013 |
|---|
| Schlagwörter: |
|---|
| Systematik: |
|
|---|
| Anmerkung: |
© Springer-Verlag Wien 2013 |
|---|
| Übergeordnetes Werk: |
Enthalten in: Computing - Springer Vienna, 1966, 96(2013), 10 vom: 29. Okt., Seite 975-993 |
|---|---|
| Übergeordnetes Werk: |
volume:96 ; year:2013 ; number:10 ; day:29 ; month:10 ; pages:975-993 |
| Links: |
|---|
| DOI / URN: |
10.1007/s00607-013-0361-x |
|---|
| Katalog-ID: |
OLC2061427529 |
|---|
| LEADER | 01000caa a22002652 4500 | ||
|---|---|---|---|
| 001 | OLC2061427529 | ||
| 003 | DE-627 | ||
| 005 | 20230502133755.0 | ||
| 007 | tu | ||
| 008 | 200819s2013 xx ||||| 00| ||eng c | ||
| 024 | 7 | |a 10.1007/s00607-013-0361-x |2 doi | |
| 035 | |a (DE-627)OLC2061427529 | ||
| 035 | |a (DE-He213)s00607-013-0361-x-p | ||
| 040 | |a DE-627 |b ger |c DE-627 |e rakwb | ||
| 041 | |a eng | ||
| 082 | 0 | 4 | |a 004 |q VZ |
| 084 | |a SA 4220 |q VZ |2 rvk | ||
| 084 | |a SA 4220 |q VZ |2 rvk | ||
| 100 | 1 | |a Kanso, Ali |e verfasserin |4 aut | |
| 245 | 1 | 0 | |a Comparing redundancy models for high availability middleware |
| 264 | 1 | |c 2013 | |
| 336 | |a Text |b txt |2 rdacontent | ||
| 337 | |a ohne Hilfsmittel zu benutzen |b n |2 rdamedia | ||
| 338 | |a Band |b nc |2 rdacarrier | ||
| 500 | |a © Springer-Verlag Wien 2013 | ||
| 520 | |a Abstract Highly available systems are fault tolerant systems with no single point of failure. Thus the failure of a system component does not imply the outage of the service (i.e. the functionality) provided by the component. This is achieved by deploying redundant components that resume the service provisioning in case of failure. These redundant components may collaborate in assuring the availability of their service according to different redundancy models. In this paper we analyze these redundancy models under different assumptions, and compare their effectiveness with respect to availability in the context of a standardized middleware for service high availability and under some specific setups to derive configuration guidelines. | ||
| 650 | 4 | |a Quality of service | |
| 650 | 4 | |a Service availability | |
| 650 | 4 | |a Redundancy models | |
| 650 | 4 | |a Availability management | |
| 650 | 4 | |a Availability analysis | |
| 650 | 4 | |a Stochastic petri nets | |
| 700 | 1 | |a Toeroe, Maria |4 aut | |
| 700 | 1 | |a Khendek, Ferhat |4 aut | |
| 773 | 0 | 8 | |i Enthalten in |t Computing |d Springer Vienna, 1966 |g 96(2013), 10 vom: 29. Okt., Seite 975-993 |w (DE-627)129534927 |w (DE-600)215907-7 |w (DE-576)014963949 |x 0010-485X |7 nnns |
| 773 | 1 | 8 | |g volume:96 |g year:2013 |g number:10 |g day:29 |g month:10 |g pages:975-993 |
| 856 | 4 | 1 | |u https://doi.org/10.1007/s00607-013-0361-x |z lizenzpflichtig |3 Volltext |
| 912 | |a GBV_USEFLAG_A | ||
| 912 | |a SYSFLAG_A | ||
| 912 | |a GBV_OLC | ||
| 912 | |a SSG-OLC-TEC | ||
| 912 | |a SSG-OLC-MAT | ||
| 912 | |a SSG-OPC-MAT | ||
| 912 | |a GBV_ILN_22 | ||
| 912 | |a GBV_ILN_24 | ||
| 912 | |a GBV_ILN_65 | ||
| 912 | |a GBV_ILN_70 | ||
| 912 | |a GBV_ILN_130 | ||
| 912 | |a GBV_ILN_2004 | ||
| 912 | |a GBV_ILN_2012 | ||
| 912 | |a GBV_ILN_2057 | ||
| 912 | |a GBV_ILN_2088 | ||
| 912 | |a GBV_ILN_4036 | ||
| 912 | |a GBV_ILN_4125 | ||
| 912 | |a GBV_ILN_4318 | ||
| 912 | |a GBV_ILN_4323 | ||
| 912 | |a GBV_ILN_4700 | ||
| 936 | r | v | |a SA 4220 |
| 936 | r | v | |a SA 4220 |
| 951 | |a AR | ||
| 952 | |d 96 |j 2013 |e 10 |b 29 |c 10 |h 975-993 | ||
| author_variant |
a k ak m t mt f k fk |
|---|---|
| matchkey_str |
article:0010485X:2013----::oprnrdnacmdlfrihvia |
| hierarchy_sort_str |
2013 |
| publishDate |
2013 |
| allfields |
10.1007/s00607-013-0361-x doi (DE-627)OLC2061427529 (DE-He213)s00607-013-0361-x-p DE-627 ger DE-627 rakwb eng 004 VZ SA 4220 VZ rvk SA 4220 VZ rvk Kanso, Ali verfasserin aut Comparing redundancy models for high availability middleware 2013 Text txt rdacontent ohne Hilfsmittel zu benutzen n rdamedia Band nc rdacarrier © Springer-Verlag Wien 2013 Abstract Highly available systems are fault tolerant systems with no single point of failure. Thus the failure of a system component does not imply the outage of the service (i.e. the functionality) provided by the component. This is achieved by deploying redundant components that resume the service provisioning in case of failure. These redundant components may collaborate in assuring the availability of their service according to different redundancy models. In this paper we analyze these redundancy models under different assumptions, and compare their effectiveness with respect to availability in the context of a standardized middleware for service high availability and under some specific setups to derive configuration guidelines. Quality of service Service availability Redundancy models Availability management Availability analysis Stochastic petri nets Toeroe, Maria aut Khendek, Ferhat aut Enthalten in Computing Springer Vienna, 1966 96(2013), 10 vom: 29. Okt., Seite 975-993 (DE-627)129534927 (DE-600)215907-7 (DE-576)014963949 0010-485X nnns volume:96 year:2013 number:10 day:29 month:10 pages:975-993 https://doi.org/10.1007/s00607-013-0361-x lizenzpflichtig Volltext GBV_USEFLAG_A SYSFLAG_A GBV_OLC SSG-OLC-TEC SSG-OLC-MAT SSG-OPC-MAT GBV_ILN_22 GBV_ILN_24 GBV_ILN_65 GBV_ILN_70 GBV_ILN_130 GBV_ILN_2004 GBV_ILN_2012 GBV_ILN_2057 GBV_ILN_2088 GBV_ILN_4036 GBV_ILN_4125 GBV_ILN_4318 GBV_ILN_4323 GBV_ILN_4700 SA 4220 SA 4220 AR 96 2013 10 29 10 975-993 |
| spelling |
10.1007/s00607-013-0361-x doi (DE-627)OLC2061427529 (DE-He213)s00607-013-0361-x-p DE-627 ger DE-627 rakwb eng 004 VZ SA 4220 VZ rvk SA 4220 VZ rvk Kanso, Ali verfasserin aut Comparing redundancy models for high availability middleware 2013 Text txt rdacontent ohne Hilfsmittel zu benutzen n rdamedia Band nc rdacarrier © Springer-Verlag Wien 2013 Abstract Highly available systems are fault tolerant systems with no single point of failure. Thus the failure of a system component does not imply the outage of the service (i.e. the functionality) provided by the component. This is achieved by deploying redundant components that resume the service provisioning in case of failure. These redundant components may collaborate in assuring the availability of their service according to different redundancy models. In this paper we analyze these redundancy models under different assumptions, and compare their effectiveness with respect to availability in the context of a standardized middleware for service high availability and under some specific setups to derive configuration guidelines. Quality of service Service availability Redundancy models Availability management Availability analysis Stochastic petri nets Toeroe, Maria aut Khendek, Ferhat aut Enthalten in Computing Springer Vienna, 1966 96(2013), 10 vom: 29. Okt., Seite 975-993 (DE-627)129534927 (DE-600)215907-7 (DE-576)014963949 0010-485X nnns volume:96 year:2013 number:10 day:29 month:10 pages:975-993 https://doi.org/10.1007/s00607-013-0361-x lizenzpflichtig Volltext GBV_USEFLAG_A SYSFLAG_A GBV_OLC SSG-OLC-TEC SSG-OLC-MAT SSG-OPC-MAT GBV_ILN_22 GBV_ILN_24 GBV_ILN_65 GBV_ILN_70 GBV_ILN_130 GBV_ILN_2004 GBV_ILN_2012 GBV_ILN_2057 GBV_ILN_2088 GBV_ILN_4036 GBV_ILN_4125 GBV_ILN_4318 GBV_ILN_4323 GBV_ILN_4700 SA 4220 SA 4220 AR 96 2013 10 29 10 975-993 |
| allfields_unstemmed |
10.1007/s00607-013-0361-x doi (DE-627)OLC2061427529 (DE-He213)s00607-013-0361-x-p DE-627 ger DE-627 rakwb eng 004 VZ SA 4220 VZ rvk SA 4220 VZ rvk Kanso, Ali verfasserin aut Comparing redundancy models for high availability middleware 2013 Text txt rdacontent ohne Hilfsmittel zu benutzen n rdamedia Band nc rdacarrier © Springer-Verlag Wien 2013 Abstract Highly available systems are fault tolerant systems with no single point of failure. Thus the failure of a system component does not imply the outage of the service (i.e. the functionality) provided by the component. This is achieved by deploying redundant components that resume the service provisioning in case of failure. These redundant components may collaborate in assuring the availability of their service according to different redundancy models. In this paper we analyze these redundancy models under different assumptions, and compare their effectiveness with respect to availability in the context of a standardized middleware for service high availability and under some specific setups to derive configuration guidelines. Quality of service Service availability Redundancy models Availability management Availability analysis Stochastic petri nets Toeroe, Maria aut Khendek, Ferhat aut Enthalten in Computing Springer Vienna, 1966 96(2013), 10 vom: 29. Okt., Seite 975-993 (DE-627)129534927 (DE-600)215907-7 (DE-576)014963949 0010-485X nnns volume:96 year:2013 number:10 day:29 month:10 pages:975-993 https://doi.org/10.1007/s00607-013-0361-x lizenzpflichtig Volltext GBV_USEFLAG_A SYSFLAG_A GBV_OLC SSG-OLC-TEC SSG-OLC-MAT SSG-OPC-MAT GBV_ILN_22 GBV_ILN_24 GBV_ILN_65 GBV_ILN_70 GBV_ILN_130 GBV_ILN_2004 GBV_ILN_2012 GBV_ILN_2057 GBV_ILN_2088 GBV_ILN_4036 GBV_ILN_4125 GBV_ILN_4318 GBV_ILN_4323 GBV_ILN_4700 SA 4220 SA 4220 AR 96 2013 10 29 10 975-993 |
| allfieldsGer |
10.1007/s00607-013-0361-x doi (DE-627)OLC2061427529 (DE-He213)s00607-013-0361-x-p DE-627 ger DE-627 rakwb eng 004 VZ SA 4220 VZ rvk SA 4220 VZ rvk Kanso, Ali verfasserin aut Comparing redundancy models for high availability middleware 2013 Text txt rdacontent ohne Hilfsmittel zu benutzen n rdamedia Band nc rdacarrier © Springer-Verlag Wien 2013 Abstract Highly available systems are fault tolerant systems with no single point of failure. Thus the failure of a system component does not imply the outage of the service (i.e. the functionality) provided by the component. This is achieved by deploying redundant components that resume the service provisioning in case of failure. These redundant components may collaborate in assuring the availability of their service according to different redundancy models. In this paper we analyze these redundancy models under different assumptions, and compare their effectiveness with respect to availability in the context of a standardized middleware for service high availability and under some specific setups to derive configuration guidelines. Quality of service Service availability Redundancy models Availability management Availability analysis Stochastic petri nets Toeroe, Maria aut Khendek, Ferhat aut Enthalten in Computing Springer Vienna, 1966 96(2013), 10 vom: 29. Okt., Seite 975-993 (DE-627)129534927 (DE-600)215907-7 (DE-576)014963949 0010-485X nnns volume:96 year:2013 number:10 day:29 month:10 pages:975-993 https://doi.org/10.1007/s00607-013-0361-x lizenzpflichtig Volltext GBV_USEFLAG_A SYSFLAG_A GBV_OLC SSG-OLC-TEC SSG-OLC-MAT SSG-OPC-MAT GBV_ILN_22 GBV_ILN_24 GBV_ILN_65 GBV_ILN_70 GBV_ILN_130 GBV_ILN_2004 GBV_ILN_2012 GBV_ILN_2057 GBV_ILN_2088 GBV_ILN_4036 GBV_ILN_4125 GBV_ILN_4318 GBV_ILN_4323 GBV_ILN_4700 SA 4220 SA 4220 AR 96 2013 10 29 10 975-993 |
| allfieldsSound |
10.1007/s00607-013-0361-x doi (DE-627)OLC2061427529 (DE-He213)s00607-013-0361-x-p DE-627 ger DE-627 rakwb eng 004 VZ SA 4220 VZ rvk SA 4220 VZ rvk Kanso, Ali verfasserin aut Comparing redundancy models for high availability middleware 2013 Text txt rdacontent ohne Hilfsmittel zu benutzen n rdamedia Band nc rdacarrier © Springer-Verlag Wien 2013 Abstract Highly available systems are fault tolerant systems with no single point of failure. Thus the failure of a system component does not imply the outage of the service (i.e. the functionality) provided by the component. This is achieved by deploying redundant components that resume the service provisioning in case of failure. These redundant components may collaborate in assuring the availability of their service according to different redundancy models. In this paper we analyze these redundancy models under different assumptions, and compare their effectiveness with respect to availability in the context of a standardized middleware for service high availability and under some specific setups to derive configuration guidelines. Quality of service Service availability Redundancy models Availability management Availability analysis Stochastic petri nets Toeroe, Maria aut Khendek, Ferhat aut Enthalten in Computing Springer Vienna, 1966 96(2013), 10 vom: 29. Okt., Seite 975-993 (DE-627)129534927 (DE-600)215907-7 (DE-576)014963949 0010-485X nnns volume:96 year:2013 number:10 day:29 month:10 pages:975-993 https://doi.org/10.1007/s00607-013-0361-x lizenzpflichtig Volltext GBV_USEFLAG_A SYSFLAG_A GBV_OLC SSG-OLC-TEC SSG-OLC-MAT SSG-OPC-MAT GBV_ILN_22 GBV_ILN_24 GBV_ILN_65 GBV_ILN_70 GBV_ILN_130 GBV_ILN_2004 GBV_ILN_2012 GBV_ILN_2057 GBV_ILN_2088 GBV_ILN_4036 GBV_ILN_4125 GBV_ILN_4318 GBV_ILN_4323 GBV_ILN_4700 SA 4220 SA 4220 AR 96 2013 10 29 10 975-993 |
| language |
English |
| source |
Enthalten in Computing 96(2013), 10 vom: 29. Okt., Seite 975-993 volume:96 year:2013 number:10 day:29 month:10 pages:975-993 |
| sourceStr |
Enthalten in Computing 96(2013), 10 vom: 29. Okt., Seite 975-993 volume:96 year:2013 number:10 day:29 month:10 pages:975-993 |
| format_phy_str_mv |
Article |
| institution |
findex.gbv.de |
| topic_facet |
Quality of service Service availability Redundancy models Availability management Availability analysis Stochastic petri nets |
| dewey-raw |
004 |
| isfreeaccess_bool |
false |
| container_title |
Computing |
| authorswithroles_txt_mv |
Kanso, Ali @@aut@@ Toeroe, Maria @@aut@@ Khendek, Ferhat @@aut@@ |
| publishDateDaySort_date |
2013-10-29T00:00:00Z |
| hierarchy_top_id |
129534927 |
| dewey-sort |
14 |
| id |
OLC2061427529 |
| language_de |
englisch |
| fullrecord |
<?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>01000caa a22002652 4500</leader><controlfield tag="001">OLC2061427529</controlfield><controlfield tag="003">DE-627</controlfield><controlfield tag="005">20230502133755.0</controlfield><controlfield tag="007">tu</controlfield><controlfield tag="008">200819s2013 xx ||||| 00| ||eng c</controlfield><datafield tag="024" ind1="7" ind2=" "><subfield code="a">10.1007/s00607-013-0361-x</subfield><subfield code="2">doi</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-627)OLC2061427529</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-He213)s00607-013-0361-x-p</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-627</subfield><subfield code="b">ger</subfield><subfield code="c">DE-627</subfield><subfield code="e">rakwb</subfield></datafield><datafield tag="041" ind1=" " ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="082" ind1="0" ind2="4"><subfield code="a">004</subfield><subfield code="q">VZ</subfield></datafield><datafield tag="084" ind1=" " ind2=" "><subfield code="a">SA 4220</subfield><subfield code="q">VZ</subfield><subfield code="2">rvk</subfield></datafield><datafield tag="084" ind1=" " ind2=" "><subfield code="a">SA 4220</subfield><subfield code="q">VZ</subfield><subfield code="2">rvk</subfield></datafield><datafield tag="100" ind1="1" ind2=" "><subfield code="a">Kanso, Ali</subfield><subfield code="e">verfasserin</subfield><subfield code="4">aut</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">Comparing redundancy models for high availability middleware</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="c">2013</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="a">Text</subfield><subfield code="b">txt</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="a">ohne Hilfsmittel zu benutzen</subfield><subfield code="b">n</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="a">Band</subfield><subfield code="b">nc</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">© Springer-Verlag Wien 2013</subfield></datafield><datafield tag="520" ind1=" " ind2=" "><subfield code="a">Abstract Highly available systems are fault tolerant systems with no single point of failure. Thus the failure of a system component does not imply the outage of the service (i.e. the functionality) provided by the component. This is achieved by deploying redundant components that resume the service provisioning in case of failure. These redundant components may collaborate in assuring the availability of their service according to different redundancy models. In this paper we analyze these redundancy models under different assumptions, and compare their effectiveness with respect to availability in the context of a standardized middleware for service high availability and under some specific setups to derive configuration guidelines.</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Quality of service</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Service availability</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Redundancy models</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Availability management</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Availability analysis</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Stochastic petri nets</subfield></datafield><datafield tag="700" ind1="1" ind2=" "><subfield code="a">Toeroe, Maria</subfield><subfield code="4">aut</subfield></datafield><datafield tag="700" ind1="1" ind2=" "><subfield code="a">Khendek, Ferhat</subfield><subfield code="4">aut</subfield></datafield><datafield tag="773" ind1="0" ind2="8"><subfield code="i">Enthalten in</subfield><subfield code="t">Computing</subfield><subfield code="d">Springer Vienna, 1966</subfield><subfield code="g">96(2013), 10 vom: 29. Okt., Seite 975-993</subfield><subfield code="w">(DE-627)129534927</subfield><subfield code="w">(DE-600)215907-7</subfield><subfield code="w">(DE-576)014963949</subfield><subfield code="x">0010-485X</subfield><subfield code="7">nnns</subfield></datafield><datafield tag="773" ind1="1" ind2="8"><subfield code="g">volume:96</subfield><subfield code="g">year:2013</subfield><subfield code="g">number:10</subfield><subfield code="g">day:29</subfield><subfield code="g">month:10</subfield><subfield code="g">pages:975-993</subfield></datafield><datafield tag="856" ind1="4" ind2="1"><subfield code="u">https://doi.org/10.1007/s00607-013-0361-x</subfield><subfield code="z">lizenzpflichtig</subfield><subfield code="3">Volltext</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_USEFLAG_A</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">SYSFLAG_A</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_OLC</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">SSG-OLC-TEC</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">SSG-OLC-MAT</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">SSG-OPC-MAT</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_22</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_24</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_65</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_70</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_130</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2004</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2012</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2057</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2088</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4036</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4125</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4318</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4323</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4700</subfield></datafield><datafield tag="936" ind1="r" ind2="v"><subfield code="a">SA 4220</subfield></datafield><datafield tag="936" ind1="r" ind2="v"><subfield code="a">SA 4220</subfield></datafield><datafield tag="951" ind1=" " ind2=" "><subfield code="a">AR</subfield></datafield><datafield tag="952" ind1=" " ind2=" "><subfield code="d">96</subfield><subfield code="j">2013</subfield><subfield code="e">10</subfield><subfield code="b">29</subfield><subfield code="c">10</subfield><subfield code="h">975-993</subfield></datafield></record></collection>
|
| author |
Kanso, Ali |
| spellingShingle |
Kanso, Ali ddc 004 rvk SA 4220 misc Quality of service misc Service availability misc Redundancy models misc Availability management misc Availability analysis misc Stochastic petri nets Comparing redundancy models for high availability middleware |
| authorStr |
Kanso, Ali |
| ppnlink_with_tag_str_mv |
@@773@@(DE-627)129534927 |
| format |
Article |
| dewey-ones |
004 - Data processing & computer science |
| delete_txt_mv |
keep |
| author_role |
aut aut aut |
| collection |
OLC |
| remote_str |
false |
| illustrated |
Not Illustrated |
| issn |
0010-485X |
| topic_title |
004 VZ SA 4220 VZ rvk Comparing redundancy models for high availability middleware Quality of service Service availability Redundancy models Availability management Availability analysis Stochastic petri nets |
| topic |
ddc 004 rvk SA 4220 misc Quality of service misc Service availability misc Redundancy models misc Availability management misc Availability analysis misc Stochastic petri nets |
| topic_unstemmed |
ddc 004 rvk SA 4220 misc Quality of service misc Service availability misc Redundancy models misc Availability management misc Availability analysis misc Stochastic petri nets |
| topic_browse |
ddc 004 rvk SA 4220 misc Quality of service misc Service availability misc Redundancy models misc Availability management misc Availability analysis misc Stochastic petri nets |
| format_facet |
Aufsätze Gedruckte Aufsätze |
| format_main_str_mv |
Text Zeitschrift/Artikel |
| carriertype_str_mv |
nc |
| hierarchy_parent_title |
Computing |
| hierarchy_parent_id |
129534927 |
| dewey-tens |
000 - Computer science, knowledge & systems |
| hierarchy_top_title |
Computing |
| isfreeaccess_txt |
false |
| familylinks_str_mv |
(DE-627)129534927 (DE-600)215907-7 (DE-576)014963949 |
| title |
Comparing redundancy models for high availability middleware |
| ctrlnum |
(DE-627)OLC2061427529 (DE-He213)s00607-013-0361-x-p |
| title_full |
Comparing redundancy models for high availability middleware |
| author_sort |
Kanso, Ali |
| journal |
Computing |
| journalStr |
Computing |
| lang_code |
eng |
| isOA_bool |
false |
| dewey-hundreds |
000 - Computer science, information & general works |
| recordtype |
marc |
| publishDateSort |
2013 |
| contenttype_str_mv |
txt |
| container_start_page |
975 |
| author_browse |
Kanso, Ali Toeroe, Maria Khendek, Ferhat |
| container_volume |
96 |
| class |
004 VZ SA 4220 VZ rvk |
| format_se |
Aufsätze |
| author-letter |
Kanso, Ali |
| doi_str_mv |
10.1007/s00607-013-0361-x |
| dewey-full |
004 |
| title_sort |
comparing redundancy models for high availability middleware |
| title_auth |
Comparing redundancy models for high availability middleware |
| abstract |
Abstract Highly available systems are fault tolerant systems with no single point of failure. Thus the failure of a system component does not imply the outage of the service (i.e. the functionality) provided by the component. This is achieved by deploying redundant components that resume the service provisioning in case of failure. These redundant components may collaborate in assuring the availability of their service according to different redundancy models. In this paper we analyze these redundancy models under different assumptions, and compare their effectiveness with respect to availability in the context of a standardized middleware for service high availability and under some specific setups to derive configuration guidelines. © Springer-Verlag Wien 2013 |
| abstractGer |
Abstract Highly available systems are fault tolerant systems with no single point of failure. Thus the failure of a system component does not imply the outage of the service (i.e. the functionality) provided by the component. This is achieved by deploying redundant components that resume the service provisioning in case of failure. These redundant components may collaborate in assuring the availability of their service according to different redundancy models. In this paper we analyze these redundancy models under different assumptions, and compare their effectiveness with respect to availability in the context of a standardized middleware for service high availability and under some specific setups to derive configuration guidelines. © Springer-Verlag Wien 2013 |
| abstract_unstemmed |
Abstract Highly available systems are fault tolerant systems with no single point of failure. Thus the failure of a system component does not imply the outage of the service (i.e. the functionality) provided by the component. This is achieved by deploying redundant components that resume the service provisioning in case of failure. These redundant components may collaborate in assuring the availability of their service according to different redundancy models. In this paper we analyze these redundancy models under different assumptions, and compare their effectiveness with respect to availability in the context of a standardized middleware for service high availability and under some specific setups to derive configuration guidelines. © Springer-Verlag Wien 2013 |
| collection_details |
GBV_USEFLAG_A SYSFLAG_A GBV_OLC SSG-OLC-TEC SSG-OLC-MAT SSG-OPC-MAT GBV_ILN_22 GBV_ILN_24 GBV_ILN_65 GBV_ILN_70 GBV_ILN_130 GBV_ILN_2004 GBV_ILN_2012 GBV_ILN_2057 GBV_ILN_2088 GBV_ILN_4036 GBV_ILN_4125 GBV_ILN_4318 GBV_ILN_4323 GBV_ILN_4700 |
| container_issue |
10 |
| title_short |
Comparing redundancy models for high availability middleware |
| url |
https://doi.org/10.1007/s00607-013-0361-x |
| remote_bool |
false |
| author2 |
Toeroe, Maria Khendek, Ferhat |
| author2Str |
Toeroe, Maria Khendek, Ferhat |
| ppnlink |
129534927 |
| mediatype_str_mv |
n |
| isOA_txt |
false |
| hochschulschrift_bool |
false |
| doi_str |
10.1007/s00607-013-0361-x |
| up_date |
2024-07-04T03:34:19.216Z |
| _version_ |
1803617890973253632 |
| fullrecord_marcxml |
<?xml version="1.0" encoding="UTF-8"?><collection xmlns="http://www.loc.gov/MARC21/slim"><record><leader>01000caa a22002652 4500</leader><controlfield tag="001">OLC2061427529</controlfield><controlfield tag="003">DE-627</controlfield><controlfield tag="005">20230502133755.0</controlfield><controlfield tag="007">tu</controlfield><controlfield tag="008">200819s2013 xx ||||| 00| ||eng c</controlfield><datafield tag="024" ind1="7" ind2=" "><subfield code="a">10.1007/s00607-013-0361-x</subfield><subfield code="2">doi</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-627)OLC2061427529</subfield></datafield><datafield tag="035" ind1=" " ind2=" "><subfield code="a">(DE-He213)s00607-013-0361-x-p</subfield></datafield><datafield tag="040" ind1=" " ind2=" "><subfield code="a">DE-627</subfield><subfield code="b">ger</subfield><subfield code="c">DE-627</subfield><subfield code="e">rakwb</subfield></datafield><datafield tag="041" ind1=" " ind2=" "><subfield code="a">eng</subfield></datafield><datafield tag="082" ind1="0" ind2="4"><subfield code="a">004</subfield><subfield code="q">VZ</subfield></datafield><datafield tag="084" ind1=" " ind2=" "><subfield code="a">SA 4220</subfield><subfield code="q">VZ</subfield><subfield code="2">rvk</subfield></datafield><datafield tag="084" ind1=" " ind2=" "><subfield code="a">SA 4220</subfield><subfield code="q">VZ</subfield><subfield code="2">rvk</subfield></datafield><datafield tag="100" ind1="1" ind2=" "><subfield code="a">Kanso, Ali</subfield><subfield code="e">verfasserin</subfield><subfield code="4">aut</subfield></datafield><datafield tag="245" ind1="1" ind2="0"><subfield code="a">Comparing redundancy models for high availability middleware</subfield></datafield><datafield tag="264" ind1=" " ind2="1"><subfield code="c">2013</subfield></datafield><datafield tag="336" ind1=" " ind2=" "><subfield code="a">Text</subfield><subfield code="b">txt</subfield><subfield code="2">rdacontent</subfield></datafield><datafield tag="337" ind1=" " ind2=" "><subfield code="a">ohne Hilfsmittel zu benutzen</subfield><subfield code="b">n</subfield><subfield code="2">rdamedia</subfield></datafield><datafield tag="338" ind1=" " ind2=" "><subfield code="a">Band</subfield><subfield code="b">nc</subfield><subfield code="2">rdacarrier</subfield></datafield><datafield tag="500" ind1=" " ind2=" "><subfield code="a">© Springer-Verlag Wien 2013</subfield></datafield><datafield tag="520" ind1=" " ind2=" "><subfield code="a">Abstract Highly available systems are fault tolerant systems with no single point of failure. Thus the failure of a system component does not imply the outage of the service (i.e. the functionality) provided by the component. This is achieved by deploying redundant components that resume the service provisioning in case of failure. These redundant components may collaborate in assuring the availability of their service according to different redundancy models. In this paper we analyze these redundancy models under different assumptions, and compare their effectiveness with respect to availability in the context of a standardized middleware for service high availability and under some specific setups to derive configuration guidelines.</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Quality of service</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Service availability</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Redundancy models</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Availability management</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Availability analysis</subfield></datafield><datafield tag="650" ind1=" " ind2="4"><subfield code="a">Stochastic petri nets</subfield></datafield><datafield tag="700" ind1="1" ind2=" "><subfield code="a">Toeroe, Maria</subfield><subfield code="4">aut</subfield></datafield><datafield tag="700" ind1="1" ind2=" "><subfield code="a">Khendek, Ferhat</subfield><subfield code="4">aut</subfield></datafield><datafield tag="773" ind1="0" ind2="8"><subfield code="i">Enthalten in</subfield><subfield code="t">Computing</subfield><subfield code="d">Springer Vienna, 1966</subfield><subfield code="g">96(2013), 10 vom: 29. Okt., Seite 975-993</subfield><subfield code="w">(DE-627)129534927</subfield><subfield code="w">(DE-600)215907-7</subfield><subfield code="w">(DE-576)014963949</subfield><subfield code="x">0010-485X</subfield><subfield code="7">nnns</subfield></datafield><datafield tag="773" ind1="1" ind2="8"><subfield code="g">volume:96</subfield><subfield code="g">year:2013</subfield><subfield code="g">number:10</subfield><subfield code="g">day:29</subfield><subfield code="g">month:10</subfield><subfield code="g">pages:975-993</subfield></datafield><datafield tag="856" ind1="4" ind2="1"><subfield code="u">https://doi.org/10.1007/s00607-013-0361-x</subfield><subfield code="z">lizenzpflichtig</subfield><subfield code="3">Volltext</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_USEFLAG_A</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">SYSFLAG_A</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_OLC</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">SSG-OLC-TEC</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">SSG-OLC-MAT</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">SSG-OPC-MAT</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_22</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_24</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_65</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_70</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_130</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2004</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2012</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2057</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_2088</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4036</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4125</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4318</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4323</subfield></datafield><datafield tag="912" ind1=" " ind2=" "><subfield code="a">GBV_ILN_4700</subfield></datafield><datafield tag="936" ind1="r" ind2="v"><subfield code="a">SA 4220</subfield></datafield><datafield tag="936" ind1="r" ind2="v"><subfield code="a">SA 4220</subfield></datafield><datafield tag="951" ind1=" " ind2=" "><subfield code="a">AR</subfield></datafield><datafield tag="952" ind1=" " ind2=" "><subfield code="d">96</subfield><subfield code="j">2013</subfield><subfield code="e">10</subfield><subfield code="b">29</subfield><subfield code="c">10</subfield><subfield code="h">975-993</subfield></datafield></record></collection>
|
| score |
7.400959 |