All important actions happen on the server side. User state stored in server side sessions. Server side has control.
1 of 16
Traditional methodoligies:
Model 2, CGI,Component Oriented, Event Driven, Filter chains.
2 of 16
Monolithic Web Applications
Data in many places. Session, forms, request parameters, DAO objects. Easy to lose track of things.Lots of plumbing code. Low cohesion. Maintenance is difficult.
3 of 16
Web Applications vs Web Servies
Web Apps produce web pages(HTML) designed to be consumed by humans via a web browser.Web Services produce structured data designed to be consumed by another computer(M2M).Use web servers in similar ways. Primary diff=HTTP req&rsp bdies diff format
4 of 16
Traditional b2b communication
Person acts as bridge between systems (on phone). Modern B2B is M2M - one is client and one is service role.
5 of 16
What is modern about that?
Traditionally DISs used network protocols and frameworks specifically for M2M. Could be expensive.
6 of 16
Whats great about Web Technologies?
Simple, flexible, Standardised, Pervasive, Tend to be allowed through firewalls.
7 of 16
XML & JSON can be used to encode domain objects
both are text, both provide context to the data they encode, but have huge library support
8 of 16
RPC
RPC (remote procedure call). Client sends req that describes a method call. Service receives req, calls method & sends result back in response to client.
9 of 16
Types of Web Service - REST
Representational State Transfer: Makes better use of HTTP for managing resources
10 of 16
REST
Resources = domain objects. HTTP verbs: GET POST PUT DELETE. Product details are encoded in JSON - easy for other apps or services to consume. Operatiosn can easily be mapped to DAO ops.
11 of 16
REST API Design
Made up of: URIs that represent resources (indiv or collections). Operations that the resources support. operations = GET POST PUT DELETE
12 of 16
Microservices
Services are a unit of modulation. System is a collection of services. High cohesion, low coupling. A service provides a single function.
13 of 16
Microservices are stateless
STATELESS=Dont store state on behalf of clients - no server side sessions. Allows services to become disposable. Means we can run many redundant services for load balancing.
14 of 16
Jooby
Microservice framework Java. Runs on Netty (web server). Very flexible
15 of 16
Jooby with JSON
adding a JSON filter (GZON) to the filter chain means all message bodies are JSON.
16 of 16
Other cards in this set
Card 2
Front
Traditional methodoligies:
Back
Model 2, CGI,Component Oriented, Event Driven, Filter chains.
Comments
No comments have yet been made