REST and ASP.NET Web API (Milan)

Oct 20, 2012Download as PPTX, PDF5 likes4,944 views

This document discusses REST (REpresentational State Transfer) and ASP.NET Web API. It begins by defining REST as an architectural style for building distributed hypermedia systems and emphasizing that REST in practice relies on HTTP. The document then covers basic REST concepts like resources, identifiers, representations, and verbs. It discusses HATEOAS and how hypermedia links APIs together. Finally, it provides an overview of ASP.NET Web API, describing how it maps to REST concepts and allows building RESTful web services and clients in .NET.

about/jefclaes

@jefclaes
http://jefclaes.be

The acronym

REpresentational State Transfer

REST is NOT...

• ‘Webservices using JSON’

• A protocol
• A design pattern

REST is..

“An architectural style for building
distributed hypermedia systems.”

In theory...

REST isn’t limited to a
single message protocol.

But in practice...

It’s all about HTTP.

So now you wonder..

Haven’t we been successfully building
web services using SOAP and HTTP
for over 10 years ?

Resources
• An entity, item, or just a thing you want to expose.
• REST is Resource Oriented.

Identifiers
Something that identifies a resource.

ID: 1
URI: http://batman.com/api/batresource/1

Representations
View on a resource’s state at an instant in time.

XML: JSON: Other:

<BatResource> { • Images
<Id>1</Id> "Id":"1", • CSV
<Description> "Description":"Bataran • Custom
Batarang g", • ...
</Description> "Quantity":1
<Quantity>1</Quantity> }
</BatResource>

Verbs
Actions on a resource.

Create Read Update Delete
POST GET PUT DELETE

Hypermedia
HATEOAS: Hypermedia as the engine of application state
Linking your API together
{
"Id":"1",
"Description":"Batarang",
“Quantity":1,
“Links":
{
"Rel":"Next",
"Href":"http://localhost:8080/api/batresource/2"
}
}

HypeRRRRRRRmedia
• Relations
• Embedded resources
• Reference data
• Redistribution of effort
• Reduction of payload size
• Reflow
• Restriction of functionality

Architecture of the WEB
ARCHITECTURAL VALUES

Scalability and performance
Yes, text-based, synchronous, request-response
can be performant.
• Stateless
• Caching

Loose coupling
• No transactions
• No state
• No guarantees
• HATEOAS
• No specific technology stack

Consistency and Uniformity

Everybody knows how to use HTTP
–Constraints
–Well understood semantics

Richardson’s Maturity Model

Level 0: POX

Level 1: Resources

Level 2: HTTP verbs
Level 3: Hypermedia

What?

.NET HTTP framework
(4.0)

for building RESTful services.

When?
• HTTP Services (WCF)
• AJAX back-ends

Options
• WebHost
– ASP.NET MVC: Click, click, click
• SelfHost

Representations
application/json
text/xml

Summary
• REST
– Concepts
– Architectual values
– Left overs
• ASP.NET Web API
– Server
– Client

There is more
Slides and source on http://jefclaes.be

Extensibility?
• Next session (Raffaele Rialdi)
• http://github.com/JefClaes/aspnet-webapi-samples-tunisia

Please rate this session
Scan the code, go online, rate this session

REST is an architectural style for building distributed hypermedia systems based on HTTP. The core concepts of REST include resources identified by URIs, representations of those resources exchanged via standard HTTP methods like GET, PUT, POST, and DELETE. Effective REST APIs follow architectural values like performance, scalability, loose coupling, and consistency by making resources and relationships between them accessible over HTTP. ASP.NET Web API is a framework for building RESTful services on .NET. It allows creating HTTP-based services using controllers and attributes, supports content negotiation for XML and JSON, and includes features for error handling, message handlers, dependency injection, and testing.

Overview of Rest Service and ASP.NET WEB APIPankaj Bajaj

The document provides an overview of REST services and ASP.NET Web API. It defines REST and its features, describing how REST services use HTTP verbs and are resource-oriented. It then explains ASP.NET Web API, how it makes building HTTP services easy in .NET, and compares REST to SOAP and ASP.NET Web API to WCF. The document aims to explain REST and how ASP.NET Web API can be used to create RESTful services.

Excellent rest using asp.net web apiMaurice De Beijer [MVP]

This document discusses REST and ASP.NET WebAPI. It begins with introductions to REST, the Richardson Maturity Model, and ASP.NET WebAPI. It then covers key WebAPI concepts like controllers, routes, content negotiation, and HTTP methods. A large portion discusses hypermedia and the OData protocol for building hypermedia-driven REST services with WebAPI and Entity Framework. It provides examples of OData queries, metadata support, and routing. The document concludes with recommendations for further reading and questions.

ASP.NET WEB API TrainingChalermpon Areepong

This document outlines an advanced ASP.NET Web API course agenda. The course will cover topics like model binding and custom formatters, OData, asynchronous operations, and performance improvement techniques. The first part of the course will introduce web technologies like HTTP, JSON, XML, and provide an overview of ASP.NET Web API. Later sections will demonstrate how to work with model binding, custom formatters, OData queries, and async logic. The course will also cover security implementations like basic authentication and token validation, as well as performance techniques such as message compression and high-performance JavaScript serialization.

