My journey: Dockerized Java on Apache Mesos Container cluster on Azure – Setup Mesus cluster on Azure

Friday, September 2, 2016

At the end of the last post (see here) we finished when we have an "Automated Build Repository" on Docker-Hub. Now we need a containers platform to run it. I decided to use the Apache Mesus open source solution, when the cluster located on Azure cloud. Step 1: create the Apache Mesus cluster. Login to Azure Portal using this link. Press on the + New link On the search box write "Azure Container Service" The filter slide will open with the "Azure Container Service" text. Select the DC/OS on Azure container. Press the "Create" button. Step 1-Tag: create the SSH - Keys. I...
no comments

My journey: Dockerized Java on Apache Mesos Container cluster on Azure – Setup a Docker (Part II)

Thursday, September 1, 2016

At the previous post we manage to create Automated Build Docker Repository. Now we need to create and configure the Docker. Now we have the skeleton and it's the same skeleton for all Docker types, whether it will hold Java / Python / Scala / .NET Core container, the skeleton is the same. Environment Setup - Linux So, we need an environment to work with the Dockers. I myself prefer to work with the Linux Server for that, I sure that there are another alternatives. Sill the terminal approach more clean to do so. I'm using Ubuntu 16.04 server on Oracle VirtualBox. (if...
no comments

My journey: Dockerized Java on Apache Mesos Container cluster on Azure.

Friday, August 26, 2016

I want to start this journey from the basic. Although I'm pretty sure that Docker software solution are known knowledge, the all pack should cover it all. So, what we talking about it to take an exiting solution provided by Docker Hub and second solution provided by Apache Mesos and set it on a 3rd IaaS cluster solution stored on Azure. The main idea is to do it well and not step on each other toes. The project System Architecture. The project will contain the next layers: The Azure Cluster which contains the Mesos cluster. This part will be an IaaS solution...
no comments

Visitor Pattern

Monday, April 21, 2014

After I wrote the previous post I understand that must of the time by accident we couple the logic to the model too much, and that all in the name of capsulation. Let’s take for example the next Classes: We can see here 3 concrete Classes that diverted from SmartDevice Class. Tables, Phones & Watches. As you can see I reviled 4 methods here (I you can imagine there are more than that), By from my point of view under 2 categories: Close Method: No change on the logic, no extension required Support3G: By the device spec, or it’s supported of  not MemorySize: The same...