CODEWITHSUNDEEP
javadeploymentpackaging
IAmYourFaja
IAmYourFaja

Reputation: 56944

Pros/cons to various Java packaging strategies

Let's say I'm writing a Java backend for some front-end GUI (Swing) tool. This backend will consist of many different types of EJBs for middleware/business logic, as well as some web services that filter & forward requests on to those EJBs.

As far as packaging & deployment goes, we have several different possible strategies:

What are the pros/cons of each of these 4 strategies? Are some more secure? Performant? More conducive for clustering/replication? Are some of these strategies just plain silly?!?

Thanks in advance!

Upvotes: 5

Views: 498

Answers (1)

cdeszaq
cdeszaq

Reputation: 31300

Packaging applications has no inherent impact on security. The number of services exposed, individual servers, request endpoints, etc. as well as the way in which the services access resources that need to be protected are what security is concerned with, not how something is packaged.

That said, the main issue you are looking at here is monolithic vs. modular. Once you understand that that is the core issue, all of the existing literature about tradeoffs involved are relevant.

Specifically, you will be looking at:

  1. Scaleability - Many small pieces are more flexible to scale, since you can scale each piece on it's own
  2. Complexity - Wireing together small services allows you to keep the individual services much less complex, since they have to worry about fewer things

Upvotes: 2

Related Questions