Why SRE documents matter.
How documentation enables SRE teams to manage new and existing services.
| Publicado en: | Communications of the ACM Vol. 61; no. 12; pp. 45 - 52 |
|---|---|
| Autores principales: | , |
| Formato: | Artículo |
| Publicado: |
Association for Computing Machinery
Dec2018
|
| Materias: | |
| Acceso en línea: | Ver este registro en EBSCOhost |
| fields | @attributes: recordID: 1 pdfLink: plink: https://search.ebscohost.com/login.aspx?direct=true&db=hlh&AN=134657116&site=ehost-live header: @attributes: shortDbName: hlh uiTerm: 134657116 longDbName: Humanities International Complete uiTag: AN controlInfo: bkinfo: jinfo: jid: 00010782 ACM jtl: Communications of the ACM issn: 00010782 maglogo: N pubinfo: dt: Dec2018 vid: 61 iid: 12 pid: 68 pub: Association for Computing Machinery artinfo: ui: 134657116 10.1145/3267122 ppf: 45 ppct: 7 formats: tig: atl: Why SRE documents matter. aug: au: Nukala, Shylaja Rau, Vivek su: Reliability in engineering Reliability engineering software Computer software developers Computer software development Computer systems Systems design sug: subj: Reliability in engineering Reliability engineering software Computer software developers Computer software development Computer systems Systems design ab: How documentation enables SRE teams to manage new and existing services. pubtype: Periodical doctype: Article src: R language: English refInfo: copyright: @attributes: flag: Y dt: @attributes: year: 2018 holdings: @attributes: islocal: N |
|---|