What are java ee (Enterprise Edition) architects?

As information technologists, we are faced with the decisions concerning technology choices, designs, approuches or patterns. These decisions can be overwhelming and often the initial decisions can lead to the overall success or failure of the associated execution projects.

When we talk about this process, we relate it directly to the building construction industry. It has long been known that the skillset, experience and design knowledge that goes into the construction of buildings, is the domain of the architect. Software is no different. Software architecture is almost an exact mirror of the construction architecture domain. Each area of the design of the building or software can benefit from an existing design or pattern of construction from a previously successful implementation. There are also almost always, new techniques, new materials and tools, and new thinking, which needs to be carefully considered for applicablility. There is almost never one way to build a building or a software solution.

Software architects carry this responsibility. How to best make use of the available materials, and labor, to produce the best fit solution to the problem.

When faced with a development requirement, companies need to choose what technology set to use. They often turn to technologies which are already used and established in the organization, based on the experience of the current staff, and existance of current reusable code and patterns.

Contact us now to learn more info@javadojo.com

There has recently emerged two choices of tooling to persue. A Microsoft toolset, or a Java toolset. Both have similar product offerings and technology portfolios, however each is a vastly different approuch to the same problem set. For this reason, staffing a project for either technology can involve a completely different group of people. There are in fact very few overlaps. If the decision is to go with the Java technologies, there are once again a large set of choices for each area of the design. Careful consideration needs to be taken to make sure the technology choices live together harmoniously, and do no create additional or unforseen problems, well down the construction path. It is therefore highly recommended to make these decisions with the help of an experienced and well rounded J2EE architect. Somebody that has built complete solutions in Java, from the original versions, through to the later Enterprise editions. Someone that has made the mistakes before, and knowns which combinations, implementations and API's work best together, and which introduce complexity, expense and bottleknecks.

JavaDojo j2ee architects have been down this road many times, on projects aimed at constructing various different types of solutions, for varied requirements, users and hardware platforms. All this experience has produced the patterns, tooling, reusable libraries and intellectual property that make these architectural decisions easier and more reliable. Contact JavaDojo and have a chat to one of our architects. We will help you make the right decisions.

Contact us now to learn more info@javadojo.com