Hypermedia

Nov 7, 2012Download as KEY, PDF4 likes2,552 views

My Hypermedia and ASP.NET Web API talk from Oredev RestBugs sample (for of Howard Dierking's repo) using templates: https://github.com/glennblock/RestBugs Collection+Json: https://github.com/glennblock/collectionjson

Hypermedia and
ASP.NET Web API
Glenn Block
@gblock

What is
Hypermedia? iou s
Prev
Catalog
Embedded links in HTTP Ne
xt
responses which are application
state transitions

What is
Hypermedia?
Embedded links in HTTP
responses which are application
state transitions

What is o va
l
pr

Hypermedia? A p

Ful?llment
Order
Embedded links in HTTP Ca
nc
responses which are application el
lat
io
n
state transitions

What is a
Hypermedia API API
A web API that returns
responses containing
hypermedia

What is a
Hypermedia API
And this is really good

How does a
hypermedia work? API
Server embeds links to
resources

How does a
hypermedia work? Client
Clients identi?es available links
and their associated urls

How does a
hypermedia work?
Client
Client navigates to the chosen link

Hypermedia and
Web API
How do we implement it?

COLLECTION
+JSON HTML

HAL ATOM

Media Types
Hypermedia is conventionally
surfaced via the media type SIREN

Hypermedia can also be
surfaced via headers

Formatters and Media Type

Hypermedia
Formatter

Media Type API
Formatters create media type Formatter Controller
representations from objects
Media Type
Formatters are the key place Formatter
for hypermedia to be rendered

Controller

Media Type
populates a
model with
links

Models
Media Type API
One approach is to have a Formatter Controller
media type speci?c model
Formatter
renders the

The application populates the model and
links

model, and a custom formatter
renders it

Controller

Media Type
returns a set
of DTOs

Templates
Media Type API
Another is to have media type Formatter Controller
speci?c templates.
Formatter

The application returns a model renders
template
with links
passed to a formatter.

The formatter renders using a
a template (like razor)

More information

http://codebetter.com/glennblock
http://amundsen.com/media-types/collection/
http://github.com/howarddierking/restbugs
http://github.com/tavis-software/RestAgent

An API is an interface that allows software programs to communicate with each other. APIs define a set of functions that allow components within a software system to communicate in a standardized way. Traditionally, APIs focused on solving data integration problems by enabling the exchange and sharing of data between different software programs and platforms. Modern organizations now leverage APIs to gain insights from user data on other platforms, quickly develop common tasks, and automate existing processes. Popular examples of APIs include Google Maps, Facebook, and YouTube.

Api presentation updategreti79

This document discusses APIs (Application Programming Interfaces) and how they allow software applications and online services to communicate. APIs are sets of routines, protocols, and tools that allow programs to interact with each other. They transmit data between devices in agreed-upon formats. APIs were initially created to make programming easier by providing reusable building blocks, and now allow things like embedding files from services like �ݺ�ߣShare onto blogs through web APIs. APIs are important because they enable connections and sharing of information between programs and online services.

More Coverage, Better DiagnosticsSmartBear

OSGi Overview TomTom DevDay May 2009Toralf Richter

OSGi is an open specification that defines a modular system and service platform for Java applications. It promotes building applications from loosely coupled and independently versioned bundles that can be dynamically installed, started, stopped, updated, or uninstalled without requiring a reboot. The OSGi specification is maturing for use on the server side, with features being added to support enterprise applications. While tooling is still developing, OSGi allows for robust, high availability applications through clear componentization and hot deployment of bundles.

ŷ�޹��ʰ�Light Lin

speech @ ntu 20111020Light Lin

��20����֮��Light Lin

Node js - Enterprise ClassGlenn Block

Node.js is gaining significant interest for building scalable web applications. Several large companies like LinkedIn, eBay, and Walmart are using Node.js in production for its performance and scalability benefits when handling input/output bound workloads. Node.js allows non-blocking event-driven programming which helps simplify building applications that interact with services, databases, and handle many concurrent connections using little memory. Its large ecosystem of open-source modules also helps speed up development.

REST and the Hypermedia ConstraintInviqa

The document discusses the constraints of REST (REpresentational State Transfer) architectural style. It defines REST as a set of constraints for distributed hypermedia systems. The key constraints are that systems be stateless, cacheable, have a uniform interface, and include hypertext driving application state. The hypermedia constraint requires that hyperlinks define valid state transitions and drive the API, making it RESTful. The document provides examples of how to implement the hypermedia constraint using formats like HTML, Atom, and custom MIME types.

Rest and the hypermedia constraintInviqa

A RESTful API is only truly RESTful if it uses hypermedia to tell us about all the actions that can be performed on the curent resource, allowing us to traverse the API from a single entry point. His session looks at REST and HATEOAS (Hypermedia As The Engine Of Application State) to illustrate good service structure. Ben will use the RESTful file sharing service fdrop.it to illustrate the various examples of how this can be used. This session is recommended for architects and senior developers alike and will give a good grounding in writing excellent, self-explanatory RESTful services.

L11 Service Design and REST?lafur Andri Ragnarsson

This document provides an overview of service design and REST architectures. It discusses key concepts like microservices, APIs, service boundaries, and Conway's Law. It explains that services should be organized around business capabilities and have well-defined interfaces. REST architectural styles are also covered, including the Richardson Maturity Model levels and best practices like resources, uniform interfaces, and HATEOAS. Overall, the document is a useful introduction to designing and modeling service-oriented systems using REST principles.

Trends in Web APIs Layer 7 API Management Workshop LondonCA API Management

API Athens Meetup - API standards 22.03.2016Ivan Goncharov

APIs.guru is a platform that aims to serve as a Wikipedia for web APIs by providing documentation for APIs in one centralized location. It filters out private and unreliable APIs, standardizes documentation into the Swagger 2.0 format, and allows contributors to add and improve API descriptions. APIs.guru also seeks to address challenges of data and schema incompatibility between APIs by developing a system of common scalar and complex data types that can be referenced and converted between APIs.

Representational State TransferAlexei Skachykhin

Rest assuredYaniv Rodenski

This document discusses the evolution of web APIs from SOAP to RESTful architectures. It covers the basics of REST including the Richardson maturity model, use of HTTP verbs and status codes, hypermedia, and content negotiation. Caching techniques are also discussed as a means of improving scalability. The overall summary is that HTTP provides a powerful application protocol for building web APIs and REST architectures allow these APIs to better leverage the inherent scaling capabilities of the web.

Introduction to APIrajnishjha29

The document discusses APIs, defining them as interfaces that allow applications to communicate and share data over a network. It notes that APIs act as an interface between clients and servers, exposing backend data through operations, inputs, outputs, and data types. The document also outlines the benefits of APIs in standardizing communication and enabling reusability. It introduces common API terminology and types, focusing on web APIs which are the most widely used.

Modern APIs: The Non-Technical User��s Guide | The Enterprise WorldEnterprise world

Making Sense of Hypermedia APIs �C Hype or Reality?Akana

advanced computer network, about computerjishukurmi81

Building Self Documenting HTTP APIs with CQRSDerek Comartin

Does your HTTP API expose your database structure? HTTP endpoints that represent your database entities couples your consuming clients to the internals of your application. Making it much harder to change your API. Go beyond serializing a database row into json by leveraging CQRS. Start designing an HTTP API like a regular HTML website. Bringing the concepts of HTML links and forms to your API allows your clients to consume it with ease. Attendees will learn how to design an HTTP API by leveraging CQRS and hypermedia to decouple their core application from their HTTP API.

Digital Methods Winterschool 2012: API - Interfaces to the CloudDigital Methods Initiative

This document discusses APIs (application programming interfaces) and their role in web development. It defines APIs as specifications that allow software components to communicate with each other. On the web, APIs typically use HTTP requests and JSON/XML responses to allow access to structured data and services. This has enabled the combination of multiple online services into new applications. As more websites provide APIs, the web itself is becoming a platform that outside developers can build upon. However, there are also limitations and ethical issues to consider regarding APIs, including restricted access, changing formats, and debates around scraping data versus using official APIs.

O'Reilly SACon San Jose, CA - 2019 - API design tutorialTom Hofte

This document discusses mapping a domain model to a RESTful web API. It begins with an introduction and agenda for the presentation. It then covers discovering the API domain by identifying domain entities, operations, and relationships. This involves analyzing use cases, events, and domain expert input. The document provides an example of mapping verbs and nouns to entities and operations. It emphasizes grouping related concepts into bounded contexts. The goal is to learn how to map the domain model to REST resources, representations, and operations to define the API interface.

Microservices&ap imanagementpramodkumards

The document discusses microservices and API management. It defines microservices as small, independent processes communicating via APIs to compose complex applications. Benefits include improved modularity, scalability, and fault isolation. API management provides tools to publish, secure, monitor, and analyze APIs. It allows enterprises to expose APIs internally or externally in a controlled manner. The document outlines considerations around microservices and features of API management systems.

ConnectME: connecting content for future TV & videoconnectme_project

Today, media material is increasingly digital and shifting to delivery via IP and the Web, including cultural artifacts or broadcast television. This opens up the possibility of new services deriving added value from such material by combining it with other material elsewhere on the Web which is related to it or enhances it in a meaningful way, to the benefit of the owner of the original content, the providers of the content enhancing it and the end consumer who can access and interact with these new services. Since the services are built around providing new experiences through connecting different related media together, we consider such services to be Connected Media Experiences (ConnectME). In particular, much rich depth of information and service functionality associated to content in video is not derived today due to a lack of suitably granular description of video, including linking of video objects to the concepts they represent. For example, news reports about local tourism and events are not linked to tourist information and event�Crelated services which a viewer may (spontaneously) wish to access and make use of. The technological result of the ConnectME project will be an end-to-end service platform to host those added-value services over different networks, providing the common required functionality of each service: multimedia annotation and subsequent enrichment with related content from the Web, combined with the packaging and delivery of synchronized multimedia presentations to the end device. At the device, intuitive user interfaces must be developed so that the selection of on-screen objects and the browsing of the associated content can be done in a non-disruptive and intuitive fashion. As a result, ConnectME facilitates a new interactive media experience built on top of the convergence of TV/video and the Web.

API Days Berlin highlightsAndrii Gakhov

Apply API Governance to RESTful Service APIs using WSO2 Governance Registry a...WSO2

This document discusses applying API governance to RESTful APIs using WSO2 Governance Registry and API Manager. It promotes these products for designing, implementing, and managing APIs at design time and runtime. Key points include establishing consumer/subscriber relationships, implementing versioning, and ensuring operational governance through monitoring, analytics, and quality of service controls.

Understanding API Architectures: Web API vs. Minimal API �C An In-Depth Compar...Polyxer Systems

apidays London 2023 - Autonomous Agents, Zdenek Nemec, superface.aiapidays

apidays London 2023 - APIs for Smarter Platforms and Business Processes September 13 & 14, 2023 Autonomous Agents: Forget about APIs Zdenek Nemec, Founder & CTO, superface.ai ------ Check out our conferences at https://www.apidays.global/ Do you want to sponsor or talk at one of our conferences? https://apidays.typeform.com/to/ILJeAaV8 Learn more on APIscene, the global media made by the community for the community: https://www.apiscene.io Explore the API ecosystem with the API Landscape: https://apilandscape.apiscene.io/

Api Strat Portland 2017 Serverless Extensibility talkGlenn Block

The document discusses the evolution of extensibility for software-as-a-service (SaaS) products. It describes how extensibility was easier when companies hosted their own software but became more challenging with the rise of cloud computing and SaaS. Webhooks revolutionized SaaS extensibility by allowing third-party code to run isolated from the SaaS, but customers still had to host and manage the code. The document introduces serverless extensibility as the next step, where SaaS products can directly invoke third-party extensions running on serverless platforms without requiring customer management. Examples of serverless extensibility include Auth0 Extend and integrations with platforms like AWS Lambda.

Serverless ExtensibilityGlenn Block

Serverless extensibility allows third-party code to be securely executed within a Software as a Service (SaaS) product using serverless functions. This provides benefits over traditional webhooks by handling hosting and monitoring, and allowing custom code to be created and run directly within the SaaS product using an inline code editor. Serverless extensibility benefits both customers by lowering costs and barriers to customization, and SaaS providers by improving customer retention and enabling new integration possibilities. However, concerns remain around ensuring custom code is properly versioned, debugged and secured to prevent issues like vendor lock-in.

More Related Content

Similar to Hypermedia (20)

REST and the Hypermedia ConstraintInviqa

Rest and the hypermedia constraintInviqa

L11 Service Design and REST?lafur Andri Ragnarsson

Trends in Web APIs Layer 7 API Management Workshop LondonCA API Management

API Athens Meetup - API standards 22.03.2016Ivan Goncharov

Representational State TransferAlexei Skachykhin

Rest assuredYaniv Rodenski

Introduction to APIrajnishjha29

Modern APIs: The Non-Technical User��s Guide | The Enterprise WorldEnterprise world

Making Sense of Hypermedia APIs �C Hype or Reality?Akana

advanced computer network, about computerjishukurmi81

Building Self Documenting HTTP APIs with CQRSDerek Comartin

Digital Methods Winterschool 2012: API - Interfaces to the CloudDigital Methods Initiative

O'Reilly SACon San Jose, CA - 2019 - API design tutorialTom Hofte

Microservices&ap imanagementpramodkumards

ConnectME: connecting content for future TV & videoconnectme_project

API Days Berlin highlightsAndrii Gakhov

Apply API Governance to RESTful Service APIs using WSO2 Governance Registry a...WSO2

Understanding API Architectures: Web API vs. Minimal API �C An In-Depth Compar...Polyxer Systems

apidays London 2023 - Autonomous Agents, Zdenek Nemec, superface.aiapidays

REST and the Hypermedia ConstraintInviqa

Rest and the hypermedia constraintInviqa

L11 Service Design and REST?lafur Andri Ragnarsson

Trends in Web APIs Layer 7 API Management Workshop LondonCA API Management

API Athens Meetup - API standards 22.03.2016Ivan Goncharov

Representational State TransferAlexei Skachykhin

Rest assuredYaniv Rodenski

Introduction to APIrajnishjha29

Modern APIs: The Non-Technical User��s Guide | The Enterprise WorldEnterprise world

Making Sense of Hypermedia APIs �C Hype or Reality?Akana

advanced computer network, about computerjishukurmi81

Building Self Documenting HTTP APIs with CQRSDerek Comartin

Digital Methods Winterschool 2012: API - Interfaces to the CloudDigital Methods Initiative

O'Reilly SACon San Jose, CA - 2019 - API design tutorialTom Hofte

Microservices&ap imanagementpramodkumards

ConnectME: connecting content for future TV & videoconnectme_project

API Days Berlin highlightsAndrii Gakhov

Apply API Governance to RESTful Service APIs using WSO2 Governance Registry a...WSO2

Understanding API Architectures: Web API vs. Minimal API �C An In-Depth Compar...Polyxer Systems

apidays London 2023 - Autonomous Agents, Zdenek Nemec, superface.aiapidays

More from Glenn Block (18)

Api Strat Portland 2017 Serverless Extensibility talkGlenn Block

Serverless ExtensibilityGlenn Block

Deploying web apis on core clr to dockerGlenn Block

This document provides an overview of .NET Core, ASP.NET 5, and Docker. It introduces .NET Core as a cross-platform version of .NET that allows side-by-side app versioning. ASP.NET 5 is the new version of ASP.NET that is modular and runs on .NET Core, supporting Web UI and APIs. Docker is a tool that allows packaging apps and dependencies into standardized containers to enable portable development environments. The document provides links for additional information on these topics and an example contact API project using these technologies on GitHub.

HTTP Event Collector, Simplified Developer LoggingGlenn Block

Liberate your Application LoggingGlenn Block

A Lap Around Developer Awesomeness in Splunk 6.3Glenn Block

The document discusses new developer features in Splunk 6.3, including the HTTP Event Collector for sending events directly to Splunk, custom alert actions for integrating with external systems, and improved custom search commands. It also demonstrates some of these features, such as sending events using the HTTP Event Collector and creating custom alert actions. Additional sessions are recommended for learning more about modular inputs, reference apps, and other developer tools in Splunk.

Islands of Node in a sea of big dataGlenn Block

In this presentation, Glenn Block discusses how Splunk uses node.js in its products. Surprising, huh? Node shows up in various islands of Splunk��s architecture from the Splunk Server, to middleware components, and finally in the SDKs. The focus here is on real world usage, the specific places where we chose to use node and why, as well as the team��s experiences deploying it into production. What��s Splunk? It��s a product designed for data ingest and query for massive realtime data work loads. It is used by some of the largest organizations in the world.

Splunk and nodeGlenn Block

Splunk, a smorgasboard for developing big data solutions Glenn Block

This document discusses developing big data solutions using Splunk. It provides an overview of Splunk's capabilities for collecting, analyzing and visualizing machine data from various sources. It also describes Splunk's developer platform for building custom apps and extensions, searching data, and sending data to Splunk from various platforms and languages. The document directs readers to Splunk's online resources for tutorials, code samples and support.

Splunk's api how we built itGlenn Block

Splunk for net developersGlenn Block

This document discusses tools for .NET developers to use Splunk. It introduces the Splunk SDK for C#, which allows developers to integrate with and extend Splunk using a modern asynchronous API. Logging libraries are presented that allow .NET applications to log directly to Splunk using common loggers like log4net and NLog. A Visual Studio extension is demonstrated that streamlines using these Splunk libraries in development. Code samples and demos show logging to Splunk and creating modular inputs.

Dev sum hypemedia talkGlenn Block

The document discusses hypermedia and how it can be used to help clients navigate an API. It defines hypermedia as control information provided by an API to clients through links and forms. These controls allow clients to identify available actions and activate them to move between states. The document provides an example of how this could work in a issue tracking API, allowing clients to retrieve, open, close and search for issues. It also recommends implementing hypermedia with ASP.NET Web API and provides additional resources for further information.

Getting your head around big dataGlenn Block

The document provides an overview of the history of data from ancient times to modern technologies and the challenges of harnessing big data. It discusses how data is generated from a variety of sources at different frequencies and velocities and not all data is useful or accurate, highlighting issues of veracity. It then presents solutions for storing, processing, analyzing and visualizing large datasets including MapReduce, high-scale databases, distributed processing, data visualization tools, and end-to-end platforms.

EdgeGlenn Block

This document discusses Edge, an open source module for Node.js that allows Node.js applications to leverage .NET capabilities by calling .NET libraries and services. Edge allows Node.js code to call into .NET code and .NET code to call back into Node.js code in a non-blocking way within the same process. It supports multiple .NET languages like C#, F# and Powershell. Edge enables access to Windows capabilities like the event log, registry, performance counters and more. It is extensible via additional Edge modules for SQL, Powershell, and other languages/platforms. The document provides code examples and links to the Edge GitHub repository and additional Edge modules.

Realtime Conf - Lightning node.js devGlenn Block

The document discusses Glenn Block who is a node.js developer at Microsoft who develops infrastructure, tools and libraries for node.js on Azure and supports the node.js community. It provides information on deploying and managing node.js applications on Azure including commands for deploying from Git repositories, managing virtual machines, and building mobile backends with node.js and Windows Azure Mobile Services.

Node js on Windows AzureGlenn Block

Building systems with restGlenn Block

Building Systems with REST discusses how HTTP differs from RPC and how it enables intermediaries through its use of resources and representations. The document outlines how HTTP is a transfer protocol rather than a transport protocol and how following its semantics allows functionality through firewalls. It advocates for building systems according to REST principles by decoupling concerns and focusing on resources, representations, and hypermedia.

Building Extensible RIAs with MEFGlenn Block

Api Strat Portland 2017 Serverless Extensibility talkGlenn Block

Serverless ExtensibilityGlenn Block

Deploying web apis on core clr to dockerGlenn Block

HTTP Event Collector, Simplified Developer LoggingGlenn Block

Liberate your Application LoggingGlenn Block

A Lap Around Developer Awesomeness in Splunk 6.3Glenn Block

Islands of Node in a sea of big dataGlenn Block

Splunk and nodeGlenn Block

Splunk, a smorgasboard for developing big data solutions Glenn Block

Splunk's api how we built itGlenn Block

Splunk for net developersGlenn Block

Dev sum hypemedia talkGlenn Block

Getting your head around big dataGlenn Block

EdgeGlenn Block

Realtime Conf - Lightning node.js devGlenn Block

Node js on Windows AzureGlenn Block

Building systems with restGlenn Block

Building Extensible RIAs with MEFGlenn Block

Hypermedia

1. Hypermedia and ASP.NET Web API Glenn Block @gblock

2. Hypermedia 101

3. What is Hypermedia? iou s Prev Catalog Embedded links in HTTP Ne xt responses which are application state transitions

4. What is Hypermedia? Embedded links in HTTP responses which are application state transitions

5. What is Hypermedia? Embedded links in HTTP responses which are application state transitions

6. What is o va l pr Hypermedia? A p Ful?llment Order Embedded links in HTTP Ca nc responses which are application el lat io n state transitions

7. What is Hypermedia? Not a new concept

8. What is Hypermedia? Not a new concept

9. What is Hypermedia? Not a new concept

10. What is Hypermedia? Not a new concept

11. What is Hypermedia? Not a new concept

12. What is Hypermedia? Not a new concept

13. What is a Hypermedia API API A web API that returns responses containing hypermedia

14. What is a Hypermedia API Not this

15. What is a Hypermedia API This is better

16. What is a Hypermedia API And this is really good

17. How does a hypermedia work? API Server embeds links to resources

18. How does a hypermedia work? Client Clients identi?es available links and their associated urls

19. How does a hypermedia work? Client Client navigates to the chosen link

20. Hypermedia The concept is simple

21. Hypermedia and Web API How do we implement it?

22. COLLECTION +JSON HTML HAL ATOM Media Types Hypermedia is conventionally surfaced via the media type SIREN Hypermedia can also be surfaced via headers

23. Formatters and Media Type Hypermedia Formatter Media Type API Formatters create media type Formatter Controller representations from objects Media Type Formatters are the key place Formatter for hypermedia to be rendered

24. Controller Media Type populates a model with links Models Media Type API One approach is to have a Formatter Controller media type speci?c model Formatter renders the The application populates the model and links model, and a custom formatter renders it

25. Controller Media Type returns a set of DTOs Templates Media Type API Another is to have media type Formatter Controller speci?c templates. Formatter The application returns a model renders template with links passed to a formatter. The formatter renders using a a template (like razor)

26. Rest Agent Client

27. More information http://codebetter.com/glennblock http://amundsen.com/media-types/collection/ http://github.com/howarddierking/restbugs http://github.com/tavis-software/RestAgent

Editor's Notes

#2: \n
#3: \n
#4: \n
#5: \n
#6: \n
#7: \n
#8: \n
#9: \n
#10: \n
#11: \n
#12: \n
#13: \n
#14: \n
#15: \n
#16: \n
#17: \n
#18: \n
#19: \n
#20: \n
#21: \n
#22: \n
#23: \n

�ݺ�ߣ

Hypermedia

Recommended

More Related Content

Similar to Hypermedia (20)

More from Glenn Block (18)

Hypermedia

Editor's Notes