• Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Finally experience is a must

 
Akar Rafidj
Ranch Hand
Posts: 44
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm a good developer, with 5 years experience but too young to have a real experience in architecturing performant and scalable J2EE systems. I was facing one big problem: what architecture and J2EE technologies should i select. I have 5-6 ways to do it....all seem to meet functional and non functional requirements. What is the best way? Only experience could help me....
Since 15 days,i'm doing and redoing the assignment 2 hours a day.Each time i ask my self: Is what i'm doing the best choice ?
I think that the best and only choice is the simplest way...I hope ....!

Akar
 
Jeremy Hsu
Ranch Hand
Posts: 79
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

When you are architecting in the real world, there is a set of constraints, such as amount of budget, development time, number of senior developers and their knowledge on J2EE, and also what actual J2EE servers you are using.

And yes, there are several ways to solve the problem, but there is only one way that might satisfy those constrant.

Your role as architector needs to find one solution that fits those constraint.

In my opinion, when you are facing with many solutions, pick one that is simplest to implement. Because in the real world, shorter development time means more time for testing and QA, and therefore, you can pinpoint the problem of your system earlier and can focus on performance tuning that part of the system.

Also, you should study more on different approaches of software development lifecycle because that might affect your architecture decision.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic