Java experts please come

[Pichkaari]

So, Ma applications lo Spring MVC design flow is like UI request <-> Backend Controller <-> Service layer <-> DAO <-> Database ..

Last week interview lo .. Ee design ni ela better chestav ani asked.. but I'm not sure if there's any other design to make it better.. Any ideas?

Also, What type of authentication you guys use to send data from UI to backend?

 

 

[dasara_bullodu]

Controller ki service layer ki madhyalo REST API rastanu so that distributed architecture ki flexibility pergutundi

[Pichkaari]

Just now, dasara_bullodu said:

Controller ki service layer ki madhyalo REST API rastanu so that distributed architecture ki flexibility pergutundi

Ardham kaale.. ? Controller is basically rest controller e kada man..

[dasara_bullodu]

Service layer ni business functionality based ga divide chey ...so each service can move into it's own container with own db. This will result in microservices architecture

[dasara_bullodu]

3 minutes ago, Pichkaari said:

Ardham kaale.. ? Controller is basically rest controller e kada man..

Is there a defined API for controller ? 

 

Ante bayta vallaki mee API tho connect cheyyali ante

[Pichkaari]

8 minutes ago, dasara_bullodu said:

Is there a defined API for controller ? 

 

Ante bayta vallaki mee API tho connect cheyyali ante

yeah defined api vundhi .. and based on the URI.. request route aitadhi .. and Microservices is an alternatuv.. but adhi kaakunda.. Same design flow lo  contoller->service->DAO ki inko alternative em vuntadhi ani thinking..

[TOM_BHAYYA]

15 minutes ago, Pichkaari said:

So, Ma applications lo Spring MVC design flow is like UI request <-> Backend Controller <-> Service layer <-> DAO <-> Database ..

Last week interview lo .. Ee design ni ela better chestav ani asked.. but I'm not sure if there's any other design to make it better.. Any ideas?

Also, What type of authentication you guys use to send data from UI to backend?

 

 

Calling java tech lead @Amrita ankul

[alpachinao]

2 minutes ago, Pichkaari said:

yeah defined api vundhi .. and based on the URI.. request route aitadhi .. and Microservices is an alternatuv.. but adhi kaakunda.. Same design flow lo  contoller->service->DAO ki inko alternative em vuntadhi ani thinking..

DAO layer ni kooda rest cheyadam emo

interviewer emi expect chesado manaki emi telusthundi end lo adigi vundalsindi

[pandit]

Replacing Spring-DAO with Spring-Data(SQL+NoSQL support). Makes sense?

[Gains]

may be migrating  to spring boot?..  will make life easier.. as it does all the  configuration by itself... authentication ki shiro

[TOM_BHAYYA]

Just now, Gains said:

may be migrating  to spring boot?..  will make life easier.. as it does all the  configuration by itself... authentication ki shiro

But layer ni thagginchadhu ga...

still you need to mention dao interface 

[MeetFriendz]

ltt

 

[Amrita]

1 hour ago, Pichkaari said:

So, Ma applications lo Spring MVC design flow is like UI request <-> Backend Controller <-> Service layer <-> DAO <-> Database ..

Last week interview lo .. Ee design ni ela better chestav ani asked.. but I'm not sure if there's any other design to make it better.. Any ideas?

Also, What type of authentication you guys use to send data from UI to backend?

 

 

In some projects UI and backend will not be in same application and on same server. Angular vadute node /some other server mida front end deploy chestaru and they have different project in version control say bitbucket. Back end is totally in different project and may be deployed on tomcat or weblogic etc. This way UI and Backedn app are totally independent and view routes request to backend app without being tightly coupled. Also front end change or backend change ki redeployment dependency is also avoided. Also swagger use cheste asalu backend and front end developer ki kuda dependency undadu . I  guess this is what he expected. 

Regarding authentication we can use spring security OAuth. He might have expected you to talk about authentication and authorization related to two legged oAuth. Context of question telekunda cheppadam kashtam but i am guessing this might be what he expected. Hope it helps.

[siritptpras]

Ok

[dasara_bullodu]

19 minutes ago, Amrita said:

In some projects UI and backend will not be in same application and on same server. Angular vadute node /some other server mida front end deploy chestaru and they have different project in version control say bitbucket. Back end is totally in different project and may be deployed on tomcat or weblogic etc. This way UI and Backedn app are totally independent and view routes request to backend app without being tightly coupled. Also front end change or backend change ki redeployment dependency is also avoided. Also swagger use cheste asalu backend and front end developer ki kuda dependency undadu . I  guess this is what he expected. 

Regarding authentication we can use spring security OAuth. He might have expected you to talk about authentication and authorization related to two legged oAuth. Context of question telekunda cheppadam kashtam but i am guessing this might be what he expected. Hope it helps.

What about LDAP Single Sign on ..ippudu clients dani kosam adugutunnaru adi OAuth loki vastunda