REST and ASP.NET Web API (Tunisia)

Sep 12, 2012Download as PPTX, PDF3 likes4,380 views

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.

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.

A bank

Identifiers
Something that identifies a resource.

BIC (= Bank Identifier Code): KREDBEBB

URI: http://myapi.com/bank/KREDBEBB

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

XML: JSON: Other:

<Bank> { • Images
<BIC>KREDBEBB</BIC> "BIC":"123“, • CSV
<Name>KBC</Name> “Name”:”KBC” • Custom
</Bank> } • ...

Verbs
Actions on a resource.

Read, Update, Delete, Add

GET, PUT, DELETE, POST

Hypermedia
HATEOAS: Hypermedia as the engine of application state

Linking your API together

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 (4.0) HTTP framework
for building RESTful services.

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

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

Packages
Microsoft.AspNet.WebApi.SelfHost

Without conventions
• Attributes [HttpGet]
• [NonAction]

Default behaviour &
IncludeErrorDetailPolicy
• By default 500 Internal Server Error

XML/JSON
Supported out of the box:
• text/xml
• application/json (NewtonSoft)

Summary
• REST
– Concepts
– Architectual values
– Left overs
• ASP.NET Web API
– Server/client
– Exception handling
– Content negotiation
– Message handlers
– IoC
– Testing

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.

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.

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.

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.

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.

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.

RESTful Web Services with Spring MVCdigitalsonic

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.

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.

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

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.

Architecture Best PracticesAWS Germany

This document provides 6 rules for building powerful web applications on AWS: 1) Service all web requests, 2) Service requests as fast as possible, 3) Handle requests at any scale, 4) Simplify architecture with services, 5) Automate operational management, and 6) Leverage unique cloud properties. It describes AWS services like Route53, ELB, RDS, DynamoDB, SQS, CloudSearch, and EMR that can be used to implement these rules and build scalable, high-performance applications on AWS. Customer examples are provided that demonstrate how AWS services allow them to focus on their business rather than infrastructure management.

SOAP vs RESTMário Almeida

This document compares SOAP and REST web services. SOAP uses XML and relies on complex specifications, while REST uses simple HTTP requests and aims to be lightweight. REST has advantages for simplicity, bandwidth usage, caching and statelessness. SOAP may be better for complex transactions that require ACID properties and reliable messaging. Factors like security requirements, scalability, and programming language support also influence the choice of protocol.

Representational State Transfer (REST)David Krmpotic

REST (REpresentational State Transfer) is an architectural style for building web APIs that relies on HTTP verbs like GET, POST, PUT, and DELETE to manipulate resources identified by URIs. Resources can have multiple representations like JSON or XML, and the appropriate representation is selected via content negotiation. REST aims to provide a simple, lightweight interface and takes advantage of existing web protocols to transfer representations of resources between clients and servers. Key REST constraints include using nouns for resources and HTTP methods for actions, making the interface lightweight, client-server, cacheable, and layered.

Rest api standards and best practicesAnkita Mahajan

Webservices: connecting Joomla! with other programs.Herman Peeren

This document discusses connecting Joomla! to other applications and services via web services. It describes different types of web services including XML-RPC, SOAP, and REST. XML-RPC and SOAP use remote procedure calls to call methods on a server, while REST uses HTTP methods to manipulate resources. The document provides examples of using these services with Joomla! and other applications and frameworks. It emphasizes the importance of standardizing web service connections in Joomla! using its MVC framework.

Web service testing_final.pptxvodqancr

Building Ext JS Using HATEOAS - Jeff StanoSencha

This document discusses using HATEOAS (Hypermedia as the Engine of Application State) with the ExtJS JavaScript framework. It defines HATEOAS and common media types like HAL and Siren. HATEOAS reduces client-server coupling by having the client discover available state transitions from resource representations instead of having hardcoded URLs. The document explains how to extend ExtJS models and proxies to consume HAL responses and handle state transitions based on the link relations in HAL documents. Live coding examples demonstrate implementing this with the Sencha HAL package.

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,

