Architect Interview Question

ESB SOAP/HTTP JMS FTP FTP No Changes in File SOAP/HTTP N/A JMS N/A FTP   MOVE IT/ UCF   FTP FTP Changes in File FTP   Good to Use   ü   Integrate with more than 2 System/Application ü   Integration between application/System with different   data format/protocol ü   More frequent changes/deployment in provider system , Integration should happens through ESB.It prevents the changes/impact in the Consumer ü   Same Provider Services consumed by different consumer with minimum changes , integration should happens through ESB ü   Any Data Enrichment required during   the Integration th...

Guidelines     ü Business Services should be Stateless ü Services should be reusable ü Standardize the interface contract , Should expose in   CDM ü Each Business Services will expose as 1 or 2 Proxy Services ü Consumer not ready to adopt our business/Proxy services due to data format then will define the Adaptor Services for those consumer only ü Aggregation should be in Process Services/Adaptor services ie Process Service/Adaptor Services will aggregate more than one business services ü NFRS should be in Cross Cutting Manner , we can enable/disable without /minor changes in services level ü ESB will trigger the alert if any unknown exception or services down ü Communication between our Business services and Provider System always through enabler Services(Data Services) . ü Define the Throttling /rating in Service and Operation plus consumer level ü Securit...

C- Consistency A- Availability P- Partition Tolerance It should satisfy the 2 among 3 properties,Not possible to fulfill all the properties CA-System always there with consistent Data Ex: RDBMS AP- System is available But data may not accurate  Ex: DynamoDB CP - Consistent but not available Ex: Mongo DB  

NOSQL - Not SQL Data Base , It used to store the Structure /Non Structure Data which is log/avi/twits/Blogs and etc. In generally prefer the NOSQL in the following 1) Better Performance 2) Horizontal Scalablity 3) HA Category : 1) Key Value - DynamoDB 2) Document - MongoDB 3) Column Based -HBASE Not exists in NOSQL : 1) No Join 2) No Constrain 3) No Complex Transaction

SQL No SQL Data is in Structured Format Accept both Define Schema Dynamic Schema For Transactional Data Not for Trasactional Data Based ACID Property BASED on BASE propoerty and supports CAP Scaled Vertically Scaled Horizandally Supports complex Queries Does not support the Complex Query Based on table based DB Based on Document/Graph/Key Value /Column based Its either Open Source/ Vendors specific Mostly Open Source

NOSQL is used for following usecases 1) Profile Management 2) Customer 360 Degree View 3) Content Management 4) Product Catalog 5) Digital Communication 6) Real Time Operational Data 7) Fraud Detection 8) IOT Things 9) Pesonlization  

Security Implementation in RESTful Web Service : We can implement the Security in various in Web Service Context  . Authentication and Authorization are the Key Factors for Security. Authentication mainly used to check the user credential  to make that user are authenticated and Authorization to make sure whether user has the access for those resource . Both are managed by Active directory access through LDAP . Implementing the Security in RESTful in following ways 1)       Basic Authentication 2)       Digest Authentication 3)       CERT Authentication 4)       App key Authentication 5)       O Auth2.0 6)       Algorithm to generate the Passwords Basic Authentication : Authenticated the User Credential (User name and Password) pass as the plain text and it will validate against the Active Direc...