Skip to main content

Defining datasources in Application Vs App Server



Defining datasources in Application

  • Pros
    • Avoid configuring client's application server  
    • Useful in development stage to just change the parameters and build and deploy 
  • Cons
    • Cannot use same build for Dev, QA, UAT and Pro. that may leads to minor problems 
Defining datasources in App server

  • Pros
    • More secure by having it in app server configuration builder will not have the credentials to the clients DB 
    • Can make war file smaller having DB modules in app server
    • Can use same war file in multiple places (Test, Production and different clients) 
    • Can use same build for staging and make sure that application works perfectly 
    • Easy deployment 
  • Cons
    • Based on the different clients having different application servers would take some time to configure 

Comments

Post a Comment

Popular posts from this blog

Prototype Design Pattern

Prototype Design Pattern is a creational design pattern which will be used when there is a need to create multiple object with the same class and will be involved in lot of configurations. By using Prototype Design pattern we can clone a existing object with same configurations values, with same property values into a different memory location, that will exclude the costly operations. This will save us both time and resources. When to use? and Why? Creating new objects by cloning other objects. Allows for adding any subclass instance of a known super class at run-time when there are numerous potential classes that you want to only use if needed at run-time. Reduce the need for creating sub classes public interface Shape extends Cloneable {            public Shape makeCopy(); } public class Circle implements Shape {            public Circle() {                 ...
Post a Comment
Read more

Why S.O.L.I.D

Why S.O.L.I.D SOLID principles are design principles that enable us manage most of the software design problems. Objective of SOLID is to make software design more understandable, flexible and maintainable. Why SOLID was promoted Rigidity - Every change affects many other parts Fragility - Things breaks in unrelated places Immobility - Cannot reuse the code outside of its origin context Because of these we ended up with these  End up with tight or strong coupling of the code with many other modules. Tight coupling causes time to implement any new requirements, bug fixes and some times creates unknown issues End up with code which is not testable End up with duplication of code End up creating new bugs when changing the code If followed SOLID Achieve reduction in complexity of the code Increase readability, extensible and maintainability Reduce errors and implement re-usability Reduce tight coupling S.O.L.I.D Principles Single Responsibility...
Post a Comment
Read more

Redirect to a url after login - Spring Security

If you wa nt the browser to remember the url that you enter before login and redirect to that url after you login to the application.  XML Configuration - spring-security.xml   What happens after login will be handled by AuthenticationSuccessHandler SavedRequestAwareAuthenticationSuccessHandler will use the saved request stored in the session. After the successfull login the user will be redirected to the original request url.
Post a Comment
Read more