Skip to main content

Microservices - tools and implementations

UP1: If you are planning to migrate to Microservice, we recommend you to read the book "High performance in-memory computing with Apache Ignite".

One of the challenging thing in Microservices world is not the implementation of the services, rather it's monitoring and the management. In the time of writing the blog, we have a few frameworks and tools to implements microservices such as Dropwizard, Spring boot and vertx. Complexity grows when you have a lot of independent micro services deployed and running over cloud infrastructure. It really a pain full task to monitor and manage all the services through 24*7. However Ansible, puppet, docker and logstash tools can help you to build such a management platform for micro services but they are not always sufficient. To solve the above described problem Jboss project release such a management tool for micro services named fabric8. Fabric8 provides following possibilities such as management, continuous delivery and simple integration platform based on Apache Camel project. This open source project based on google kubernetes and openshiftV3. Every application deployed in fabric8 is independent and running in separate java container, which you can stop, start or restart. Any moment you can increase or decrease the number of instance of any application in fabric8 with a single mouse click. In this blog i am going to quick start with fabric8, install and run in a single machine and will try to deploy one simple application from it's quick start example.
For installation of fabric8 you can follow the getting started guide, i have choose the Vagrant way. If you already familiar with Vagrant and docker then installation process will be easy for you. If everything goes fine with your installation you should have the following page.
Now you can play with some of the pre installed application, for example quickstart-rest. If any of them is not running, you can check application logs. If you will got following errors in web console or in any application log:
index.docker.io: no such host
add the following name server in you /etc/resolv.conf file and restart the docker instance
nameserver 8.8.8.8
nameserver 8.8.4.4
sudo systemctl restart docker
Now we can clone the quick start project from the git hub and try to deploy any of the example.
The example is well documented but for the first time it may not works.
Build the docker image
mvn package docker:build
if you will get error something like these
index.docker.io: no such host, you should add the following IP address in you /etc/hosts host machine.
52.0.31.125 index.docker.io
52.0.31.125 registry-1.docker.io
If you are using vagrant image in an single machine, do not need to push the image in the docker hub, rather than you can apply kubernetes configuration to the installed platform. 
mvn fabric8:apply
Above command will deploy the given application with meta data to local fabric8.
Now you can increase the instance of the application by clicking the pod column and try to invoke the servlet by the following URL:
http://quickstart-camelservlet.vagrant.f8/camel/hello?name=shamim
the result should be as follows:
From here you can develop your application with maven archetypes provides by fabric8 team and enjoy your micro services.
Labels:

Comments

Post a Comment

Popular posts from this blog

8 things every developer should know about the Apache Ignite caching

Any technology, no matter how advanced it is, will not be able to solve your problems if you implement it improperly. Caching, precisely when it comes to the use of a distributed caching, can only accelerate your application with the proper use and configurations of it. From this point of view, Apache Ignite is no different, and there are a few steps to consider before using it in the production environment. In this article, we describe various technics that can help you to plan and adequately use of Apache Ignite as cutting-edge caching technology. Do proper capacity planning before using Ignite cluster. Do paperwork for understanding the size of the cache, number of CPUs or how many JVMs will be required. Let’s assume that you are using Hibernate as an ORM in 10 application servers and wish to use Ignite as an L2 cache. Calculate the total memory usages and the number of Ignite nodes you have to need for maintaining your SLA. An incorrect number of the Ignite nodes can become a b...
Post a Comment
Read more

Apache Ignite Baseline Topology by Examples

Ignite Baseline Topology or BLT represents a set of server nodes in the cluster that persists data on disk. Where, N1-2 and N5 server nodes are the member of the Ignite clusters with native persistence which enable data to persist on disk. N3-4 and N6 server nodes are the member of the Ignite cluster but not a part of the baseline topology. The nodes from the baseline topology are a regular server node, that store's data in memory and on the disk, and also participates in computing tasks. Ignite clusters can have different nodes that are not a part of the baseline topology such as: Server nodes that are not used Ignite native persistence to persist data on disk. Usually, they store data in memory or persists data to a 3rd party database or NoSQL. In the above equitation, node N3 or N4 might be one of them. Client nodes that are not stored shared data. To better understand the baseline topology concept, let’s start at the beginning and try to understand its goal and what ...
Post a Comment
Read more

Benchmarking high performance java collection framework

I am an ultimate fan of java high performance framework or library. Java native collection framework always works with primitive wrapper class such as Integer, Float e.t.c. Boxing and unboxing of wrapper class to primitive data type always decrease the java execution performance. Most of us, always looking for such a library or framework to works with primitive data type in collections for increasing performance of Java application. Most of the time i uses javolution framework to get better performance, however, this holiday i have read about a few new java collections frameworks and decided to do some homework benchmarking to find out, how much they could better than Java native collection framework. I have examine two new java collection framework, one of them are fastutil and another one are HPPC. For benchmarking i have used java JMH with mode Throughput. For benchmarking i took similar collection for java ArrayList, HashSet and HasMap from two above described frameworks. Col...
Post a Comment
Read more