Design Patterns and Best Practices in Java

Independence from infrastructure planning

One important and core idea of this whole exercise is to realize that we have created an API without setting up any machine or server. We simply created a JAR file and uploaded on Amazon. We are not worried about load or performance anymore. We don't think about whether we will use Tomcat or Jboss or any other server. We are not thinking about whether the API will get one hit or one million hits in a day. We will only pay for the number of requests and the computational power used.

Please note that we used the API to call the function and returned a simple message. Much more complex implementations are supported easily. For example, a function can be triggered from a message queue, database change, ...