Skip to main content

Posts

Showing posts from December, 2022

Tech Conversant Weekly Dec 05 - Dec 10

Topic: General                                                                                                                                              Level: All In this post, we shall catch up on the multi-faceted technological updates that happened over the past week as well as a few that seized my attention, The Garbage collector in JVM abstracts away from managing the memory allocation of the Java application by releasing/dereferencing/defragmenting the object allocated in the memory preventing memory leaks and space depletion. Several GC implementations strategically try to balance on the below parameters for optimal performance of GC, 1. Low latency  2. High Throughput  3. Efficient resources usage (CPU and memory) Typical stages involved in the GC are, 1. Mark (Tracing) - the objects are tree represented and from the application root reachable nodes are painted (LIVE) and unreachable (NON-LIVE) are marked for GC. 2. Sweep - Nonlive objects cleared from the heap memory  3. C

Tech Conversant Weekly Nov 28 - Dec 03

Topic: General                                                                                                                                              Level: All In this post, we shall catch up on the multi-faceted technological updates that happened over the past week as well as a few that seized my attention, How can a DTO contribute to enhancing the security of the java application? A DTO can be a JavaBeans (encapsulated) or POJO (no constructor) or an immutable Record class (added advantage on serialization), that maps the data from the database layer domain model to the presentation layer, restricting the data on a need-to-know basis and acts as a proxy providing filtering and preprocessing. https://snyk.io/blog/how-to-use-java-dtos/ By employing static code analysis tools, the NullPointerException feasibility on the code flow is determined, making the code not only null-safe but also cutting down the exception propagated stacktrace given in the piped code sequence invocation