Spring Restfull:

1) Distributed Applications
2) Distributed Technologies
3) RestFull service Introduction
4) Rest Principles
5) XML
6) XSD
7) One time operation
8) Run Tine operation(a. Marshalling b. un-Marshalling)
9) JAX-B Introduction
10) JAX-B Architecture
11) Application development with JAX-B
12) JSON
13) XML VS JSON
14) JACKSON API
15) Converting Java object to JSON and Vice versa(JSON to java object)
16) GSON API
17) Converting java object to JSON and vice versa using GSON
18) HTTP Protocal Details
19) HTTP Methods(GET,POST,PUT,DELETE
20) HTTP Status codes
21) @RestController
22) @RequestBody
23) @ResponseBody
24) @RequestParam
25) @PathVariable
26) Media Types
27) Consumes(JSON data)
28) Produces(JSON Data)
29) Accept Header
30) Content-Type header
31) RestAPI Development Using Spring Boot
32) POSTMAN
33) SWAGGER & SWAGGER UI
34) Exception handling in Rest API
35) REST Security(JWT,OAuth2.0)
36) Mono Objects
37) Flux Objects
38) Rest Client Introduction
39) RestTemplate
40) WebClient
41) Synchronous and Astnchronous Calls
42) Apache Kafka in Spring Boot
43) Redis Cache Spring Boot

Micro Services:
1) Monolith Introduction
2) Monolith Architecture case study
3) Monolith Application Development Process
4) Load balancer(Cluster)case study
5) Load Balancing Algoritham(a.Round Robin, b)IP Hashing, c)Sticky Session)
6) Monolith Drawbacks
7) Micro Services Introduction
8) Micro Services Advantages
9) Micro Services Dis-Advantages
10) Micro Services Case study
11) Micro Services Architecture
12) Micro Services Development(a.API-1, b.API-2)
13) Inter service communication case study
14) Feign Client
15) Cloud Introduction.(AWS,AZURE,PCF)
16) PCF CLI Installation
17) Deploying Micro Services to PCF using CLI
18) Auto Scalling
19) Service Registry case study(Netflix Edurekha)
20) Gateway API(Zuul Proxy)
21) Hystrix(Circuit Breaker)
22) Hystrix Dashboard
23) Spring Boot Admin services.
What is Web Services ?

A)web Service is distributed technology which is used to develop Distributed Application with
Interoperatability.

What is intereopereability ?

A)Irrespective of the platform and irrespective of the programming language if two applications
are then those applications are called as Intereoperatable application

Java----python

Python----,net

.net--Java

In the world of webservices we will have 2 particles

1)Provider

2)consumer

Who is provider?

A) The application which is providing business services to other applications is called provider
application

Who is consumer?

A)The application which is accessing business services form another application is called as
consume application.

In the world of webservices always Development will begin form provider service

->Provider Development can be done in 2 ways

a)contract first approach

b)contract second approach

what is contract?

A)contract mean WSDL

 ->WSDLwebservices description Language

WSDL is a special XML which is describes how provider providing services to consumers.

 Contract First approach means WSDL file be created first then Development will be started.
 Contract Last approach means we will develop the service then we will prepare WSDL for
that.
 Once we got WSDL file, we can start Consuming Development
1)Stub Based Consumer
2)Dynamic Proxy Consumer

-> once Consumer development is completed, consumer will send request to provider

-> Provider will process consumer request and will send response to consumber

Rest Architecture Principles:

1)Unique Addressability

2) uniform Constrains Interface

3)Message Oriented Representation’

4)Communication stateless

5)HATEOS

 Every Distributed component should bind to unique url

 We should write limited and same methods in Distributed Components(http
request methods)
-HTTP GET
-HTTP POST
-HTTP put
-HTTP DELETE
Note: The aim of second is to provide easy accessability & adoptability

Message oriented representation provide support for exchanging data in

multiple format xml,json,text. Etc……..

Note: this principle provides real interapability

 Communication stateless means we should not any information related to
client in server.
 Every request is consider as a new Request


HATEOS:

Hypermedia as an engine for application state

Server should response to client using hyperlinks