REST API Design & DevelopmentAshok Pundit

The document discusses demystifying APIs. It begins with an introduction to APIs, including their evolution and benefits. It then discusses RESTful APIs and their key aspects like uniform interface and use of HTTP methods. The document outlines best practices for API design, development, and challenges. It provides examples of designing APIs using Node.js and Hapi.js and discusses challenges like security, authentication, rate limiting, and scalability. Tools mentioned include Express, Swagger, Postman, and Kong.

Building RESTfull Data Services with WebAPIGert Drapers

Data services are a major building block inside a service oriented architecture. Not only do they provide the abstraction and isolation between physical storage systems and the business layer, they can also provide the means for: authentication, authorization, transformation, projection, scale (through for example sharding) and caching. This session will walk you through implementing your RESTfull data service so that you can easily enable and integrate the described capabilities

Using the Cascade Server Web Service API, by Artur Tomusiakhannonhill

This document provides an overview of Cascade Server web services. It discusses what a web service is and examples of how they can be used. It covers the main operations available through the Cascade Server web services API like create, read, edit, delete, copy, and managing access rights. It also explains how to authenticate to the web services and understand the WSDL file. Code examples are provided for common operations in PHP. Limitations of the web services are outlined and upcoming features in Cascade Server 7.2 are previewed.

L18 REST API DesignÓlafur Andri Ragnarsson

Forritun veflausna, hvort sem er fyrir neytendur (B2C) eða fyrirtækni (B2B) eru í sívaxandi mæli að nota API til að bjóða upp á þjónustur. Þetta opnar örðum hugbúnaðarhúsum leið til að bjóða upp á lausnir sem nota viðkomandi APi. Sem dæmi má nefna að margir nota Google Maps API til að birta kort t.d. hvar eitthvað er. Notkun API er einnig architecture style og þar kemur REST inn. Með því að aðskila viðmót og backvinnslu með API má ná fram skörpum skilum þarna á milli. Í þessum fyrirlestri er REST skoða sem leið til að búa til lausnir.

Optimization of modern web applicationsEugene Lazutkin

Restful ServicesSHAKIL AKHTAR

RESTful API Design Best Practices Using ASP.NET Web API💻 Spencer Schneidenbach

Designing and building RESTful APIs isn’t easy. On its surface, it may seem simple – after all, we’re only marshaling JSON back and forth over HTTP right? However, that’s only a small part of the equation. There are many things to keep in mind while building the systems that act as the key to your system. In this session, we’ll delve into several best practices to keep in mind when designing your RESTful API. We’ll discuss authentication, versioning, controller/model design, and testability. We’ll also explore the do’s and don’t’s of RESTful API management so that you make sure your APIs are simple, consistent, and easy-to-use. Finally, we’ll discuss the importance of documentation and change management. The session will show examples using ASP.NET Web API and C#. However, this session will benefit anyone who is or might be working on a RESTful API.

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.

More Related Content

What's hot (20)

Best Practice in Web Service DesignLorna Mitchell

Designing REST services with Spring MVCSerhii Kartashov

Webservices Overview : XML RPC, SOAP and RESTPradeep Kumar

Web ServicesKatrien Verbert

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

REST API DesignDevi Kiran G

Architecture Best PracticesAWS Germany

SOAP vs RESTMário Almeida

Representational State Transfer (REST)David Krmpotic

Rest api standards and best practicesAnkita Mahajan

Webservices: connecting Joomla! with other programs.Herman Peeren

Web service testing_final.pptxvodqancr

Building Ext JS Using HATEOAS - Jeff StanoSencha

Consuming RESTful services in PHPZoran Jeremic

REST API Design & DevelopmentAshok Pundit

Building RESTfull Data Services with WebAPIGert Drapers