ASP.NET Mvc 4 web apiTiago Knoch

Introduction to the Web APIBrad Genereaux

The document provides an introduction to web APIs and REST. It defines APIs as methods to access data and workflows from an application without using the application itself. It describes REST as an architectural style for APIs that uses a client-server model with stateless operations and a uniform interface. The document outlines best practices for REST APIs, including using HTTP verbs like GET, POST, PUT and DELETE to perform CRUD operations on resources identified by URIs. It also discusses authentication, authorization, security concerns and gives examples of popular REST APIs from Facebook, Twitter and other services.

Web API BasicsLearnNowOnline

This document discusses building web APIs with ASP.NET Web API. It covers the objectives of seeing how REST and web services can access data, building a first Web API service, using routing conventions, and modifying services for CRUD operations. The agenda includes explaining what Web API is, creating a first service, routing, and creating a service for CRUD. It also defines REST concepts like HTTP methods GET, POST, PUT, and DELETE and their typical uses for selecting, adding, editing, and deleting data.

The ASP.NET Web API for BeginnersKevin Hazzard

This document provides an overview and examples for building web APIs with ASP.NET Web API. It discusses Richardson maturity levels, the HTTP request/response processing pipeline, attribute routing, and implementing handlers. It also demonstrates testing Web API controllers with the WebApiTestClient without requiring a running host. Key topics include building controllers, adding OData query support, creating an authorization handler, and following the Arrange, Act, Assert pattern for tests.

Web services - A Practical ApproachMadhaiyan Muthu

ASP.NET Web API and HTTP FundamentalsIdo Flatow

ASP.NET Web API is the de facto framework for building HTTP-based services in the .NET ecosystem. With its WCF and MVC lineage, Web API brings to the table better architecture, easier configuration, increased testability, and as always, it's customizable from top to bottom. But to properly use Web API it is not enough to get familiar with its architecture and API, you also need to really understand what HTTP is all about. HTTP is the most common application layer protocol in the world, and yet, not many web developers are familiar with HTTP concepts such as of chunking, caching, and persisted connections. In this full-day tutorial, we will focus on designing and implementing HTTP-based services with ASP.NET Web API, and you will learn how to better use it to implement the features provided by HTTP.

Designing REST services with Spring MVCSerhii Kartashov

Webservices Overview : XML RPC, SOAP and RESTPradeep Kumar

This document discusses different approaches to designing web services, including XML-RPC, SOAP, and REST. XML-RPC uses XML to encode calls and HTTP POST for transport. SOAP is more powerful than XML-RPC and uses WSDL and supports different protocols. REST is an architectural approach that uses HTTP methods to perform CRUD operations on resources identified by URIs, following principles like being stateless. The document provides examples of requests and responses for each approach and discusses their advantages and disadvantages.

Web ServicesKatrien Verbert

This document provides an overview of web services, including RESTful and SOAP-based services. It discusses key concepts such as APIs, URIs, HTTP methods, XML/JSON data formats. For RESTful services, it covers the main design principles of being stateless, using explicit HTTP methods, and having directory-like URIs. For SOAP-based services, it describes the roles of SOAP, WSDL, and UDDI in defining and discovering services. The document also provides examples and comparisons of RESTful and SOAP-based approaches.

Restful webserviceDong Ngoc

ASP.NET WEB APIThang Chung

This document provides an overview of ASP.NET Web API including: - A model of REST maturity with 4 levels from plain XML to hypermedia controls. - The purpose of Web APIs as RESTful HTTP services compared to SOAP. - Mapping from WCF to the Web API model using controllers, actions, and routing instead of endpoints. - Features like content negotiation, model binding, and dependency injection supported in the Web API stack.

REST - Representational state transferTricode (part of Dept)

The document provides an overview of Representational State Transfer (REST), describing its key concepts and constraints. REST was developed as an architectural style for the World Wide Web with the goals of making the web protocol standards more effective. The core REST constraints include being client-server, stateless, cacheable, using a uniform interface, operating as a layered system, and optionally supporting code on demand. Examples are provided of how REST has been applied through resource-oriented architectures and how it differs from service-oriented architectures.

Soap and restful webserviceDong Ngoc

- SOAP and RESTful web services are two common approaches for building web services. SOAP uses XML and web-related standards like HTTP, SMTP, and SOAP. RESTful services are based on REST architectural principles and use HTTP and common data formats like JSON and XML. - The document outlines the specifications, implementations, and differences between SOAP and RESTful web services. It discusses topics like SOAP vs REST characteristics, WSDL and SOAP message structure, JAX-WS and JAX-RS annotations for building web services, and considerations for when to use each approach.

REST & RESTful Web ServicesHalil Burak Cetinkaya

Rest & RESTful WebServicesPrateek Tandon

Restful webservicesLuqman Shareef

The document discusses RESTful web services and compares them to SOAP-based web services. It defines RESTful web services and outlines their key characteristics, including using standard HTTP methods to perform operations on resources identified by URIs. The document provides examples of building RESTful web services with JAX-RS and discusses arguments for using RESTful approaches over SOAP-based services, noting REST's simplicity, flexibility and performance advantages.

