Rakesh K

Both tools are powerful, fast, in-memory data stores that are useful as a cache. Both can help speed up your application by caching database results, HTML fragments, or anything else that might be expensive to generate. Points to Consider When used for the same thing, here is how they compare using the original question's "Points to Consider": Read/write speed : Both are extremely fast. Benchmarks vary by workload, versions, and many other factors but generally show redis to be as fast or almost as fast as memcached. I recommend redis, but not because memcached is slow. It's not. Memory usage : Redis is better. memcached: You specify the cache size and as you insert items the daemon quickly grows to a little more than this size. There is never really a way to reclaim any of that space, short of restarting memcached. All your keys could be expired, you could flush the database, and it would still use the full chunk of RAM you configured it with. redis: Se...

Phases within the ADM are as follows: The  Preliminary Phase  describes the preparation and initiation activities required to prepare to meet the business directive for a new enterprise architecture, including the definition of an Organization-Specific Architecture framework and the definition of principles. Phase A: Architecture Vision  describes the initial phase of an architecture development cycle. It includes information about defining the scope, identifying the stakeholders, creating the Architecture Vision, and obtaining approvals. Phase B: Business Architecture  describes the development of a Business Architecture to support an agreed Architecture Vision. Phase C: Information Systems Architectures  describes the development of Information Systems Architectures for an architecture project, including the development of Data and Application Architectures. Phase D: Technology Architecture  describes the development of t...

Initial Stands for (acronym) Concept S SRP Single responsibility principle a class should have only a single responsibility. O OCP Open/closed principle “software entities … should be open for extension, but closed for modification”. L LSP Liskov substitution principle “objects in a program should be replaceable with instances of their subtypes without altering the correctness of that program”. See also design by contract . I ISP Interface segregation principle “many client-specific interfaces are better than one general-purpose interface.” [5] D DIP Dependency inversion principle one should “Depend upon Abstractions. Do not depend upon concretions.” [5] Dependency injection is one method of following this principle.

Importance of Source code review

JProfiler Features in detail: http://www.ej-technologies.com/products/jprofiler/features.html Yourkit Features in detail: http://yourkit.com/features/index.jsp Almost neck to neck competition between JProfiler and Yourkit: Both JProfiler and Yourkit Profiler are leading profiling tools. Few additional widgets like open/closed sockets, Loaded classes , JSP/servlet requests status available in Yourkit, which are not available in home screen in JProfiler, but you can get the same information with few set of clicks. Less expertise and tutorials available over the internet for Yourkit compare to JProfiler. When we talk about Industry wide use: JProfiler wins over Yourkit. Both display the information while the program is running. Both are very easy to use, compared to the other tools in their class. Both have remote profiling options, which is useful for PROD/QA/UAT server’s profiling. Doesn’t require any special preparation or setup in both the profiling tools. Both integ...