Using the Cascade Server Web Service API, by Artur Tomusiakhannonhill

L18 REST API DesignÓlafur Andri Ragnarsson

Optimization of modern web applicationsEugene Lazutkin

Restful ServicesSHAKIL AKHTAR

Best Practice in Web Service DesignLorna Mitchell

Designing REST services with Spring MVCSerhii Kartashov

Webservices Overview : XML RPC, SOAP and RESTPradeep Kumar

Web ServicesKatrien Verbert

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

REST API DesignDevi Kiran G

Architecture Best PracticesAWS Germany

SOAP vs RESTMário Almeida

Representational State Transfer (REST)David Krmpotic

Rest api standards and best practicesAnkita Mahajan

Webservices: connecting Joomla! with other programs.Herman Peeren

Web service testing_final.pptxvodqancr

Building Ext JS Using HATEOAS - Jeff StanoSencha

Consuming RESTful services in PHPZoran Jeremic

REST API Design & DevelopmentAshok Pundit

Building RESTfull Data Services with WebAPIGert Drapers

Using the Cascade Server Web Service API, by Artur Tomusiakhannonhill

L18 REST API DesignÓlafur Andri Ragnarsson

Optimization of modern web applicationsEugene Lazutkin

Restful ServicesSHAKIL AKHTAR

Viewers also liked (17)

RESTful API Design Best Practices Using ASP.NET Web API💻 Spencer Schneidenbach

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

ASP.NET Web APIPietro Libro

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.

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.

Introduction à ASP.NET CoreMicrosoft

"ASP.NET Core est le nouveau framework Open Source et Cross Platform pour développer des applications connectées modernes : applications webs, backends mobiles ou applications IoT. ASP.NET Core peut tourner sur .NET Core ou sur le .NET Framework complet. Son architecture a été complètement revue depuis la précédente génération du framework afin de fournir une expérience de développement plus moderne, plus flexible et plus performante. Venez découvrir les bases d'ASP.NET Core afin de pouvoir l'envisager dans vos futurs projets !"

Best Practices for Architecting a Pragmatic Web API.Mario Cardinal

This presentation teach how to design a real-world and pragmatic web API. It draws from the experience Mario Cardinal have gained over the years being involved architecting many Web API. This presentation begins by differencing between a Web and a REST API, and then continue with the design process. We conclude with the core learnings of the session which is a review of the best practices when designing a web API. Armed with skills acquired, you can expect to see significant improvements in your ability to design a pragmatic web API.

Web Services - A brief overviewRaveendra Bhat

Web services allow applications to communicate over the web through standard protocols like HTTP and XML. There are two main types of web services: REST services which rely on HTTP verbs to manipulate resources identified by URIs, and SOAP services which use XML and HTTP to define structured messages to access services described in a WSDL file. SOAP services require more overhead for message formatting and processing compared to the lighter-weight REST approach.

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.

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.

Web Service Presentationguest0df6b0

REST & RESTful Web ServicesHalil Burak Cetinkaya

RESTful Web ServicesChristopher Bartling

The document discusses REST (REpresentational State Transfer), an architectural style for building distributed systems. It covers REST concepts like resources, representations, URIs, HTTP methods, caching, and versioning. It provides guidance on designing RESTful APIs, including determining resources, supported methods, and return codes. Content negotiation and tools for testing REST APIs are also mentioned.

RESTful API Design, Second EditionApigee | Google Cloud

This document provides guidance on designing RESTful APIs. It recommends using nouns instead of verbs, keeping URLs simple with only two endpoints per resource, and following conventions from leading APIs. Complex variations and optional parameters should be "swept behind the '?'." The document emphasizes designing for application developers by making APIs intuitive, consistent and complete while also accommodating exceptional clients. It suggests adding an API virtualization layer to handle complexity.

Best practices for RESTful web service designRamin Orujov

Support Web Services SOAP et RESTful Mr YOUSSFIENSET, Université Hassan II Casablanca

