The Open Integration Hub (OIH), has reached a milestone this week as it concludes the two-year funding commitment from Germany’s Federal Ministry for Economic Affairs and Energy (BMWi). Just to remind you, OIH project was founded in 2017 to create a central open source integration platform offering a uniform and secure standard for automatic data synchronization across various applications.
In 2018, the forecast for the iPaaS market was to grow by an astonishing 42.1% CAGR to reach a global market valuation of US $8.6billion by 2024. A considerably more recent forecast suggested a moderate, yet ‘robustly’ positive CAGR of 11.9% to reach $1.2 billion by 2022. Of all the forecasts for the global integration platform as a service (iPaaS) market, this estimate is probably the most restrained to hit the headlines in a while.
How many times have we wondered whether school lessons will ever be useful in the outside world? I never thought of the importance of trigonometry until I tried to fit a large sofa through a narrow doorway! In a similar way – unless your career path takes you in certain directions – many may question the value of grammar in real life. After all, when text-speak, emoticons and all manner of colloquialisms dominate our daily communications, how important is grammatical correctness?
Recently, I read an article called “For IoT, think about creating a minimum viable ecosystem” on Stacey on IoT blog, which got me thinking about what we ourselves have been observing in the SaaS sector. In particular, the article says: “With the internet of things, companies are no longer trying to create a product to offer value, but rather establish relationships between companies and individuals to create value.
By the September deadline, Europe’s banks and fintech companies should be compliant with the Second Payment Services Directive (PSD2). Rather than focusing inwards on business operations, PSD2 is an outward-looking directive. It encourages open access and competition in the banking industry. Organisations across the breadth of the industry are required to open their payments infrastructures and customer data to third parties.
In the previous article of our last chapter of Data Integration Best Practices, we took a look at how to describe integrations in such a way that everybody – from developers to business users – understands the requirements correctly. We also discussed why you eventually might need some type of an integration layer to keep your integration projects under control. In this article, we continue reviewing some tips that revolve around preparing for and running an integration project.
So far, in our blog series Data Integration Best practices, we have covered the different types of high-level and low-level problems occurring in data integration projects. We have also addressed the different types of integration, the systems that move data and even the pricing aspect of such a project. Ten articles later, we arrived at best practices moving forward. In this last chapter, we are going to talk about some tips that revolve around preparing for and running an integration project.
