I've been reading StackOverflow for quite a while now and I'm only
now building the nerve to ask a question. I'm 20 years old and
currently enrolled in college in IT here in my hometown (Cluj-Napoca,
Romania). Enough for introductions :D.
Basically I have
my little software firm that provides Book-keeping appz. They're
(horrifyingly) written in Delphi and I want to start from scratch and
write them in Java. I've had little experience with Java in the past
but I want to learn and I've chosen Java because of the cheap and
quality tools the platform offers.
Now could you please
point me to the right direction as where could I find some complete
I want to design a DAO layer for may application , which will be used
by web-applications and core java programs also.
Fist is it a good approach to have webservice for each database
I am planning to configure connection pool in context.xml of tomcat
Access the data-source using spring , perform operation using jdbc
I will use batch update in few places where i need to process requests
The above URL will be call from various internal applications
to communicate with database.
Per day requests expected 10-Million Inserts , 20-Million
Updates, 20-Million selects.
Concern: Java, Tomcat , DB oracle and mysql are
the technology constraints -
Which approach will be the fastest and salable way dealing with
huge database operators.
Can spring handle huge requests, is it a good approach to have a
web-service to perform database operations.
Note: I don't want to bloat my applications by
writing database connection every where by accessing from a properties
file, that is the reason going for context declaration with pool
I'm working on a layered business application written in Java that
should be packaged as an EAR file and deployed to a JBoss application
server. There's a web-application layer, a service layer, a domain
layer but no persistence layer. At least on paper.
the best practice for deploying the different layers? In our team we
have a little religious war going on between:
layer in its own JAR file (e.g. in its own Maven module), and adding
each module to the EAR file, OR
Bundling everything together in a
single JAR file, with each layer mapped to a package naming
Are there other possibil