Muhammad Usama Bin Islam

So I'm a senior working as a senior software engineer for the past two years. And before that, I was in the industry for the past six plus years now. So the projects I embarked on are related to the health care sector, IoT, and the education sector, where I was working on some admin assistance for schools in Canada. And I also have experience in working on financial services, providing financial services software. So the back-end technology I am most comfortable with is Java and the Java framework. Regarding frameworks, I have experience working with several projects related to the fields I just mentioned. So from the database side, I have worked on Oracle, PostgreSQL, MySQL, MSSQL, and from NoSQL, I have worked on MongoDB and Cassandra and Cosmos DB from Azure. So yeah, and I am leading a team of 14 members at the moment and also taking an active part in that development. I know how to organize. Currently, the project I am working on is deployed on Kubernetes. So I also have experience in Kubernetes from source code control. I worked on Git Bitbucket and GitLab. So on the cloud side, I have experience working with Azure and AWS. And on AWS, I have worked with Lambda functions, deploying the application on ECS using the Elastic Container Service. So yeah. And on Azure, I have experience working with Azure DevOps for deployment of the application. I also work on CPU systems with integration, and that particular system was integrated with Salesforce. So, other than that, I am comfortable working in any environment.

So if I am, I want to update a front-end component without causing downtime in Kubernetes. I will take the help of the versioning system of Kubernetes. I will deploy another version of the port for the front end. And once that is deployed, version 2 is deployed and working correctly, I will close version 1 and only version 2 will be working. Thank you.

If I'm deploying a set of services on Kubernetes and I want to ensure they interact properly with the live stream instance, I will take it from the Liferay DXP portal to divide those particular microservices. Liferay provides all of the management systems. We can deploy the microservices on Kubernetes or use the tools provided by, like, for instance, and I will make sure they are interacting properly from the portal.

So, for, preventing the CSS styles from conflicting with the global styles, I will, I can't answer that. This particular thing is not

So, for that too, I will take care from the Liferay and, with the help of Liferay, it provides all of the functionalities for managing things like that. So, I will make use of the package provided by the LifeView portal to efficiently handle errors and, for logging, I will also use LifePlay libraries instead of any other.

So for avoiding the circular dependencies, the technique I mostly use is to exclude the specific dependencies from the package which I am including to divide the circular dependency thing. So, I exclude the packages which are not already added in the Maven and they should not be added again.

something seems out of the way what is wrong with this implementation so this public class singleton private static singleton instance private singleton public static singleton getter instance is equal to equal to null one thread to work on it to work on a specific so we are using the synchronized keyword on the singleton class so that only one thread is accessing this particular chunk of code at one time so the condition if instance is equal to is equal to null that is not the first condition that is not under the synchronized block so then all of the threads will be waiting inside this block to get its access so we should remove the first if condition so that the blocks are checking it but they will come in the second one and then again there is an if condition there we are checking if instance is equal to null we can remove the first condition that is there without any use after that it is return instance if instance is equal to null so the complete singleton class is in a synchronized block so it will hinder the threads to access this particular class if we are working in a very threaded environment other than that I don't see any issue here.

So here, we are using two, then. We can just move the second "then" with the first and then we are there is no need for two "then" conditions.

For providing check safety for a screen service in multiple porta system, like freight porta. So for doing that, what I will do is first, I will use the collections which are thread-safe. And, I will not use a hash set. I will use a hash table for all of the functionalities providing in that. Is saying if there is something I want only one thread to access at a point, I will use synchronization for that purpose.

So for implementing responsive design, I follow the standards provided by Liferay team for the screens that are by default in Liferay. I try to abide by them and do the styling accordingly.