-
AOP and why you should do it
Aspect Oriented Programming or AOP focuses on processes rather than functionalities. It helps us with cross-cutting concerns such as caching, logging and security. In addition, AOP directs you to mainatin single responsibility and write modular, testable and reusable.
-
Benefits of cross-functional teams
When there is no direct link between the stakeholders and developers, the requirement is passed through hoops to get to the developers and it takes way too long. By the time they are implemented they might not be what the stakeholders wanted or it might be way too late and the competitors have already filled the market with their product.
-
Default configuration can go wrong
Usually when you upgrade a framework, there is a chance you use a default configuration provided by the developers of the framework. Copy and paste. Forgetting the fact that default configuration might not be compatible with your code.
-
Reducing your page load time by serving static files through nginx
Applications Servers or web servers such as Tomcat, JBoss or IIS are normally configured to handle all the requests by passing them to the web applications. The application then processes the request based on the type (GET,POST,...) and also the extension (.html, .do, .jspx, .aspx, ...).
-
How to write/read images to/from MongoDB GridFs
There are many times that you need to save images for your entities, a profile image, or photos of your products that are stored in the database. There are also many ways to save the images. You can save them in the database as BLOB fields (not a good idea) or come up with a folder structure to be able to find them fast and efficient.