Restful web services pptOECLIB Odisha Electronics Control Library

The document provides an overview of a seminar on RESTful web services. It discusses what REST is, its characteristics and principles, and compares RESTful architectures to SOAP. Key points covered include how REST focuses on a system's resources and how they are addressed and transferred over HTTP, the client-server interaction style of REST, and advantages of REST like scalability and loose coupling between components.

Best Practices in Web Service DesignLorna Mitchell

REST & RESTful Web ServiceHoan Vu Tran

An Overview of Web Services: SOAP and REST Ram Awadh Prasad, PMP

Consuming RESTful services in PHPZoran Jeremic

Here are the key steps to load data from a RESTful service using AJAX and jQuery: 1. Make an AJAX GET request to the REST API endpoint using jQuery.ajax() or jQuery.getJSON(). 2. Specify the URL, set the data type to "json", and provide a success callback. 3. On success, the JSON response will be passed to the callback function where it can be used to update the UI. 4. Parse the JSON response into a JavaScript object for easy access to the data. 5. Update the HTML using the jQuery DOM manipulation methods like html(), text(), etc. So in summary - make an AJAX GET, parse the JSON response,

Best Practice in Web Service DesignLorna Mitchell

This document provides an overview and best practices for API design. It discusses when to build an API, such as to share data between apps or give users control over their data. It covers HTTP fundamentals like requests and responses, status codes, headers, and verbs. It also discusses different service types like RPC and RESTful services. The document provides tips on design considerations for APIs like target audience, statelessness, versioning, error handling, and access control.

Rest api design by george reesebuildacloud

As you go into the cloud, the applications you are building will often be built on service-oriented architectures that communicate through RESTful APIs. Where API design and development used to be an uncommon thing, today it has become a basic application requirement. George Reese will cover the basic considerations in designing and implementing an API for your applications. George Reese is the author of a number of technology books and a regular speaker on RESTful APIs, cloud computing, Java, and database systems. His most recent books are The REST API Design Handbook and O’Reilly’s Cloud Application Architectures. Professionally, he is the Executive Director of Cloud Computing at Dell as a result of Dell's recent acquisition of Enstratius, a company George co-founded. George has also led a number of Open Source projects, including several MUD libraries and the Imaginary Home home automation libraries for Java. He is also the primary maintainer of Dasein Cloud, a cloud abstraction API for Java. George holds a BA from Bates College in Maine and an MBA from the Kellogg School of Management at Northwestern University.

Web Services TutorialLorna Mitchell

The document provides an introduction and overview of building and consuming web services. It begins with defining what a web service is and discussing common web service architectures and types, including RESTful and RPC services. It then covers topics like HTTP, data formats like JSON and XML, and how to build a simple PHP-based web service that returns data in various formats depending on the Accept header. The document also discusses consuming web services using PHP libraries like cURL and Pecl_HTTP. It includes examples of building and consuming a SOAP web service in PHP. Finally, it discusses building RESTful web services and routing requests in PHP.

OAuth-as-a-service using ASP.NET Web API and Windows Azure Access ControlMaarten Balliauw

This document summarizes a presentation about building an OAuth-as-a-service API using ASP.NET Web API and Windows Azure. The presentation introduces APIs and their benefits, describes API characteristics like HTTP verbs and status codes, demonstrates how to build an API with ASP.NET Web API, discusses securing APIs with OAuth2 and using Windows Azure Access Control for OAuth delegation to manage authentication. The key takeaways are that APIs are becoming the new way applications connect to services, they are valuable, should use HTTP, and ASP.NET Web API and Azure ACS can help build and secure OAuth-based APIs.

Unleash the power of HTTP with ASP.NET Web APIFilip W

This document provides an overview of ASP.NET Web API, a framework for building HTTP services and applications on the Microsoft stack. It discusses how Web API simplifies and standardizes the HTTP area, supports building RESTful and RPC-style APIs, and can be self-hosted without IIS. Key features highlighted include the new HTTP message-based object model, support for content negotiation in different formats like JSON and XML, and routing of API endpoints to controller actions.

More Related Content

What's hot (20)

Web services - A Practical ApproachMadhaiyan Muthu

ASP.NET Web API and HTTP FundamentalsIdo Flatow

Designing REST services with Spring MVCSerhii Kartashov

Webservices Overview : XML RPC, SOAP and RESTPradeep Kumar

Web ServicesKatrien Verbert

Restful webserviceDong Ngoc

ASP.NET WEB APIThang Chung

REST - Representational state transferTricode (part of Dept)

Soap and restful webserviceDong Ngoc

REST & RESTful Web ServicesHalil Burak Cetinkaya

Rest & RESTful WebServicesPrateek Tandon

Restful webservicesLuqman Shareef

Restful web services pptOECLIB Odisha Electronics Control Library

Best Practices in Web Service DesignLorna Mitchell

REST & RESTful Web ServiceHoan Vu Tran

An Overview of Web Services: SOAP and REST Ram Awadh Prasad, PMP

Consuming RESTful services in PHPZoran Jeremic

