Autobahn-Java on Felix Seifert

autobahn-spring: Autobahn|Java and Spring

Sun, 27 Jan 2019 16:24:36 +0000

Are you an enthusiastic user of Spring and do you also want to benefit from the Web Application Messaging Protocol? Even though wamp2spring mainly serves as a router, Spring users often want to create several microservices communicating with each other. A comfortable solution is using the WAMP library Autobahn|Java. This article will describe how to combine Spring and Autobahn|Java.

Create a Controller for WAMP

Autobahn|Java could be implemented as a controller. Therefore, the bean of Spring should be created with the annotation @Controller. Topics and procedures could be handled exactly as described in the article about Autobahn|Java. The methods implementing this should be registered as listeners. This could be achieved in the constructor of the controller.

Autobahn|Java - WAMP Library of Crossbar.io

Sat, 13 Oct 2018 19:35:04 +0000

You have already learned how to set up a local Web Application Messaging Protocol (WAMP) router. This article would describe how to make the first step in programming a microservice in Java using the library Autobahn|Java and, thus, how to use a WAMP router.

Idea of Autobahn|Java

A WAMP network usually consists of a router and multiple clients. The clients are often microservices which are part of, at least, one bigger service. While being connected with the router, these microservices can communicate with each other. The article about WAMP describes the different ways of communicating via this protocol. It is not relevant in which programming language the clients are being implemented, Autobahn|Java is the library of Crossbar.io to implement a client for a WAMP network specifically in Java. It is based on the framework Netty, which is used for asynchronous programming.

Fiction2Science: WAMP and Microservices

Fri, 05 Oct 2018 13:35:49 +0000

Last weekend, I attended the hackathon Fiction2Science of Continental. I was assigned to the Cloud Challenge where we dealt with the communication between microservices in the cloud.

The Cloud Challenge

After the official welcome, we gathered at our challenge areas with around 20 people participating in each challenge (total of 7 different challenges). Each participant indicated what his focus area is (frontend, backend or design). Based on this indication, we autonomously formed teams of four to five participants. Eventually, our team consisted of only three participants: one person focusing on design and frontend development, one developer who engaged in both frontend and backend development and me. In the beginning, I dealt mainly with backend development but eventually, I was also responsible for the presentation. At first, we learned the technique how our developed microservices would communicate. To help with this, we had a simple tutorial with some tasks that we had to solve. Then, we tried to understand how to use our programming language to publish and subscribe to topics and how to register remote procedures and call them. We continued to solve tasks to understand these required techniques a little bit more. Having learnt these techniques, we then developed our own service by combining several microservices. Finally, we had to present our own service in front of a panel consisting of professional Software Engineers and Innovation Managers.