The WeakReference class, monitoring memory leak and garbage collection in a Java application

Image
 Below is a Stack implementation that uses an internal resizeable array structure.  public class MyStack< T > implements Stack< T > { private static final int CAPACITY = 100 ; private Object[] array ; private int pos = 0 ; public MyStack () { this . array = new Object[ CAPACITY ] ; } @Override public void push ( T item) { if ( pos >= array . length / 2 ) { Object[] newArray = new Object[ pos * 2 ] ; System. arraycopy ( array , 0 , newArray , 0 , array . length ) ; array = newArray ; } array [ pos ++] = item ; } @Override public T pop () { if (isEmpty()) { throw new RuntimeException( "empty stack" ) ; } @SuppressWarnings ( "unchecked" ) T item = ( T ) array [ pos - 1 ] ; pos -= 1 ; return item ; } @Override @SuppressWarnings ( "unchecked" ) public T peek...

DEVOPS



This table shows imporant aspects of DEVOPS and related software products. The ones that I have used in the past are painted in red. I think this is a very nice table to look at alternative solutions to use for new projects. Of course some of them are essential:

  • Version control. (Subversion,  Git, ..)
  • Build tool. (Maven, Gradle, ..)
  • Testing. Unit Test, Stress Test, UI TEst. (JUnit, JMeter, Selenium)
  • Continuous Integration. (Bamboo, Continuum, ..)

The others seem to depend on the size of the organization and the project. Some use AWS, others manage their own servers. 

Comments

Popular posts from this blog

A Pattern Recognition Problem: Finding Line Segments Effectively In Java

My Crappy Looking Solution to "Binary Tree Common Ancestor" Problem

The WeakReference class, monitoring memory leak and garbage collection in a Java application