Test locally first, then deploy to the cloud.

As recommended by Cheuk Chau on Medium, I read 'How to Develop a Daily Writing Habit’ - I’ll try to put it in practice here with my second advise - should have been my #1 advise:

Run a local copy of your application first, before to test it on your cloud instance.

While it’s simple to run directly on the Cloud, and we have a lot of samples available to get started, working local first is the best way to get ready when trouble come your way.

Samples are available from:
One challenge you will face : there are many ways to get code deployed - you need to find the best option for you and your organization. Here are a few :
  1. JDeveloper workspace, using build.
  2. ant build.xml (part of the SDK samples)
  3. maven pom.xml (part of the SDK samples)
  4. java cli (part of the SDK samples)
  5. the web console
The other step important is to check the output of the deployment and minimize the number of error and warning you see.

In one case, I started to look at some error I was seeing first in my Cloud instance, assuming it was a new issue. After a few trials, I finally run another test with my local setup and found that I was getting the same error. I made a mistake while editing some of the source code for my application and did not catch the error with local testing, which would have been cheaper for me.

For my next post, my advise is going to be of a different form - what you should not try. The do not advices are as valuable as the do advises - In some case. you have to learn from your mistakes, but sometime, it’s cheaper to leverage someone else mistakes.


john said…
Can this be only on oracle cloud? how about amazon ec2?

Popular posts from this blog

Changing the version of JDK used by JDeveloper

Connection reset from a WCF Web Service