Best Practice in Web Service DesignLorna Mitchell

Rest api design by george reesebuildacloud

Web Services TutorialLorna Mitchell

Web services - A Practical ApproachMadhaiyan Muthu

ASP.NET Web API and HTTP FundamentalsIdo Flatow

Designing REST services with Spring MVCSerhii Kartashov

Webservices Overview : XML RPC, SOAP and RESTPradeep Kumar

Web ServicesKatrien Verbert

Restful webserviceDong Ngoc

ASP.NET WEB APIThang Chung

REST - Representational state transferTricode (part of Dept)

Soap and restful webserviceDong Ngoc

REST & RESTful Web ServicesHalil Burak Cetinkaya

Rest & RESTful WebServicesPrateek Tandon

Restful webservicesLuqman Shareef

Restful web services pptOECLIB Odisha Electronics Control Library

Best Practices in Web Service DesignLorna Mitchell

REST & RESTful Web ServiceHoan Vu Tran

An Overview of Web Services: SOAP and REST Ram Awadh Prasad, PMP

Consuming RESTful services in PHPZoran Jeremic

Best Practice in Web Service DesignLorna Mitchell

Rest api design by george reesebuildacloud

Web Services TutorialLorna Mitchell

Viewers also liked (20)

OAuth-as-a-service using ASP.NET Web API and Windows Azure Access ControlMaarten Balliauw

Unleash the power of HTTP with ASP.NET Web APIFilip W

Introdução ao ASP .NET Web APIVinicius Mussak

Building modern web sites with ASP .Net Web API, WebSockets and RSignalAlessandro Pilotti

My session at ITCamp.ro 2012: Web site development is an ever changing landscape. Thanks to the latest web browser technologies it's possible to create highly responsive single page applications, requiring a new approach to design and development on the server side. During this session we'll see ho to use .Net technologies to get the best out of the new Web API, WebSockets and the excellent RSignal framework.

ASP.net Image SlideshowHock Leng PUAH

What's new in Angular 2?Alfred Jett Grandeza

Angular 2 introduced many changes from Angular 1 including components instead of directives, templates instead of views, and services instead of factories. It uses TypeScript for static typing and classes. Key features include components, data binding with property and event binding, lifecycle hooks, dependency injection, and routing. Components are the fundamental building block and define templates, styles, and logic. Data binding synchronizes templates and classes. Observables replaced promises for asynchronous operations.

Introduction to AngularJSCollaboration Technologies

AngularJS is a JavaScript framework made by Google for building complex client-side applications. Angular.js is a MVW (Model-View-Whatever) open-source JavaScript web framework that facilitates the creation of single-page applications (SPA) and data-driven apps. Angular projects have a somewhat different structure than other JavaScript MVC frameworks, but it can be highly modular and easy to maintain once you understand the structure.

Introduction to HTML4Collaboration Technologies

OAuth-as-a-service using ASP.NET Web API and Windows Azure Access Control - W...Maarten Balliauw

API’s are the new apps. They can be consumed by everyone using a web browser or a mobile application on their smartphone or tablet. How would you build your API if you want these apps to be a full-fledged front-end to your service without compromising security? In this session, Maarten will explain how to build an API using the ASP.NET Web API framework and how the Windows Azure Access Control service can be used to almost completely outsource all security and OAuth-related tasks.

Web Service Implementation Using ASP.NETPonraj

The document provides an overview of web service implementation using ASP.NET. It defines web services as software components that can be published, located, and run over the Internet using XML. The key points covered include: how web services work by allowing client applications to request and use classes and methods hosted on a web server; the technologies that power web services including the web, XML, and service-oriented architecture (SOA); how to create a basic web service in ASP.NET and test it using a client application.

C O R B A Unit 4Roy Antony Arnold G

The document discusses distributed systems and CORBA (Common Object Request Broker Architecture). It provides an overview of CORBA architecture including its object model, object request broker, interface definition language, client/server communication model using object references, and stubs and skeletons. It also compares CORBA to other distributed computing technologies like DCOM and discusses their similarities and differences.

ASP, ASP.NET, JSP, COM/DCOMAashish Jain

Dcom vs. corbaMohd Arif

DCOM and CORBA are distributed object computing architectures that allow objects to communicate remotely. Both use a three-layer architecture - a top layer for programming interfaces, a middle remoting layer, and a bottom wire protocol layer. Key differences are that DCOM supports multiple interfaces per object while CORBA inherits all interfaces from a common base class, and DCOM's wire protocol is tied to RPC while CORBA's is not. Overall they provide similar distributed object capabilities with some differences in implementation details.

OAuth-as-a-serviceusing ASP.NET Web API and Windows Azure Access ControlMaarten Balliauw

Concepts of Asp.Netvidyamittal

This document provides an agenda for a presentation on ASP.NET fundamentals including programming models, design goals, architecture, and CLR services. It discusses how ASP.NET unifies programming models and simplifies development. It describes the Common Language Runtime, including design goals to simplify development and deployment while providing a robust execution environment. It also summarizes CLR services like type safety, memory management, and metadata.

Asp.netNaveen Sihag

