Embark on a journey of knowledge! Take the quiz and earn valuable credits.
Take A QuizChallenge yourself and boost your learning! Start the quiz now to earn credits.
Take A QuizUnlock your potential! Begin the quiz, answer questions, and accumulate credits along the way.
Take A QuizKindly log in to use this feature. We’ll take you to the login page automatically.
LoginGeneral Tech Technology & Software 3 years ago
User submissions are the sole responsibility of contributors, with TuteeHUB disclaiming liability for accuracy, copyrights, or consequences of use; content is for informational purposes only and not professional advice.
No matter what stage you're at in your education or career, TuteeHUB will help you reach the next level that you're aiming for. Simply,Choose a subject/topic and get started in self-paced practice sessions to improve your knowledge and scores.
Kindly log in to use this feature. We’ll take you to the login page automatically.
LoginReady to take your education and career to the next level? Register today and join our growing community of learners and professionals.
Your experience on this site will be improved by allowing cookies. Read Cookie Policy
Your experience on this site will be improved by allowing cookies. Read Cookie Policy
manpreet
Best Answer
3 years ago
I have a few applications that needs to be migrated from one technology stack to another.
Please refer below for sample dependencies:
Example:
Stack 1:
d1-stack1, d2-stack1, Java 7, Apache CXF, Spring 3, ..... .. etc.
Stack 2:
d1-stack2, d2-stack2, Java 8, RESTEasy, Spring 4, ..... .. etc.
Here, d1-stack1, d2-stack1 etc. are maven projects that are used in these applications as dependencies and these dependencies also needs to be migrated to new stack.
In order to migrate all the applications and their dependencies smoothly, I am thinking of abstracting out the applications' dependencies behind common interfaces (Facade, Adopter etc.) and then I am thinking of using maven profiles (stack-1 and stack-2) for adding the dependencies for respective technology stacks for build.
Do you think this approach will be helpful in long term? Will there be any blockers?
Please note dependencies like d1-stack* and d2-stack* will have different framework dependencies for both stacks.