<?xml version="1.0" encoding="UTF-8"?>
<record
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>02474nam a22003017i 4500</leader>
  <controlfield tag="005">20251030140037.0</controlfield>
  <controlfield tag="006">a|||||r|||| 00| 0 </controlfield>
  <controlfield tag="007">t|</controlfield>
  <controlfield tag="008">250304s2022    |||||||| |||| 00| 0 spa d</controlfield>
  <datafield tag="020" ind1=" " ind2=" ">
    <subfield code="a">9780137355631</subfield>
  </datafield>
  <datafield tag="040" ind1=" " ind2=" ">
    <subfield code="a">CO-ViULL</subfield>
    <subfield code="e">rda</subfield>
    <subfield code="b">spa</subfield>
  </datafield>
  <datafield tag="041" ind1=" " ind2=" ">
    <subfield code="h">eng</subfield>
  </datafield>
  <datafield tag="082" ind1="0" ind2=" ">
    <subfield code="2">23</subfield>
    <subfield code="a">005.1</subfield>
    <subfield code="b">H635p</subfield>
  </datafield>
  <datafield tag="100" ind1="1" ind2=" ">
    <subfield code="a">Higginbotham, James</subfield>
    <subfield code="9">164278,</subfield>
    <subfield code="e">autor.</subfield>
    <subfield code="4">aut</subfield>
  </datafield>
  <datafield tag="245" ind1="1" ind2="0">
    <subfield code="a">Principles of web API design :</subfield>
    <subfield code="b">delivering value with APIs and microservices.</subfield>
  </datafield>
  <datafield tag="250" ind1=" " ind2=" ">
    <subfield code="a">1.</subfield>
  </datafield>
  <datafield tag="264" ind1=" " ind2="1">
    <subfield code="a">[Place of publication not identified] :</subfield>
    <subfield code="b">Pearson Education,</subfield>
    <subfield code="c">2022.</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">333 p&#xE1;ginas :</subfield>
    <subfield code="b">: incluye tablas y  figuras.</subfield>
  </datafield>
  <datafield tag="336" ind1=" " ind2=" ">
    <subfield code="a">texto</subfield>
    <subfield code="b">txt</subfield>
    <subfield code="2">rdacontent</subfield>
  </datafield>
  <datafield tag="337" ind1=" " ind2=" ">
    <subfield code="a">sin mediaci&#xF3;n</subfield>
    <subfield code="b">n</subfield>
    <subfield code="2">rdamedia</subfield>
  </datafield>
  <datafield tag="338" ind1=" " ind2=" ">
    <subfield code="a">volumen</subfield>
    <subfield code="b">nc</subfield>
    <subfield code="2">rdacarrier</subfield>
  </datafield>
  <datafield tag="505" ind1="8" ind2=" ">
    <subfield code="a">Part I: Introduction to Web API Design. -- Chapter 1. The Principles of API Design. -- Chapter 2. Collaborative API Design. -- Part II: Aligning on API Outcomes. -- Chapter 3. Identify Digital Capabilities -- Chapter 4. Capture Activities and Steps. -- Part III: Defining Candidate APIs -- Chapter 5. Identifying API Boundaries -- Chapter 6. API Modeling -- Part IV: Designing APIs -- Chapter 7. REST-Based API Design -- Chapter 8. RPC and Query-Based API Design -- Chapter 9. Async APIs for Eventing and Streaming -- Part V: Refining the API Design -- Chapter 10. From APIs to Microservices -- Chapter 11. Improving the Developer Experience -- Chapter 12. API Testing Strategies -- Chapter 13. Document the API Design -- Chapter 14. Designing for Change -- Chapter 15. Protecting APIs -- Chapter 16. Continuing the API Design Journey.</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">Principles of Web API Design brings together principles and processes to help you succeed across the entire API design lifecycle. Drawing on extensive in-the-trenches experience, leading consultant James Higginbotham helps you align every stakeholder on specific outcomes, design APIs that deliver value, and scale the design process from small teams to the entire organization. Higginbotham helps you bring an "outside-in" perspective to API design to reflect the voices of customers and product teams, map requirements to specific and well-organized APIs, and choose the right API style for writing them. He walks through a real-world example from the ground up, offering guidance for anyone designing new APIs or extending existing APIs.</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
    <subfield code="a">Web API Design</subfield>
    <subfield code="9">164279.</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
    <subfield code="a">API Design</subfield>
    <subfield code="9">164280.</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
    <subfield code="a">Software.</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="2">ddc</subfield>
    <subfield code="c">BK</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">48316</subfield>
    <subfield code="d">48316</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="2">ddc</subfield>
    <subfield code="4">0</subfield>
    <subfield code="5">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="a">001</subfield>
    <subfield code="b">001</subfield>
    <subfield code="c">GEN</subfield>
    <subfield code="d">2025-03-04</subfield>
    <subfield code="e">Ediciones de la U</subfield>
    <subfield code="f">Compra</subfield>
    <subfield code="g">438480.00</subfield>
    <subfield code="l">0</subfield>
    <subfield code="o">005.1 H635p</subfield>
    <subfield code="p">088491</subfield>
    <subfield code="r">2025-03-04 16:32:21</subfield>
    <subfield code="t">Ej.:1</subfield>
    <subfield code="w">2025-03-04</subfield>
    <subfield code="x">SIS</subfield>
    <subfield code="y">BK</subfield>
  </datafield>
</record>
