What Is The Proper J2EE Architect For This National Defense Project?
posted 14 years ago
A brief description of a national defense project I am looking into is that the system being developed is supposed to verify the "smartcard" of the card holder and his/her fingerprints against the Defense Department database. The system also reads in information about people (facial features, height, weight, etc.) and stores the information in the database, and then issues new "smartcard". 1. People involved in the project already decided to use swing for the client tier. 2. The problem is the Defense Department database. It is a flat file database and this database cannot be touched. It is a black box for Java developers. The Defense Department may provide a jar as an outer layer of this database. Question 1: Is the web tier essential for this defense project? Question 2: What is the proper J2EE architect for this project? Question 3: How to deal with the data problem? Especially it looks that entity beans are not applicable. Question 4: How does the system handle very heavy load? It is possible that tens of thousands of people will use the system at the same time.