1. ASP.NET uses the CLR to replace the existing ISAPI/ASP infrastructure of IIS with a more efficient framework for servicing HTTP requests. It also provides its own framework for compilation, execution, and building user interfaces. 2. ASP.NET is both an evolution of the ASP programming model as well as a revolution, introducing features like compiled pages, separation of code and HTML, server-side controls, and web services. 3. In ASP.NET, every page is compiled into an assembly the first time it is accessed. Subsequent requests use the compiled assembly for improved performance unless the source files have changed.

OAuth with AngularJS and WebAPI - SoCal Code Camp 2015Stuart

This document provides an overview of OAuth and describes how to implement OAuth authorization in an AngularJS single page application using ASP.NET Web API as the resource server. It discusses OAuth flows, access and refresh tokens, and setting up an OAuth authorization server using OWIN middleware. The demo application uses the resource owner password credentials flow to authenticate users and obtain an access token to call the Web API, with refresh tokens to obtain new access tokens when they expire.

Web API or WCF - An Architectural ComparisonAdnan Masood

ASP.NET Web API is a framework that makes it easy to build HTTP services that reach a broad range of clients, including browsers and mobile devices. The new ASP.NET Web API is a continuation of the previous WCF Web API projection. WCF was originally created to enable SOAP-based services and other related bindings. However, for simpler RESTful or RPCish services (think clients like jQuery) ASP.NET Web API is a good choice. In this meeting we discussed what do you need to understand as an architect to implement your service oriented architecture using WCF or ASP.NET web API. With code samples, we will elaborate on WCF Web API’s transition to ASP.NET Web API and respective constructs such as Service vs. Web API controller, Operation vs. Action, URI templates vs ASP.NET Routing, Message handlers, Formatters and Operation handlers vs Filters, model binders. WebApi offers support for modern HTTP programming model with full support for ASP.NET Routing, content negotiation and custom formatters, model binding and validation, filters, query composition, is easy to unit test and offers improved Inversion of Control (IoC) via DependencyResolver. You will walk away with a sample set of services that run on Silverlight, Windows Forms, WPF, Windows Phone and ASP.NET.

Visual basic asp.net programming introductionHock Leng PUAH

This document provides an introduction and overview of ASP.NET Visual Basic web forms for beginners. It covers topics like object-oriented programming concepts, the Page_Load and Button_Click subroutines, variables and data types, decision making using If/ElseIf/Else statements, and displaying output from web controls. Examples are provided for getting user input and displaying output messages based on conditions. The document also demonstrates code reuse through subroutines.

C# ASP.NET WEB API APPLICATION DEVELOPMENTDr. Awase Khirni Syed

The document provides an introduction to ASP.NET Web API and discusses key concepts related to web services and HTTP including: 1. Web API allows exposing data and services to different devices by taking advantage of full HTTP features like URIs, headers, caching, and supporting various content formats like XML and JSON. 2. SOAP and HTTP are common protocols for implementing web services, with SOAP using HTTP and XML for serialization and HTTP serving as a more lightweight alternative supporting any content over the protocol. 3. Key HTTP concepts discussed include requests, responses, status codes, headers, and the stateless nature of the protocol, with HTTP providing a standard for communication between client and server applications.

OAuth-as-a-service using ASP.NET Web API and Windows Azure Access ControlMaarten Balliauw

Unleash the power of HTTP with ASP.NET Web APIFilip W

Introdução ao ASP .NET Web APIVinicius Mussak

Building modern web sites with ASP .Net Web API, WebSockets and RSignalAlessandro Pilotti

ASP.net Image SlideshowHock Leng PUAH

What's new in Angular 2?Alfred Jett Grandeza

Introduction to AngularJSCollaboration Technologies

Introduction to HTML4Collaboration Technologies

OAuth-as-a-service using ASP.NET Web API and Windows Azure Access Control - W...Maarten Balliauw

Web Service Implementation Using ASP.NETPonraj

C O R B A Unit 4Roy Antony Arnold G

ASP, ASP.NET, JSP, COM/DCOMAashish Jain

Dcom vs. corbaMohd Arif

OAuth-as-a-serviceusing ASP.NET Web API and Windows Azure Access ControlMaarten Balliauw

Concepts of Asp.Netvidyamittal

Asp.netNaveen Sihag

OAuth with AngularJS and WebAPI - SoCal Code Camp 2015Stuart

Web API or WCF - An Architectural ComparisonAdnan Masood

Visual basic asp.net programming introductionHock Leng PUAH

C# ASP.NET WEB API APPLICATION DEVELOPMENTDr. Awase Khirni Syed

Similar to REST and ASP.NET Web API (Milan) (20)

Lies you have been told about RESTdarrelmiller71

REST – Beyond the hype The document discusses REST and common misconceptions about RESTful API design. It begins with a brief history of REST and considerations of alternatives like SOAP. It then addresses how the rise of frameworks led to prescriptive but incorrect "rules" for REST. The bulk of the document dispels common myths and "lies" told about RESTful design, focusing on proper use of URIs, resources, media types, and use of hypermedia. It emphasizes that REST is an architectural style and not a rigid set of rules.