RESTful API Design Best Practices Using ASP.NET Web API💻 Spencer Schneidenbach

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

ASP.NET Web APIPietro Libro

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

Web Service Implementation Using ASP.NETPonraj

Introduction à ASP.NET CoreMicrosoft

Best Practices for Architecting a Pragmatic Web API.Mario Cardinal

Web Services - A brief overviewRaveendra Bhat

Web services - A Practical ApproachMadhaiyan Muthu

ASP.NET Web API and HTTP FundamentalsIdo Flatow

Web Services TutorialLorna Mitchell

Web Service Presentationguest0df6b0

REST & RESTful Web ServicesHalil Burak Cetinkaya

RESTful Web ServicesChristopher Bartling

RESTful API Design, Second EditionApigee | Google Cloud

Best practices for RESTful web service designRamin Orujov

Support Web Services SOAP et RESTful Mr YOUSSFIENSET, Université Hassan II Casablanca

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

Build Modern Web Apps Using ASP.NET Web API and AngularJSTaiseer Joudeh

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.

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.

Understanding Web servicesFabricio Epaminondas

This document provides an overview of web services and how to create them using SOAP and REST. It defines web services and discusses their characteristics such as being XML-based and loosely coupled. It describes technologies used in web services like SOAP, WSDL, and UDDI. It provides examples of creating a SOAP web service in Java and a RESTful web service using Spring Boot. The document compares using REST vs SOAP and discusses when each approach is best.

Enjoying the Move from WCF to the Web APIKevin Hazzard

Дмитрий Тежельников «Разработка вэб-решений с использованием Asp.NET.Core и ...MskDotNet Community

Поговорим об эволюции в мире вэб-приложений, современных технологиях и фреймворках, которые используют в вэб-разработке сегодня. Обсудим основные архитектурные принципы при создании вэб-решений для разных клиентов. Обсудим, как сделать и запустить бэк-энд на Asp.NET.Core в Visual Studio 2017. Далее поговорим, как написать и запустить фронт-энд с использованием React.JS, Redux, Routing, Bootstrap в IntelliJ IDEA 2017. В конце доклада немного заглянем в будущее, что нас ждет в вэб-разработке завтра?

The web as it should bethebeebs

With the advent of CSS3 and the ever-greater maturity of HTML5, it’s an exciting time for the Web. The possibilities for creating truly engaging – even addictive – Web and business applications appear limitless. And, with the release of Internet Explorer 9, Microsoft finally came in from the cold after many years in the world wide wilderness. As Internet Explorer moves towards full support of standards-based HTML5 and CSS3, this is a great opportunity to hear from Martin Beeby about how these key technologies will be used to build and deliver the applications of tomorrow, engage end-users like never before, and generate even greater loyalty to Web-sites.

Amish Umesh - Future Of Web App Testing - ClubHack2007ClubHack

The document discusses the evolution of web application testing from Web 1.0 to Web 2.0. It describes how Web 1.0 applications had traditional architectures and testing methodologies, while Web 2.0 introduced challenges like asynchronous JavaScript and XML (AJAX) that limited automated testing. The document proposes that future testing requires a hybrid approach using both automated scanning and manual testing within a browser-based toolbar. This allows testing each page, handling authentication, and executing JavaScript to address limitations of current automated scanners.

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.

REST API and CRUDPrem Sanil

A REST API uses HTTP requests with verbs like GET, POST, PUT, and DELETE to perform CRUD (Create, Read, Update, Delete) operations on resources identified by URLs. It provides a lightweight alternative to SOAP that returns data in JSON format and HTTP response codes. Well-known codes include 200 for OK, 201 for Created, 400 for Bad Request, and 404 for Not Found. REST enables building applications and platforms that can easily integrate new interfaces over time.

sell ideaRashmi Joshi

