Azure stories. Azure and Java

There's always a story to tell behind the stage, and this is one of many why I like VSTS (Visual Studio Team Services). 
Recently I was working with a client trying to find the best cloud architecture for their project. 
The small problem was that they we're writing in Java and I am a Microsoft Technology Stack, so the first problem I encountered was how to start because I know 'something' about cloud and azure but I don't know how to proceed with web applications wrote in Java.
The easiest way is to Google something... but Googling something isn't enough because you can Google only the source code and you need something up and running ready to show.  The running something is the biggest problem here - how I can build Java, how to test it.
So I have some skills in DevOps in VSTS, i love VSTS and i like creating Continuous Integrations on it. 


 So what I did 

  1. search to get any website in Java. Simple Hello World will be enough. 
  2. download it. Store in Git repository on VSTS to have all the permissions to repository I needed.
  3. created a build, so VSTS makes a package for me.
  4. deploy to azure.
  5. up and running (?)

Of course I need to Google it how to make a build because I didn't know that Java is build by Maven.
When the build was successfully ended I had a package that I could deploy to Azure infrastructure and just have an application up and running in few minutes. Well maybe few more because there is still few options on Azure side that need to be configured, and the bigger choice the bigger decision problem.

 So I want to show how to create a build for Java website and then have to Deploy it Azure. Azure gives us a lot of options for the application deployments and I don't know if I can cover all of them. Will start with the most useful. 
This is just an introduction technical stuff will come later.

Popular posts from this blog

Azure post deployment scripts

Image
Let's do a trick. After deploying application (that was easy with Ftp or Git ) it would be nice to take some action. For example send an email, or write release notes to release page. I will do much fancier thing - I will write some text to console output.
Read more

Mobile view lifecycle. Fixing Xamarin.Forms Page lifecycle

Image
For mobile applications the highest priority is user. What user can see and interacts with. Application should react not only on user interacting with it but also user interacting with operating system. That's why not only application has it's own lifecycle but also "view" has it's own lifecycle. In Android view is represented by activity, or a fragment (the right side of android diagram). In iOS view has it's own set of lifecycle methods. In both cases view has the information that application(in this case view itself)  is being suspended and reactivated. View know quite a lot about outside world and view lifecycle is very similar to application lifecycle. Compare below first application and then view lifecycle diagrams: In Android view is represented by activity, or a fragment (the right side of android diagram). In iOS view has it's own set of lifecycle methods. In both cases view has the information that application(in this case view itself)  is
Read more

Mobile application life-cycle Android vs iOS vs Xamarin.Forms

Image
Lifecycle. One of the most common recruitment questions. No matter what technology you work with this is something that should be well known and understood. It's good to know how application behaves, what it is allowed depending on its state and when to react on specific lifecycle events. In mobile world lifecycle is even more complicated because there is no 1 answer but 3 in this case: Android. iOS. Xamarin.Forms. I use also Xamarin.iOS event names in my diagrams, but the sequence is the same. Lifecycle is the definition when your application have access to resources and when react on state change. For mobile the biggest priority is what user can see and interacts with, so active application have priority in using system resources. System has limited pool of resources, so  applications running in background (not visible to user) is limited by system in how much resources can it use and also system decides when application needs to release all resources (be closed/killed/end o
Read more