Soap and RestEdison Lascano

The document discusses web services and compares the SOAP and REST approaches. It provides details on: - SOAP uses XML/HTTP and defines operations via WSDL. Services are registered in UDDI. Clients access services via SOAP messages. - REST uses HTTP methods (GET, POST etc.) to manipulate resources identified by URIs. It returns representations of resources in formats like JSON/XML. Services have a uniform interface and are discoverable via documentation. - Both approaches are commonly used in web 2.0 applications via public and private APIs. Mashups combine multiple APIs to build new applications with low coupling between components.

Scaling with swaggerTony Tam

This document discusses scaling applications and services. It recommends taking a vertical approach by breaking monolithic applications into microservices that communicate through APIs. The Swagger framework is presented as a way to document and test APIs. Swagger can generate client libraries and helps services scale by enabling asynchronous communication through websockets. Taking this vertical, microservices approach with Swagger improves scalability by allowing dedicated teams to own individual services and improves performance through asynchronous communication protocols.

Introduction to REST and JerseyChris Winters

This document provides an introduction and overview of REST and Jersey. It begins with an introduction of the presenter and their background and interests. It then provides brief definitions and discussions of REST, highlighting some of its key aspects like being stateless, using standard HTTP methods, and having resources with multiple representations. It introduces the Jersey framework and discusses some of its features. It maps out the topics to be covered, including explanations of REST concepts like resources having unique IDs, linking resources together, and implementing the hypermedia constraint. It also provides a demonstration of a sample REST application called Notem and discusses challenges in implementing REST concepts like generating links between resources.

Overview of REST - Raihan UllahCefalo

REST (REpresentational State Transfer) is a software architectural style for web services that defines constraints including a client-server architecture, statelessness, and a uniform interface. Key principles are that resources are identified through URIs and manipulated through representations of their state, and that requests and responses directly map to HTTP methods. REST aims to provide interoperability, performance, and scalability for web services.

Dropping ACID: Wrapping Your Mind Around NoSQL DatabasesKyle Banerjee

This document discusses NoSQL databases as an alternative to traditional relational databases. It provides an overview of different types of NoSQL databases like document stores, wide column stores, key-value stores and graph databases. It also discusses advantages of NoSQL databases like horizontal scalability and ease of use with large amounts of unstructured data, as well as disadvantages like lack of transactions and joins. The document recommends choosing a database based on the type of queries, data size, read/write needs, and whether the data needs to be accessed by other applications.

Api crashTony Nguyen

This document provides an overview of APIs, including what they are, why they are useful, common data formats like JSON and XML, RESTful API design principles, and how to consume and create APIs. It discusses topics like HTTP verbs, resources and URIs, caching, authentication, and error handling for APIs. The document also provides examples of consuming APIs with tools like Postman and creating a simple API in Node.js.

Api crashFraboni Ec

This document provides an overview of APIs, including what they are, why they are useful, common data formats like JSON and XML, RESTful API design principles, and how to consume and create APIs. It discusses topics like HTTP verbs, resources and URIs, caching, authentication, rate limiting, and error handling for APIs. The document also provides examples of consuming APIs with tools like Postman and creating a simple API in Node.js.

Api crashJames Wong

This document provides an overview of APIs, including what they are, why they are useful, common data formats like JSON and XML, RESTful API design principles, and how to consume and create APIs. It discusses API concepts like resources, HTTP verbs, caching, authentication, and error handling. It also provides examples of consuming APIs with tools like Postman and creating a simple API in Node.js.

Api crashYoung Alista

Api crashHarry Potter

This document provides an overview of APIs, including what they are, why they are useful, common data formats like JSON and XML, RESTful API design principles, and how to consume and create APIs. It discusses topics like HTTP verbs, resources and URIs, caching, authentication, and error handling for APIs. The document also provides examples of consuming APIs through tools like Postman and creating a simple API in Node.js.

Api crashLuis Goldster

This document provides an overview of APIs, including what they are, why they are useful, common data formats like JSON and XML, RESTful API design principles, and how to consume and create APIs. It discusses API concepts like resources, HTTP verbs, caching, authentication, and error handling. It also provides examples of consuming APIs with tools like Postman and creating a simple API in Node.js.

Api crashHoang Nguyen

This document provides an overview of APIs, including what they are, why they are useful, common data formats like JSON and XML, RESTful API design principles, and how to consume and create APIs. It discusses API concepts like resources, HTTP verbs, caching, authentication, and error handling. It also provides examples of consuming APIs with tools like Postman and creating a simple API in Node.js.

Phalcon 2 High Performance APIs - DevWeekPOA 2015Jackson F. de A. Mafra

The document discusses APIs and provides examples of RESTful APIs. It describes how RESTful APIs are built upon a domain model to provide resources that can be navigated through requests. This allows clients to construct custom requests to get precisely the data needed, rather than requiring multiple calls or getting excess data. The domain model also provides a unified framework for request and response semantics.

Restful风格web服务架构Benjamin Tan