This internal presentation discusses developing and selling web applications. It introduces web applications and their components like servlets and JSP pages. It then presents an idea to share innovations online and get paid for ideas. The presentation explains how web applications work by sending requests between clients and servers. It also includes examples of web containers and the development process for web applications.

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.

Week01 jan19 introductionto_phpJeanho Chu

This document introduces PHP and MySQL for dynamic web development. PHP is an open-source scripting language suited for web development that can generate HTML code on the server. MySQL is a popular open-source database management system. PHP and MySQL allow websites to be responsive and malleable by connecting to databases and generating customized HTML based on user inputs or database contents. Examples of dynamic websites that use these technologies include WordPress, Shopify, Facebook, and interactive data visualization projects.

mearn-stackjdksjdsfjdkofkdokodkojdj.pptxaravym456

Javascript for Wep AppsMichael Puckett

JavaScript frameworks allow business logic to run on the client by sending JSON data on page load rather than dynamic HTML. This allows JavaScript to set up objects and classes to make assumptions without round trips to the server, improving performance. Popular frameworks like Backbone, Ember, Angular, Knockout, and Meteor emphasize separating UI from logic, data binding, templating, and routing to enable single-page applications. Meteor stands out by using the same syntax on client and server and web sockets for automatic UI updates.

Mini-Training: Let's have a restBetclic Everest Group Tech Team

Building dynamic applications with the share point client object modelEric Shupps

This document provides an overview of building dynamic applications using the SharePoint Client Object Model. It introduces the Client Object Model and how it can be used from .NET, Silverlight, and JavaScript applications to access and manipulate SharePoint data without server-side code. It discusses the core ClientContext object and how to load and execute queries. It also includes demos of building applications using each technology - .NET, Silverlight, and JavaScript.

SharePoint Saturday The Conference DC - How the client object model saved the...Liam Cleary [MVP]

The document discusses how the Client Object Model in SharePoint 2010 improved client application development by providing a simple and consistent API for accessing SharePoint data from various client platforms like .NET, Silverlight, and JavaScript. It saved the day by enabling quick updates to SharePoint items without direct server access and adding interactive functionality to client applications using JavaScript. The Client Object Model abstracted the complex SharePoint object model and web services into a simpler client-side API.

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.

Building rest services using aspnetwebapiBrij Mishra

Build Modern Web Apps Using ASP.NET Web API and AngularJSTaiseer Joudeh

Restful风格web服务架构Benjamin Tan

Overview of REST - Raihan UllahCefalo

Understanding Web servicesFabricio Epaminondas

Enjoying the Move from WCF to the Web APIKevin Hazzard

Дмитрий Тежельников «Разработка вэб-решений с использованием Asp.NET.Core и ...MskDotNet Community

The web as it should bethebeebs

Amish Umesh - Future Of Web App Testing - ClubHack2007ClubHack

Prometheus lightning talk (Devops Dublin March 2015)Brian Brazil

REST API and CRUDPrem Sanil

sell ideaRashmi Joshi

Soap and RestEdison Lascano

Week01 jan19 introductionto_phpJeanho Chu

mearn-stackjdksjdsfjdkofkdokodkojdj.pptxaravym456

Javascript for Wep AppsMichael Puckett

Mini-Training: Let's have a restBetclic Everest Group Tech Team

Building dynamic applications with the share point client object modelEric Shupps

SharePoint Saturday The Conference DC - How the client object model saved the...Liam Cleary [MVP]

Scaling with swaggerTony Tam

Building rest services using aspnetwebapiBrij Mishra

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

Recently uploaded (20)

Datastucture-Unit 4-Linked List Presentation.pptxkaleeswaric3

#AdminHour presents: Hour of Code2018 slide deck from 12/6/2018Lynda Kane

tecnologias de las primeras civilizaciones.pdffjgm517

Asthma presentación en inglés abril 2025 pdfVanessaRaudez

Automation Dreamin': Capture User Feedback From AnywhereLynda Kane

