After finishing the first version of the IRATA Android App, the next was to integrate it in the Gitlab-CI process.
Since the AuctionService comfortably sits in its Docker Swarm it’s time to actually use it with a first version of the IRATA Android App. Which would also bring me a step closer to becoming a Full Stack Developer (at least a little one
When looking at job descriptions these days the term “Full Stack Developer” pops up increasingly. I now what a stack trace is but not really what “Full Stack Developer” means.
Now that I finally got the ELK stack running and collecting the logs from my two “Auction-Service”-instances, it is time to check whether Docker swarms load balancer really does distribute the requests.
This post describes how I set up a first version of the auction service that serves as the basis for all my docker swarm examples.
The first version will be very basic. In alter iterations I plan to enhance the API so that it more and more resembles the behavior of the auction in M.U.L.E.
The git repository for the service can be found on gitlab: IRATA repository on Gitlab
My machines are up and running so lets install a docker swarm
Activate swarm mode
The first thing to do is to create a master. In this case it will be the host
with the name silentmaxx
docker swarm init --advertise-addr 192.168.0.1
The output of this command neatly tells you what you have to do to add a worker:
docker swarm join --token SWMTKN-1-5f975dx6krnusynvs0dzk1snhnpqrm3je3lg4h0gcr7q98aoo7-erdjldlq2yodjrov1v57db6yz 192.168.0.1:2377
Setup machines for Docker
Now that vision and technology has been defined I start with setting up an environment for my project.
Setup the nodes for the cluster
Docker swarm needs at least three nodes (one master and two workers) in order to run.
These could be virtual machines or physical machines. You could even use Docker in Docker DinD to create the nodes of the swarm cluster.
There is a great post on how to do that here.
It’s been a while since I started working on actual application design and delivery in a cloud environment. Since a lot has changed since my first tries and experiences, I decided to continue this project incorporating my new insights and ideas.
The second hurdle on the roadmap to the Certified Cloud Architect is the “Cloud Technology Concepts” module and corresponding exam. The emphasis in this module is on looking at cloud technologies that enable some of the cloud characteristics already covered in the first module. Continue reading Cloud Technology Concepts
This first exam of the path to the Cloud Architect certification and covers the basic terms and concepts of cloud computing as defined by Thomas Erl. Continue reading Fundamental Cloud Computing Terminology and Concepts