{"id":1261,"date":"2021-03-04T09:31:22","date_gmt":"2021-03-04T09:31:22","guid":{"rendered":"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/?p=1261"},"modified":"2021-03-04T09:31:24","modified_gmt":"2021-03-04T09:31:24","slug":"wcf-alternatives-part-4","status":"publish","type":"post","link":"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/wcf-alternatives-part-4\/","title":{"rendered":"WCF Alternatives (Part 4) \u2013 Summary"},"content":{"rendered":"\n

In the last blog post of the series on alternatives for the Windows Communication Foundation (WCF)<\/a>, we are going to recapitulate and compare them once again. <\/p>\n\n\n\n

<\/div>\n\n\n\n

Decision matrix<\/strong> <\/h2>\n\n\n\n
Characteristic<\/strong><\/th>Web API<\/th>gRPC<\/th><\/tr><\/thead>
Bidirectional communication <\/td>Possible with restrictions 
Has to be realized with SignalR.<\/em> <\/td>		Possible with restrictions 
Only stream response is supported.<\/em> <\/td><\/tr>
Scope of changes to existing code<\/td>Small 
Due to the adoption of the service methods into the controllers and the generation of the client, few adjustments are required.<\/em> <\/td>		Large 
Mapping is required because specific data types are prescribed in some instances: An input parameter and a return value are required.<\/em><\/td><\/tr>
Necessary prior knowledge <\/td>Technology-specific 
Web API knowledge about the use of controllers and actions, HTTP verbs<\/em> <\/td>		Technology-specific 
Particularities of gRPC, creation of the *.proto file<\/em> <\/td><\/tr>
Platform independence <\/td>Yes 
When you use .NET Core, client and server can run on different platforms.<\/em> <\/td>		Yes 
When you use .NET Core, client and server can run on different platforms.<\/em> <\/td><\/tr>
Interoperability<\/td>Yes 
Client and server can be created using different programming languages.<\/em> <\/td>		Yes 
Client and server can be created using different programming languages.<\/em> 
<\/td><\/tr>
Browser support <\/td>Yes<\/td>Optional 
Currently possible only with third-party libraries<\/em> <\/td><\/tr>
Self-describing interfaces <\/td>Optional 
OpenAPI is possible by integrating third-party libraries.<\/em> 
<\/td>		No 
You have to create the *.proto file for the description of the interface yourself.<\/em> <\/td><\/tr>
Payload size<\/td>Higher 
JSON, human-readable<\/em> <\/td>		Lower 
Binary format<\/em> <\/td><\/tr>
Speed<\/td>Lower<\/td>Higher<\/td><\/tr>
Sustainability<\/td>Yes 
Microsoft currently recommends Web API as a sustainable alternative.<\/em> <\/td>		Yes 
Microsoft currently recommends gRPC as a sustainable alternative.<\/em> 
<\/td><\/tr>
Debugging<\/td>Easily possible <\/td>Possible with restrictions 
The transferred data cannot be examined due to the compression.<\/em> <\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
<\/div>\n\n\n\n

Advantages and disadvantages<\/strong> <\/h2>\n\n\n\n
<\/div>\n\n\n\n
\n
\n

<\/p>\n<\/div>\n\n\n\n

\n

Web API<\/strong><\/p>\n<\/div>\n\n\n\n

\n

gRPC<\/strong><\/p>\n<\/div>\n<\/div>\n\n\n\n

\n
\n

Advantages<\/strong><\/strong><\/p>\n<\/div>\n\n\n\n

\n
  • Transmission data are readable <\/li>
  • Fewer code adjustments required for the migration <\/li>
  • More flexible design of the endpoints and calls with respect to input parameters and return values <\/li><\/ul>\n<\/div>\n\n\n\n
    \n
    • Faster transmission <\/li>
    • Typed by means of Protocol Buffers interface description <\/li>
    • Simple generation of client classes <\/li><\/ul>\n\n\n\n

      <\/p>\n<\/div>\n<\/div>\n\n\n\n

      \n
      \n

      Disadvantages<\/strong><\/strong><\/p>\n<\/div>\n\n\n\n

      \n
      • Slower transmission compared to gRPC <\/li>
      • Generation of client classes only by means of third-party libraries <\/li>
      • Typing of the interface not possible <\/li><\/ul>\n<\/div>\n\n\n\n
        \n
        • Transmission data not readable <\/li>
        • Mapping code required because no standard .NET types are used <\/li>
        • Greater effort involved in the migration due to more necessary code adjustments <\/li><\/ul>\n<\/div>\n<\/div>\n\n\n\n
          <\/div>\n\n\n\n

          Conclusion<\/strong><\/h2>\n\n\n\n

          In our blog post series on WCF, we have presented both ASP.NET Core Web API and gRPC. We have seen that both options have advantages and disadvantages. <\/p>\n\n\n\n

          With Web API, the interfaces can easily be used by anybody due to the content-first approach and the use of HTTP. The transmitted data are accessible and can be read at any time. <\/p>\n\n\n\n

          gRPC abstracts the interface calls using the contract-first approach, making them faster and very easy to address by developers. However, the transmitted data cannot be accessed. <\/p>\n\n\n\n

          In principle, migration to both options is possible, and both are recommended by Microsoft. Still, we cannot definitively recommend one of the alternatives. The decision should always be project-specific and based on various criteria such as the project scope, experience with the respective technology or the existing architecture. <\/p>\n","protected":false},"excerpt":{"rendered":"

          In the last blog post of the series on alternatives for the Windows Communication Foundation (WCF), we are going to recapitulate and compare them once again.<\/p>\n","protected":false},"author":105,"featured_media":1260,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"advgb_blocks_editor_width":"","advgb_blocks_columns_visual_guide":"","footnotes":""},"categories":[8,13],"tags":[24,492,629,630,633,634,636,637,638,675],"topics":[642],"class_list":["post-1261","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-web","category-dot-net","tag-microsoft","tag-distributed-collaboration","tag-wcf","tag-windows-communication-foundation","tag-net-framework-3-0","tag-net-remoting","tag-distributed-communication","tag-distributed-application","tag-communication-platform","tag-zeiss-digital-innovation","topics-wcf-alternatives"],"acf":[],"yoast_head":"\nWCF Alternatives (Part 4) - Summary - ZEISS Digital Innovation Blog<\/title>\n<meta name=\"description\" content=\"In the last blog post of the series on WCF alternatives, we are going to recapitulate and compare them once again.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/wcf-alternatives-part-4\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"WCF Alternatives (Part 4) \u2013 Summary\" \/>\n<meta property=\"og:description\" content=\"In the last blog post of the series on alternatives for the Windows Communication Foundation (WCF), we are going to recapitulate and compare them once again.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/wcf-alternatives-part-4\/\" \/>\n<meta property=\"og:site_name\" content=\"Digital Innovation Blog\" \/>\n<meta property=\"article:published_time\" content=\"2021-03-04T09:31:22+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2021-03-04T09:31:24+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/blogs.zeiss.com\/digital-innovation\/de\/wp-content\/uploads\/sites\/2\/2021\/01\/202101_WCF.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1404\" \/>\n\t<meta property=\"og:image:height\" content=\"791\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"David Siebert\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:title\" content=\"WCF Alternatives (Part 4) \u2013 Summary\" \/>\n<meta name=\"twitter:description\" content=\"In the last blog post of the series on alternatives for the Windows Communication Foundation (WCF), we are going to recapitulate and compare them once again.\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"David Siebert\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"3 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/wcf-alternatives-part-4\/\",\"url\":\"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/wcf-alternatives-part-4\/\",\"name\":\"WCF Alternatives (Part 4) - Summary - ZEISS Digital Innovation Blog\",\"isPartOf\":{\"@id\":\"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/wcf-alternatives-part-4\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/wcf-alternatives-part-4\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/blogs.zeiss.com\/digital-innovation\/de\/wp-content\/uploads\/sites\/2\/2021\/01\/202101_WCF.png\",\"datePublished\":\"2021-03-04T09:31:22+00:00\",\"dateModified\":\"2021-03-04T09:31:24+00:00\",\"author\":{\"@id\":\"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/#\/schema\/person\/6b51a72db3cce2762c3e7ba935cf25bf\"},\"description\":\"In the last blog post of the series on WCF alternatives, we are going to recapitulate and compare them once again.\",\"breadcrumb\":{\"@id\":\"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/wcf-alternatives-part-4\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/wcf-alternatives-part-4\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/wcf-alternatives-part-4\/#primaryimage\",\"url\":\"https:\/\/blogs.zeiss.com\/digital-innovation\/de\/wp-content\/uploads\/sites\/2\/2021\/01\/202101_WCF.png\",\"contentUrl\":\"https:\/\/blogs.zeiss.com\/digital-innovation\/de\/wp-content\/uploads\/sites\/2\/2021\/01\/202101_WCF.png\",\"width\":1404,\"height\":791},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/wcf-alternatives-part-4\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"WCF Alternatives (Part 4) \u2013 Summary\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/#website\",\"url\":\"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/\",\"name\":\"Digital Innovation Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/#\/schema\/person\/6b51a72db3cce2762c3e7ba935cf25bf\",\"name\":\"David Siebert\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/wp-content\/uploads\/sites\/3\/2020\/12\/siebert_david-e1607418544482-150x150.jpg\",\"contentUrl\":\"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/wp-content\/uploads\/sites\/3\/2020\/12\/siebert_david-e1607418544482-150x150.jpg\",\"caption\":\"David Siebert\"},\"description\":\"David Siebert is Senior Consultant Software Development at ZEISS Digital Innovation. His focus is primarily on .NET development. In addition, he is particularly involved with web technologies and clean code.\",\"url\":\"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/author\/endavidsiebert\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"WCF Alternatives (Part 4) - Summary - ZEISS Digital Innovation Blog","description":"In the last blog post of the series on WCF alternatives, we are going to recapitulate and compare them once again.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/wcf-alternatives-part-4\/","og_locale":"en_US","og_type":"article","og_title":"WCF Alternatives (Part 4) \u2013 Summary","og_description":"In the last blog post of the series on alternatives for the Windows Communication Foundation (WCF), we are going to recapitulate and compare them once again.","og_url":"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/wcf-alternatives-part-4\/","og_site_name":"Digital Innovation Blog","article_published_time":"2021-03-04T09:31:22+00:00","article_modified_time":"2021-03-04T09:31:24+00:00","og_image":[{"width":1404,"height":791,"url":"https:\/\/blogs.zeiss.com\/digital-innovation\/de\/wp-content\/uploads\/sites\/2\/2021\/01\/202101_WCF.png","type":"image\/png"}],"author":"David Siebert","twitter_card":"summary_large_image","twitter_title":"WCF Alternatives (Part 4) \u2013 Summary","twitter_description":"In the last blog post of the series on alternatives for the Windows Communication Foundation (WCF), we are going to recapitulate and compare them once again.","twitter_misc":{"Written by":"David Siebert","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/wcf-alternatives-part-4\/","url":"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/wcf-alternatives-part-4\/","name":"WCF Alternatives (Part 4) - Summary - ZEISS Digital Innovation Blog","isPartOf":{"@id":"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/#website"},"primaryImageOfPage":{"@id":"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/wcf-alternatives-part-4\/#primaryimage"},"image":{"@id":"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/wcf-alternatives-part-4\/#primaryimage"},"thumbnailUrl":"https:\/\/blogs.zeiss.com\/digital-innovation\/de\/wp-content\/uploads\/sites\/2\/2021\/01\/202101_WCF.png","datePublished":"2021-03-04T09:31:22+00:00","dateModified":"2021-03-04T09:31:24+00:00","author":{"@id":"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/#\/schema\/person\/6b51a72db3cce2762c3e7ba935cf25bf"},"description":"In the last blog post of the series on WCF alternatives, we are going to recapitulate and compare them once again.","breadcrumb":{"@id":"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/wcf-alternatives-part-4\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/blogs.zeiss.com\/digital-innovation\/en\/wcf-alternatives-part-4\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/wcf-alternatives-part-4\/#primaryimage","url":"https:\/\/blogs.zeiss.com\/digital-innovation\/de\/wp-content\/uploads\/sites\/2\/2021\/01\/202101_WCF.png","contentUrl":"https:\/\/blogs.zeiss.com\/digital-innovation\/de\/wp-content\/uploads\/sites\/2\/2021\/01\/202101_WCF.png","width":1404,"height":791},{"@type":"BreadcrumbList","@id":"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/wcf-alternatives-part-4\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/"},{"@type":"ListItem","position":2,"name":"WCF Alternatives (Part 4) \u2013 Summary"}]},{"@type":"WebSite","@id":"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/#website","url":"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/","name":"Digital Innovation Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/#\/schema\/person\/6b51a72db3cce2762c3e7ba935cf25bf","name":"David Siebert","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/#\/schema\/person\/image\/","url":"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/wp-content\/uploads\/sites\/3\/2020\/12\/siebert_david-e1607418544482-150x150.jpg","contentUrl":"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/wp-content\/uploads\/sites\/3\/2020\/12\/siebert_david-e1607418544482-150x150.jpg","caption":"David Siebert"},"description":"David Siebert is Senior Consultant Software Development at ZEISS Digital Innovation. His focus is primarily on .NET development. In addition, he is particularly involved with web technologies and clean code.","url":"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/author\/endavidsiebert\/"}]}},"author_meta":{"display_name":"David Siebert","author_link":"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/author\/endavidsiebert\/"},"featured_img":"https:\/\/blogs.zeiss.com\/digital-innovation\/de\/wp-content\/uploads\/sites\/2\/2021\/01\/202101_WCF-600x338.png","coauthors":[],"tax_additional":{"categories":{"linked":["<a href=\"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/category\/web\/\" class=\"advgb-post-tax-term\">Web<\/a>","<a href=\"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/category\/dot-net\/\" class=\"advgb-post-tax-term\">.NET<\/a>"],"unlinked":["<span class=\"advgb-post-tax-term\">Web<\/span>","<span class=\"advgb-post-tax-term\">.NET<\/span>"]},"tags":{"linked":["<a href=\"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/category\/dot-net\/\" class=\"advgb-post-tax-term\">Microsoft<\/a>","<a href=\"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/category\/dot-net\/\" class=\"advgb-post-tax-term\">distributed collaboration<\/a>","<a href=\"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/category\/dot-net\/\" class=\"advgb-post-tax-term\">WCF<\/a>","<a href=\"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/category\/dot-net\/\" class=\"advgb-post-tax-term\">Windows Communication Foundation<\/a>","<a href=\"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/category\/dot-net\/\" class=\"advgb-post-tax-term\">.NET Framework 3.0<\/a>","<a href=\"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/category\/dot-net\/\" class=\"advgb-post-tax-term\">.NET Remoting<\/a>","<a href=\"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/category\/dot-net\/\" class=\"advgb-post-tax-term\">distributed communication<\/a>","<a href=\"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/category\/dot-net\/\" class=\"advgb-post-tax-term\">distributed application<\/a>","<a href=\"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/category\/dot-net\/\" class=\"advgb-post-tax-term\">communication platform<\/a>","<a href=\"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/category\/dot-net\/\" class=\"advgb-post-tax-term\">ZEISS Digital Innovation<\/a>"],"unlinked":["<span class=\"advgb-post-tax-term\">Microsoft<\/span>","<span class=\"advgb-post-tax-term\">distributed collaboration<\/span>","<span class=\"advgb-post-tax-term\">WCF<\/span>","<span class=\"advgb-post-tax-term\">Windows Communication Foundation<\/span>","<span class=\"advgb-post-tax-term\">.NET Framework 3.0<\/span>","<span class=\"advgb-post-tax-term\">.NET Remoting<\/span>","<span class=\"advgb-post-tax-term\">distributed communication<\/span>","<span class=\"advgb-post-tax-term\">distributed application<\/span>","<span class=\"advgb-post-tax-term\">communication platform<\/span>","<span class=\"advgb-post-tax-term\">ZEISS Digital Innovation<\/span>"]}},"comment_count":"0","relative_dates":{"created":"Posted 5 years ago","modified":"Updated 5 years ago"},"absolute_dates":{"created":"Posted on March 4, 2021","modified":"Updated on March 4, 2021"},"absolute_dates_time":{"created":"Posted on March 4, 2021 9:31 am","modified":"Updated on March 4, 2021 9:31 am"},"featured_img_caption":"","series_order":"","_links":{"self":[{"href":"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/wp-json\/wp\/v2\/posts\/1261","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/wp-json\/wp\/v2\/users\/105"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/wp-json\/wp\/v2\/comments?post=1261"}],"version-history":[{"count":11,"href":"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/wp-json\/wp\/v2\/posts\/1261\/revisions"}],"predecessor-version":[{"id":1383,"href":"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/wp-json\/wp\/v2\/posts\/1261\/revisions\/1383"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/wp-json\/wp\/v2\/media\/1260"}],"wp:attachment":[{"href":"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/wp-json\/wp\/v2\/media?parent=1261"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/wp-json\/wp\/v2\/categories?post=1261"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/wp-json\/wp\/v2\/tags?post=1261"},{"taxonomy":"topics","embeddable":true,"href":"https:\/\/blogs.zeiss.com\/digital-innovation\/en\/wp-json\/wp\/v2\/topics?post=1261"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}