REST Course - First Class

Transcript

1. REST Course Victor Costa Romano
2. Victor Costa Romano
3. Introduction
4. Motivation Incorrect usage of REST pattern Incorrect usage of HTTP endpoints Lack of understanding to create or adapt HTTP endpoints to a RESTful API Level the knowledge about REST across the team
5. Target Audience Developers QAs
6. Prerequisite Basic Java knowledge Basic database/SQL knowledge
7. Syllabus • First class ◦ Basic concepts ◦ Basic CRUD API ◦ Richardson Maturity Model • Second class ◦ Complete CRUD API ◦ Richardson Maturity Model ◦ Easy creation of a REST API ◦ Tools • Third class ◦ Deploy ◦ Tests ◦ Documentation
8. More Than Just REST Spring Repositories
9. REST
10. REpresentational State Transfer Introduced by Roy Fielding in his dissertation in 2000 Architectural style for distributed hypermedia systems Defines a set of constraints to be used for creating web services
11. REST Constraints 1. Client-server 2. Stateless 3. Cacheable 4. Uniform interface 5. Layered system 6. Code on demand (optional)
12. 1. Client-server Servers and clients may also be replaced and developed independently, as long as the interface between them is not altered.
13. 2. Stateless No client context shall be stored on the server between requests. The client is responsible for managing the state of the application.
14. 3. Cacheable Well-managed caching partially or completely eliminates some client-server interactions, further improving scalability and performance.
15. 4. Uniform Interface Once a developer becomes familiar with one of your API, he should be able to follow the similar approach for other APIs.
16. 5. Layered System Clients cannot ordinarily tell whether they're connected directly to the end server, or to an intermediary along the way.
17. 6. Code on Demand (Optional) All above constraints help you build a truly RESTful API and you should follow them. Still, at times you may find yourself violating one or two constraints. Do not worry, you are still making a RESTful API – but not “truly RESTful”.
18. REST vs RESTful REST: architectural pattern RESTful: a service that implements the REST pattern
19. REST != HTTP REST don't enforce the usage of any specific protocol Clients and servers exchange representations of resources by using a standardized interface and protocol
20. Richardson Maturity Model
21. Richardson Maturity Model Level 0 - Remote Procedure Invocation Level 1 - Resources Level 2 - HTTP Verbs and Codes Level 3 - Hypermedia Controls
23. Spring
24. Spring De facto standard framework to build Java enterprise applications Core functionalities: • Dependency injection • Events • Resources • Internationalization (i18n) • Aspect-oriented programming (AOP)
25. Spring Boot Facilitates the creation and setup of Spring applications Provides default configuration for Spring framework and several other libraries
26. Spring Web Spring MVC REST
27. Spring Data Familiar and consistent, Spring-based programming model for data access
28. Spring Data JPA Implementation of Spring Data abstraction using JPA and Hibernate
29. HTTP
30. HTTP Verbs
31. HTTP Codes • 1xx - Informational • 2xx - Successful • 3xx - Redirection • 4xx - Client Error • 5xx - Server Error