Electronic_Mail_Attacks-1-35.pdf by xploitniftliyevhuseyn

DevOpsDays Atlanta 2025 - Building 10x Development Organizations.pptxJustin Reock

Building 10x Organizations with Modern Productivity Metrics 10x developers may be a myth, but 10x organizations are very real, as proven by the influential study performed in the 1980s, ‘The Coding War Games.’ Right now, here in early 2025, we seem to be experiencing YAPP (Yet Another Productivity Philosophy), and that philosophy is converging on developer experience. It seems that with every new method we invent for the delivery of products, whether physical or virtual, we reinvent productivity philosophies to go alongside them. But which of these approaches actually work? DORA? SPACE? DevEx? What should we invest in and create urgency behind today, so that we don’t find ourselves having the same discussion again in a decade?

What is Model Context Protocol(MCP) - The new technology for communication bw...Vishnu Singh Chundawat

The MCP (Model Context Protocol) is a framework designed to manage context and interaction within complex systems. This SlideShare presentation will provide a detailed overview of the MCP Model, its applications, and how it plays a crucial role in improving communication and decision-making in distributed systems. We will explore the key concepts behind the protocol, including the importance of context, data management, and how this model enhances system adaptability and responsiveness. Ideal for software developers, system architects, and IT professionals, this presentation will offer valuable insights into how the MCP Model can streamline workflows, improve efficiency, and create more intuitive systems for a wide range of use cases.

Technology Trends in 2025: AI and Big Data AnalyticsInData Labs

At InData Labs, we have been keeping an ear to the ground, looking out for AI-enabled digital transformation trends coming our way in 2025. Our report will provide a look into the technology landscape of the future, including: -Artificial Intelligence Market Overview -Strategies for AI Adoption in 2025 -Anticipated drivers of AI adoption and transformative technologies -Benefits of AI and Big data for your business -Tips on how to prepare your business for innovation -AI and data privacy: Strategies for securing data privacy in AI models, etc. Download your free copy nowand implement the key findings to improve your business.

Salesforce AI Associate 2 of 2 Certification.docxJosé Enrique López Rivera

Buckeye Dreamin 2024: Assessing and Resolving Technical DebtLynda Kane

Role of Data Annotation Services in AI-Powered ManufacturingAndrew Leo

Hands On: Create a Lightning Aura Component with force:RecordDataLynda Kane

The Evolution of Meme Coins A New Era for Digital Currency ppt.pdfAbi john

"Rebranding for Growth", Anna VelykoivanenkoFwdays

AI and Data Privacy in 2025: Global TrendsInData Labs

In this infographic, we explore how businesses can implement effective governance frameworks to address AI data privacy. Understanding it is crucial for developing effective strategies that ensure compliance, safeguard customer trust, and leverage AI responsibly. Equip yourself with insights that can drive informed decision-making and position your organization for success in the future of data privacy. This infographic contains: -AI and data privacy: Key findings -Statistics on AI data privacy in the today’s world -Tips on how to overcome data privacy challenges -Benefits of AI data security investments. Keep up-to-date on how AI is reshaping privacy standards and what this entails for both individuals and organizations.

ThousandEyes Partner Innovation Updates for May 2025ThousandEyes

Procurement Insights Cost To Value Guide.pptxJon Hansen

Enhancing ICU Intelligence: How Our Functional Testing Enabled a Healthcare I...Impelsys Inc.

Semantic Cultivators : The Critical Future Role to Enable AIartmondano

Datastucture-Unit 4-Linked List Presentation.pptxkaleeswaric3

#AdminHour presents: Hour of Code2018 slide deck from 12/6/2018Lynda Kane

tecnologias de las primeras civilizaciones.pdffjgm517

Asthma presentación en inglés abril 2025 pdfVanessaRaudez

Automation Dreamin': Capture User Feedback From AnywhereLynda Kane

Electronic_Mail_Attacks-1-35.pdf by xploitniftliyevhuseyn

