Recently I conducted many interviews for my employer, one 8-9 yrs exp candidate asked me what data access object layer do we use in our project. I was thinking a bit as , like they do with persistence - polyglot persistence, we maintain different DAO technologies - JPA, proprietary JDBC, JDO, Spring JDBC. you cannot say which one is the best. It depends on the context but definitely having so many things for performing dataaccess is not advisable. In this topic I will try to explore the JPA and Spring JDBC. Spring is a life savior, it's template concept reduces the boilerplate code but still the jdbc template comes with baggages - row mapper, SQL, parameters etc. If you have good knowledge of database schema, you want to execute stored procedure, you want more handle on your code to access the db. Then go for Spring, you can debug easily and have control on your DTO. If you need to abstract away the SQL, hide complexity, write less code, dont need to execute the stored proced...
NSSM logstash service can cause a fatal CPU hungry outage in your clients unless you override the AppExit default value. By default it comes as default 'Restart' To change it to ' Stop service ' you need to run the following command nssm set logstash AppExit Default Exit It will change the service definition as follow Other v alid exit actions are: Restart Ignore Exit Suicide
I have been using GWT and MVP for 2 years and so. I loved the way MVP provides flexibility of working with multiple views. In GWT or Swing based application design muddles very quickly. Maintenance becomes nightmare. We don’t think about the separation of concern, then mix up the UI code and business logic together. MVP (Model View Presenter) proposes following things - · View is an interface which is a contract for presenter. here you can define the operations and expose widgets that will be present in the UI. for example if an UI needs an input box for user name and a button then you can expose two methods getName() and getOkButton(). Get name can be implemented using whatever widget user wants- a textbox or a custom widget. · View implementaion implements the view interface and only concentrate on layout or grouping of widgets. Doesn't perform and logic, doesnt attach any DOM handler to any wi...
Comments
Post a Comment