GreenVulcano 4, the latest evolution of our enterprise service bus designed to go beyond the traditional approach on SOA architecture by innovatively interpreting the (EAI ) enterprise application integration to meet today’s requirements for high flexibility but with the robustness and reliability of the systems traditional.

  1. Speed, in all phases of the life cycle, from development to provisioning up to operations, to respond in the best possible way to the changing needs of the market;
  2. Economics, limiting infrastructure costs, thanks to the possibility of being used both on the on-demand cloud and on commodity hardware, thus also reducing the considerable software license costs;
  3. Flexibility, modularity and polymorphism, which guarantee the ability to cover needs that are not yet born and we can not foresee, changing its own structure without design from scratch.

 

Enterprise service bus | what’s this

Intrinsically, the enterprise service bus is a mechanism in which a bidirectional interface from connected systems is always provided. This means that all source and destination systems must be connected to the ESB and that the applications themselves communicate by sending messages on the bus.

An enterprise service bus is, therefore, a bus on which messages between integrated entities travel.

However, one should not think of the BUS as a mere intermediary structure, since it is possible to modify the messages by intervening in the logic of the software.

 

ESB GreenVulcano: a use case

To better understand the strength of an ESB, let’s analyze its implementation.

Suppose we have a business model according to which, a series of stores that operate on behalf of the shop, are periodically supplied from a single warehouse, all respecting the following logic:

  1. When the goods arrive at each store, the ERP system must be updated
  2. The cashier who sells the single item of clothing sends information to the ERP system via the App. The status of the garment is updated to “sold”.
  3. The cashier or Sales manager sends via the App the eventual return of the garment that a customer has returned to him, for the issue of a Credit Note
  4. A night batch issues an invoice for each store on daily sales
  5. The payment system sends the request for SDD (Sepa Direct Debit) to Banca Sella. Invoice in “paid” status. Once the payment has been received by the Bank, the invoice is set as “paid”.

As you can see there are several systems and components that cooperate with each other in a reality that we can define as integration platform: the ERP system, the web services displayed by the bank, the application that updates the ERP system for each sale of a garment, the insertion of data that takes place through the NFC reading of the various items, can in fact use protocols and different programming languages.

The enterprise service bus connects the various applications with which it interfaces.

If every service were to have a communication interface for every other service, how many interfaces should we create?

Here, therefore, that each system should have a single interface to the ESB, as can be seen in the figure below.

 

Scalability of an ESB

Imagine the example illustrated above, in a context without ESB: if each component must be able to interact with all the other components, no more than 16 interfaces would be needed, but 56!

Any change to a component could result in the modification of all the interfaces of those components with which it interacts: you can imagine the time that each update needs.

The use of an ESB is therefore the winning choice, as we can well understand how such an architecture can be scaled in terms of components, allowing a very large number.

 

 

 

Enterprise service bus architecture

The SOA (service-oriented architecture) used by Greenvulcano, as the acronym suggests itself, is a service-based architecture: in fact, we have the requests for services, and on another level, we have the actual services called up and connected by means of a BUS. The OSGI specifications implemented in Greenvulcano therefore allow the development of a component platform. These components or applications, available as bundles for distribution, can be installed, started, stopped, updated and uninstalled remotely without requiring the restart of the ESB that is deployed on the Karaf container.

The services or components within Greenvulcano, can be either strongly decoupled, think about the case in which a feature can be associated with a single service, or we can have a workflow of services (that is, multiple services performed sequentially). The enterprise service bus integrates and orchestrates all this.

Enterprise service bus | characteristics

The main features of Greenvulcano will be described below

  • Running on the Karaf container for greater lightness: this also allows you to load new configurations and hot features without having to reload and deploy the application in full.
  • Integration between different applications with different technologies such as JMS, Web Services, JDBC, HTTP and more
  • A visual development environment (developer studio): this allows you to develop some services in a simple and intuitive way or a workflow of several concatenated services. See our tutorial and find out how easy it is to create an event-driven push notification.
  • A monitoring dashboard that allows you to deploy services
  • High reliability, security and scalability
  • Use of Java 8 and OSGI 6.

 

“A control system … would have allowed us to immediately understand the conditions of structures subject to possible catastrophes, and today would have allowed us to prevent many of the disasters that have occurred in recent times”.

 

These are the words of the engineer. Paolo Persi del Marmo CEO of NTSG, a partner company of GreenVulcano.

 

The solution referred to, based on OF (acronym of optical fibers), comes precisely from the need to verify the health status of a structure during its life, a system patented by NTSG to monitor the 3D and 2D deformations of an element of generic shape, using optical fibers as a means of measurement, a system that finds its greatest application in the control of major works (bridges, tunnels, roads, railways, dams) and buildings: a very topical aspect given the recent tragic events that hit Italy.

 