DevOpsDays Atlanta 2025 - Building 10x Development Organizations.pptxJustin Reock

What is Model Context Protocol(MCP) - The new technology for communication bw...Vishnu Singh Chundawat

Technology Trends in 2025: AI and Big Data AnalyticsInData Labs

Salesforce AI Associate 2 of 2 Certification.docxJosé Enrique López Rivera

Buckeye Dreamin 2024: Assessing and Resolving Technical DebtLynda Kane

Role of Data Annotation Services in AI-Powered ManufacturingAndrew Leo

Hands On: Create a Lightning Aura Component with force:RecordDataLynda Kane

The Evolution of Meme Coins A New Era for Digital Currency ppt.pdfAbi john

"Rebranding for Growth", Anna VelykoivanenkoFwdays

AI and Data Privacy in 2025: Global TrendsInData Labs

ThousandEyes Partner Innovation Updates for May 2025ThousandEyes

Procurement Insights Cost To Value Guide.pptxJon Hansen

Enhancing ICU Intelligence: How Our Functional Testing Enabled a Healthcare I...Impelsys Inc.

Semantic Cultivators : The Critical Future Role to Enable AIartmondano

REST and ASP.NET Web API (Tunisia)

1. REST & ASP.NET Web API By @JefClaes

2. REST

3. The acronym REpresentational State Transfer

4. REST is NOT... • „Webservices using JSON‟ • A protocol • A design pattern

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

6. In theory... REST isn‟t limited to a single message protocol.

7. But in practice... It‟s all about HTTP.

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

9. BASIC CONCEPTS

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

11. Identifiers Something that identifies a resource. BIC (= Bank Identifier Code): KREDBEBB URI: http://myapi.com/bank/KREDBEBB

12. Representations View on a resource‟s state at an instant in time. XML: JSON: Other: <Bank> { • Images <BIC>KREDBEBB</BIC> "BIC":"123“, • CSV <Name>KBC</Name> “Name”:”KBC” • Custom </Bank> } • ...

13. Verbs Actions on a resource. Read, Update, Delete, Add GET, PUT, DELETE, POST

14. Hypermedia HATEOAS: Hypermedia as the engine of application state Linking your API together

15. Architecture of the WEB ARCHITECTURAL VALUES

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

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

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

19. LEFT-OVERS

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

21. Questions?

22. ASP.NET WEBAPI

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

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

25. The server

26. Options • ASP.NET MVC – Click, click, click • SelfHost

27. Selfhost

28. Packages Microsoft.AspNet.WebApi.SelfHost

29. Starting

30. Simple CRUD

31. Creating a controller

32. Creating a controller

33. Without conventions • Attributes [HttpGet] • [NonAction]

34. The Client

35. Packages Microsoft.AspNet.WebApi.Client

36. POST and GET

37. Exception handling

38. Default behaviour & IncludeErrorDetailPolicy • By default 500 Internal Server Error

39. HttpResponseException

40. ErrorFilters

41. Content negotiation

42. XML/JSON Supported out of the box: • text/xml • application/json (NewtonSoft)

43. Custom formatters

44. Custom formatters

45. HTTP Messagehandlers

46. HTTP intermediaries

47. DelegatingHandler

48. DelegatingHandler

49. IoC

50. IDependencyResolver

51. IDependencyResolver

52. Testing

53. Unit testig

54. Integration testing in-memory

55. Summary • REST – Concepts – Architectual values – Left overs • ASP.NET Web API – Server/client – Exception handling – Content negotiation – Message handlers – IoC – Testing

56. Questions

Editor's Notes

#11: Batbelt?

REST and ASP.NET Web API (Tunisia)

Recommended

More Related Content

What's hot (20)

Viewers also liked (17)

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

More from Jef Claes (8)

Recently uploaded (20)

REST and ASP.NET Web API (Tunisia)

Editor's Notes