π I'm a full-stack handson architect with proficiency in Java, Spring, Springboot, AngularJS, and React JS.
π Certified in Oracle certified Java Programmer
π Certified in Oracle certified web component developer
π AWS certified Architect Associate
-
π Iβm currently working on building an application in Azure platform with Springboot on Azure AKS, Docker, Angular with hosting on Blob Storage with Azure AD authentication.
-
π± Iβm currently gaining more expertise/ proficiency on Python with Machine learning and Big data.
-
π― Iβm looking to collaborate on React based web apps.
-
π¬ Ask me about Cloud Migration, Enterprise Architecture, Cloud based web applications with Java.
-
β‘ I mostly keep updated with new technologies and I recently started pushing my POCs to Github.
-Java -Nodejs -J2ee -Servlet -JSP -Struts -SOAP -Rest -Spring -Springboot -MicroServices -GraphQL -GraphDB -AWS -Kubernetes -Docker -Redis -ELK, DynaTrace -API Gatway -Angular -ReactJs] -Mysql, Oracle, DB2, Mongo, Redis -Jboss -Kafka -SQS -Kinesis Streams -Websphere -Tomcat -Mockito -Jasmine -Jest -Jenkins -Linux -Test Driven Development, Domain Driven Development -Architecture -Distributed tracing using Zipkin -Coaching and mentoring team of developers -Agile-Scrum -Agile-Safe -Python -Machine Learning in progress -Hadoop long back -Technical thought leadership -Solving technial issues of team members -Leading design and architecture discussions, code reviews and ensuring teams follow modern engineering practices -Very strong knowledge of all development tools like Intellij, GIT, Maven, Artifactory, Github, Gitflow -Ability to work in large, collaborative teams to achieve organizational goals -Champion the adoption of reusable architecture assets to improve efficiency -Performance Tuning and troubleshooting
Non Functional Requirement
A non-functional requirement defines the quality attribute of a software system.
It is not mandatory.
Applied to a system as a whole.
Usability requirement Serviceability requirement Manageability requirement Recoverability requirement Security requirement Data Integrity requirement Capacity requirement Availability requirement Scalability requirement Interoperability requirement Reliability requirement Maintainability requirement Regulatory requirement Environmental requirement<\br> Portability Reliability Performance Reusability Flexibility
examples of NFRs: availability, scalability, reliability Audit trails Logging requirements , zipkin response time number of simultaneous users supported portability between onpremise & multi cloud? Non-Functional Testing like Performance, Stress, Usability, Security testing, etc.
- External Configuration : externalizing credentials using Azure Vault or Hashicorp Vault etc.
- Cache Aside : This is a standard Caching pattern where we cache most frequently used read only data.
- Federated Identity : oauth2 using Azure AD, siteminder etc.
- Valet Key : This is similar to providing a token by Azure Blob or AWS S3 for temporary time/ used based access.
- Gatekeeper : Example Web Application Firewall in AWS.
- Circuit Breaker: In a micro service environment when one of the service is not working the micro service will open the circuit and a gracefull error message/ valid values is sent back to the calling service.
- Retry : retry when some external service fails transiently.
- Strangler : incrementally migrate a legacy system, gradually replace functionality of application.
- Availability Patterns
- Data Management Patterns
- Design and Implementation patterns
- Performance and Scalability Patterns
- Resilience patterns