The data, once acquired, passes to the IoT platform of GreenVulcano, where they are analyzed to draw up reports and statistics, and to artificial intelligence that uses them to make predictive maintenance and prevent possible future structural damage.

 

Most likely you will have already heard about the term Internet of Things.

 

Although on the internet there are excellent descriptions if you have any curiosity about the topic we suggest you start reading some of the posts of our blog and then deepen the topics that interest you the most:

 

 

But what is an IoT platform and what are its characteristics? In this series of articles, we will try to give a more complete answer by explaining the growing need for every company that intends to start IoT projects and how the company GreenVulcano Technologies, with its solid technical background, can help companies to face the many challenging aspects of the IoT revolution.

 

2 – An “IoT data storm” is coming. Get ready

 

After the initial IoT hype and the disillusionment phase, we arrived at the beginning of the widespread adoption of technology and productivity. Customers recognize the IoT as a fundamental element for digital transformation and are ready to take the right steps to be part of it.

 

Sensors and actuators of all kinds are added to the Internet at unimaginable speed and the IoT market will continue to be one of the best exponentially growing markets in the coming years.

 

Customers will always pay more attention to the estimate and the results of every investment in this field.

 

The amount of data that “objects” generate and download on the Internet every day has never been addressed before and will need new technologies and new paradigms to be able to collect, store, process and analyze the IoT data flow.

 

But how much data are we talking about when we say “data storm”?

 

Just to give an example on a real monitoring scenario, we show you that of a tunnel, for the control of convergence and longitudinal deformations, when it is located on land subject to landslides.

Here are some photos that show one of the fundamental activities of IoT, that is to enable objects to “speak” to communicate information. This is the tunnel walls along their entire length:

Monitoring of a gallery:

  • Number of sensors: 780
  • Sampling frequency: 10 Hz
  • Wiring: 30 km of an optical fiber (Val di Sambro tunnel)
  • Package size: 6 bytes (each sensor) + 30 bytes of header
  • Hours of operation: 24/24 hours, 365 days/year

 

it follows:

 

  • 780 sensors * 10 Hz * 10 bytes * 60 seconds * 60 minutes * 24 hours
    • ~ 46 Kb per second
    • 161.7 MB per hour
    • 3.78 GB per day
    • 10 messages (~ 4.6 kb each message) per second

 

This is a simple scenario, but there are monitoring situations that require sampling frequencies at 1000 Hz, which may then require the transfer of 1000 measurements per second on the internet.

 

For a general idea, let’s consider this table, which shows the ranges of data related to a group of sensors of a hypothetical IoT project:

 

Amount of data of a hypothetical IoT project # of bytes to digest over the internet
Small < 100 MB per day
Medium < 1-10 GB per day
High < 50-500 GB per day
Huge > 500 GB > 1 TB > 100 TB > …?

 

This table is today quite realistic when it classifies traffic as small, medium, high and huge, and given that in the near future the numbers are destined to increase exponentially, the effect that will have is that the longevity of IoT solutions will be shorter and shorter. , therefore (again) it is important to adopt open, modular and scalable solutions and, above all, a correct methodological approach that can take account of this growth if we want to be able to exploit this revolution to the fullest.

Here at GreenVulcano, we are well aware of it has already had too many times to intervene in solutions and configurations that were not adequate and that required the design of the system starting from scratch. These situations have as a direct consequence the facing of further expenditure, with the main damage of keeping inoperative or operating only in one part, the structure on which it was already spent.

3- Conclusions

The IoT solutions will be increasingly used this because they transmit important knowledge to help digital transformation and are proving a basic element in every sector and market division. The cloud, the analysis and the IoT will extraordinarily improve the companies controlled by technology and will give greater productivity, safety, intelligence and profitability to the company. Unfortunately, most IT associations have almost no knowledge or training on operational structures such as monitoring and data acquisition supervision systems (SCADA).

So if you are serious about starting an IoT project for your organization, choosing an appropriate IoT platform and choosing an experienced service provider are extremely important and sensitive.

This is only the first step because then we need to move on to an analysis of new features that will be basic in the coming years such as:

  • artificial intelligence
  • edge computing
  • etc..

Things we will discover and deepen better in the next article.

Introduction

The connected vehicle field is a microcosm of the IoT.  By using the potential of smart devices and of IoT connectivity, a connected vehicle not only can determine things such speed, location and temperature, but it also may interact with surrounding roads, buildings and other vehicles to provide near real-time information, improve safety and avoid traffic.

Consumer expectations have been deeply changed by the diffusion of smartphones and tablets. People now ask for uninterrupted connectivity and customizations, and the car it’s the natural habitat for this kind of requests and user experience.

Read more

The continuous evolution of software technologies has led to a complex situation in which traditional legacy systems have to coexist with web applications, new generation of mobile apps and, recently, Internet of Things infrastructure and cloud services. Read more