This document provides an overview of REST (Representational State Transfer) and RESTful architectures. It begins with an introduction and agenda. It then defines REST and describes its key aspects like resources, representations, and the HTTP methods. It discusses the constraints and goals of REST, examples of RESTful systems, and why REST is advantageous for building distributed systems. Finally, it covers implementing RESTful services in Java using the JAX-RS API and frameworks like Jersey.

REST API DesignDevi Kiran G

RESTful Architecture is effectively an implementation of Resource-Oriented architecture (ROA). ROA - is a good fit for Service oriented Architecture (SOA) implementation. Check out KickStartPros approach on RESTful API Design. * REST = REpresentational State Transfer * REST is Resource Based Representation. REST identifies things by JSON or XML & URIs. * REST behavior/actions are identified by HTTP methods (GET, POST, PUT, DELETE). * Using Uniform Interface Architecture with REST you can decouple Client (like Browser/Android App/iOS App) and Server. * REST using Layered System and Cacheable Architecture gives better performance.

API Testing. Streamline your testing process.Andrey Oleynik

Slides from IT talk: «API Testing. Streamline your testing process. A step by step tutorial» Code on github: https://github.com/a-oleynik/soap-ui Webinar on youtube: https://www.youtube.com/watch?v=x2ALtuCjuUo DataArt P. https://www.meetup.com/ru-RU/DataArt-Wroclaw-IT-talk/events/246967484/?eventId=246967484 Wroclaw, 2018, February 15

Javantura v4 - True RESTful Java Web Services with JSON API and Katharsis - M...HUJAK - Hrvatska udruga Java korisnika / Croatian Java User Association

1) The document discusses REST (Representational State Transfer), its constraints, and the Richardson Maturity Model for classifying RESTful web services. 2) It introduces JSON API as a standard for building RESTful hypermedia APIs and describes how the Katharsis library implements JSON API in Java applications. 3) An example is provided of using Spring Boot and Katharsis to build a RESTful web service with a Project and Task domain that follows the JSON API standard.

Austin Day of Rest - IntroductionHandsOnWP.com

Nick Batik introduces the concepts of the JASON REST APIs by explaining the logic behind APIs, and walking through a few practical uses for both personal and client websites. This is an informal discussion of the vocabulary and concepts to introduce the REST API to those who unfamiliar with the topic to help them prepare for a more technical understanding of the subject in order to take advantage of the possibilities.

Prometheus lightning talk (Devops Dublin March 2015)Brian Brazil

This document introduces Prometheus, an open-source monitoring system that allows instrumentation of everything including RPCs, interfaces, business logic, and logs. It provides client libraries that make instrumentation easy across many languages. The Prometheus server can handle over a million time series in one instance with no dependencies. It offers dashboards, expression queries, alerts and integrates with many systems. Time series have structured labels allowing flexible aggregation and complex math for rules and alerts. Prometheus costs less than $.001 per time series per month and is developed by SoundCloud, Boxever and Docker with an active community.

Lies you have been told about RESTdarrelmiller71

Soap and RestEdison Lascano

Scaling with swaggerTony Tam

Introduction to REST and JerseyChris Winters

Overview of REST - Raihan UllahCefalo

Dropping ACID: Wrapping Your Mind Around NoSQL DatabasesKyle Banerjee

Api crashTony Nguyen

Api crashFraboni Ec

Api crashJames Wong

Api crashYoung Alista

Api crashHarry Potter

Api crashLuis Goldster

Api crashHoang Nguyen

Phalcon 2 High Performance APIs - DevWeekPOA 2015Jackson F. de A. Mafra

Restful风格web服务架构Benjamin Tan

REST API DesignDevi Kiran G

API Testing. Streamline your testing process.Andrey Oleynik

Javantura v4 - True RESTful Java Web Services with JSON API and Katharsis - M...HUJAK - Hrvatska udruga Java korisnika / Croatian Java User Association

Austin Day of Rest - IntroductionHandsOnWP.com

Prometheus lightning talk (Devops Dublin March 2015)Brian Brazil

More from Jef Claes (8)

Evil By DesignJef Claes

Last year I ventured into the domain of (online) gambling. Given that the industry has been around since forever, I expected most problems to be of the technical kind. As it turned out, the struggle with technology was only part of a bigger problem; to move forward we needed to fully grasp the industry and its consumers. Events started out as a way to dismantle a legacy system, but quickly proved to be an effective tool to gain a deeper understanding of our domain. Visualising event streams, we discovered patterns that helped us identify what drives different types of users. Having a better understanding of what customers are looking for, we dove into existing literature to learn which techniques and models casinos use to cater for each type of user. We learned how to program chance while staying true to the Random Number God. Even when variance is brutal, casinos have enough data and tools to steer clear from the pain barrier. All of this entails interesting problems and software, but isn't my code damaging society? Or is gambling just another human trait?

The Ubiquitous Language DDDBE V2Jef Claes

NCrafts Eventstorming workshopJef Claes

Modeling a business process is often associated with people in suits having long and dull meetings. Way too much time gets wasted for an outcome that's far from reality and which will be obsolete in weeks. Event storming is a workshop format that brings modeling back to all stakeholders, and aims to create usable models. In this workshop, you won't be writing any code, but you will be using lots of paper, post-its and a marker. After going over a bit of theory and a small example, we will present you with a real business problem, and in a few short playful sessions you will experience how powerful event storming can be in helping a team gain insights into complex problems. The techniques you will learn in this workshop will pay off immediately.

