Integration Processes

for Serverless Hybrid Cloud

María Arias de Reyna

@delawen

Senior Software Engineer at

About me

19🐱🐱 Crazy Cat Lady
Free and Open Source Advocate
2008 Computer Science Graduate (Software Engineer)
2009 Dijkstra A* Witch
2012 Metadata Wrangler
2013 OSGeo Charter Member
2017-2019 OSGeo President
2016 Women in Tech
Senior Software Engineer at
2019 Integration Druid
2020 Apache Software Foundation

Integration Processes

for Serverless

Hybrid Cloud

What do you mean by "Integration Processes"?

When you need components to interact

Create (work)flows and automations

What do you mean by "Hybrid Cloud"?

When you have mixed components

different providers, different languages, different paradigms,...

A cloud is an internet-based computing in which most of your computing capacity is remote. That cloud allows the sharing of data-processing tasks, centralized data storage, and online access to computer services or resources. It can be very useful for "as a Service" features like Software as a Service (SaaS), Platform as a Service (PaaS), Function as a Service (FaaS),... which provides of "on-demand" functionality that enables the supporting infrastructure to be powered down and not incurring charges when not in use.

An Hybrid Cloud is a cloud that has a variety of providers, services, paradigms,... Some of those components can be free and open source as opposed to others having a restricting license. Being able to make such different components interact with each other is usually a complex task, specially when each of them "speaks" a different language, protocol and/or format.

What do you mean by "Serverless"

Integration Processes

for Serverless

Hybrid Cloud

"Glue"/Middleware

Integration Frameworks, can help us orchestrate and automate the interaction between different applications, APIs, third party services or any other software piece we may have to connect.

A proper integration tool should provide us with the following features: transformation, integration patterns and connectors to existing protocols and components.

Let's start with transformations. When we connect different components of an architecture, they rarely speak the same languages or, on this case, data formats. Some components will output an xml that has to be fed to the following component on a json form. Maybe we even need to add or remove some attributes on that json data. An integration framework allows us to define what is the mapping between the output of one component and the input of the following so we can forget about the explicit implementation. The less code we have to maintain, the better.

Now, being able to transform data on each step is not enough if we can’t connect to (and from) the specific component we need. Our ideal integration framework should offer support for common protocols like ftp, http, jdbc,… Also it should offer support to connect to common components like a mail server, messaging services, atom,… We could claim even that no integration tool would be good if it doesn’t also support specific well known services like being able to send a message through a Telegram bot or store information on Elastic Search. Being able to seamlessly connect from one component to the next without having to worry about the specifics of their interfaces is what distinguishes an average integration tool from a good integration tool.

And finally, not all flows will be lineal. Some of the steps will require broadcasting, some of them will require conditional flowing. Some will require waiting the output of different components to conflate the data. These action patterns are something that have been studied for a long time. And as with software development patterns, you can classify them and study them to create better integrations. You can find them as "Enterprise Integration Patterns".

This Camel transformations example can be found online.

Apache Camel

Compared with Lego

Let's see an example

 
              
                  //Run this workflow every second
                  from("timer:java?period=1000")
                    .setBody()
                      .simple("Hello Camel!")
                    .to("log:info");

Questions?

You can find more on

https://camel.apache.org

https://syndesis.io

https://www.redhat.com/en/technologies/jboss-middleware/fuse

This presentation is on

Integration Processes

for Serverless Hybrid Cloud

María Arias de Reyna

@delawen

Senior Software Engineer at .b185c6fe-daea-408b-9fe9-61f9c6069fbe{fill:#e00;}RedHat

About me

Integration Processes

for Serverless

Hybrid Cloud

What do you mean by "Integration Processes"?

What do you mean by "Hybrid Cloud"?

What do you mean by "Serverless"

Integration Processes

for Serverless

Hybrid Cloud

"Glue"/Middleware

Apache Camel

Let's see an example

Questions?

Senior Software Engineer at