What if we stored events instead of state?Jef Claes

The document discusses storing a sequence of events instead of state in a system. It proposes an "event store" approach where commands are logged as events and the current state can be reconstructed by replaying the sequence of events from the beginning. This allows an audit log to be maintained and for multiple "read models" to be generated from the event stream to serve different queries or views of the data.

The Ubiquitous LanguageJef Claes

The document discusses the importance of having a shared or "ubiquitous" language within development projects to facilitate effective communication and prevent failures. It states that an ubiquitous language provides common ground for learning and communication, with the domain model acting as the backbone of this shared language. While cultivating an ubiquitous language is challenging, it is worthwhile as communication and learning are very important.

Workshop event stormingJef Claes

Refactoring towards the ubiquitous languageJef Claes

WebSockets On FireJef Claes

The document discusses the need for WebSockets as a replacement for Comet techniques for direct communication between browsers and servers. It explains that WebSockets allow for full-duplex connections over a single TCP connection. The current state of WebSockets is discussed, noting browser and server support is growing but still limited in some cases. Code examples are provided to demonstrate how WebSockets work and establish connections.

Evil By DesignJef Claes

The Ubiquitous Language DDDBE V2Jef Claes

NCrafts Eventstorming workshopJef Claes

What if we stored events instead of state?Jef Claes

The Ubiquitous LanguageJef Claes

Workshop event stormingJef Claes

Refactoring towards the ubiquitous languageJef Claes

WebSockets On FireJef Claes

REST and ASP.NET Web API (Milan)

1. REST & ASP.NET Web API @JefClaes

2. Thanks to the sponsors

3. about/jefclaes @jefclaes http://jefclaes.be

4. REST

5. The acronym REpresentational State Transfer

6. REST is NOT... • ‘Webservices using JSON’ • A protocol • A design pattern

7. REST is.. “An architectural style for building distributed hypermedia systems.”

8. In theory... REST isn’t limited to a single message protocol.

9. But in practice... It’s all about HTTP.

10. So now you wonder.. Haven’t we been successfully building web services using SOAP and HTTP for over 10 years ?

11. BASIC CONCEPTS

12. Resources • An entity, item, or just a thing you want to expose. • REST is Resource Oriented.

13. Resources

14. Resources

15. Resources

16. Resources

17. Identifiers Something that identifies a resource. ID: 1 URI: http://batman.com/api/batresource/1

18. Representations View on a resource’s state at an instant in time. XML: JSON: Other: <BatResource> { • Images <Id>1</Id> "Id":"1", • CSV <Description> "Description":"Bataran • Custom Batarang g", • ... </Description> "Quantity":1 <Quantity>1</Quantity> } </BatResource>

19. Verbs Actions on a resource. Create Read Update Delete POST GET PUT DELETE

20. Hypermedia HATEOAS: Hypermedia as the engine of application state Linking your API together { "Id":"1", "Description":"Batarang", “Quantity":1, “Links": { "Rel":"Next", "Href":"http://localhost:8080/api/batresource/2" } }

21. HypeRRRRRRRmedia • Relations • Embedded resources • Reference data • Redistribution of effort • Reduction of payload size • Reflow • Restriction of functionality

22. Architecture of the WEB ARCHITECTURAL VALUES

23. Scalability and performance Yes, text-based, synchronous, request-response can be performant. • Stateless • Caching

24. Loose coupling • No transactions • No state • No guarantees • HATEOAS • No specific technology stack

25. Consistency and Uniformity Everybody knows how to use HTTP –Constraints –Well understood semantics

26. LEFT-OVERS

27. Richardson’s Maturity Model Level 0: POX Level 1: Resources Level 2: HTTP verbs Level 3: Hypermedia

28. ASP.NET WEBAPI

29. What? .NET HTTP framework (4.0) for building RESTful services.

30. When? • HTTP Services (WCF) • AJAX back-ends

31. The server

32. Options • WebHost – ASP.NET MVC: Click, click, click • SelfHost

33. Starting

34. Mapping Web API to REST concepts

35. A resource

36. A resource

37. Identifiers

38. Identifiers

39. Verbs

40. Verbs

41. Representations

42. Representations application/json text/xml

43. Representations

44. Hypermedia

45. Hypermedia

46. The Client

47. Package Microsoft.AspNet.WebApi.Client

48. Verbs and asynchrony

49. Summary • REST – Concepts – Architectual values – Left overs • ASP.NET Web API – Server – Client

50. There is more Slides and source on http://jefclaes.be Extensibility? • Next session (Raffaele Rialdi) • http://github.com/JefClaes/aspnet-webapi-samples-tunisia

51. Please rate this session Scan the code, go online, rate this session

REST and ASP.NET Web API (Milan)

Recommended

More Related Content

What's hot (20)

Viewers also liked (20)

Similar to REST and ASP.NET Web API (Milan) (20)

More from Jef Claes (8)

REST and ASP.NET Web API (Milan)