Legacy system integration

While there are many challenges young companies might struggle with, they certainly escaped one that is a blessing and a curse at the same time – the legacy IT systems. Data is indeed one of the companies’ most valued assets, as knowledge (read, ‘data’) empowers better, more informed business decisions. Moreover, chances are your organization already has most of the knowledge …

SaaStr Annual Braindates

Let me start by introducing myself properly: I’m Renat Zubairov, CEO and Co-Founder of a Germany-based company elastic.io, part-time techie, part-time sales, full-time father of three. And I will be hosting a topic at the SaaStr Annual Braindates 2020. While working at our previous companies, Igor, Rico (the other elastic.io co-founders) and I realized how much of a challenge the …

SaaS trend

With $billions invested in digital transformation over recent years, it is little surprise that IDC’s 2020 forecast predicts a continued commitment to the digital enterprise. Moreover, it’s even had a fresh new look for 2020 as the ‘digital-first’ enterprise. What is interesting is the estimation that over the next five years over 90 percent of new apps will be cloud-native, …

basics of data integration

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 …

banking fintech trends

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 …

integration best practices

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.  …

data 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 …

Saas subscription business model with a twist

Before the arrival of the SaaS subscription business model, enterprise ISVs could focus on doing what they do best – developing great software to solve a business challenge faced by their target market. The download CD (remember those?!) had a purchase price. Then periodic updates followed until the product was deemed obsolete. It was a straightforward, one-size fits all model …

Data Integration Best Practices – Integration Projects Costs

While defining a data integration project we should consider what, when and how we want to integrate. Once we have done this, we can move on with the last step of the plan: the costs. The billion-dollar question… how deep should we dig into our pockets?   If we want to have a realistic idea of the cost of our integration …

data integration best practices - data synchronisation vs. other types of integration

In the current chapter of our blog series on data integration best practices, we have already talked about different communication types for data integration – synchronous vs. asynchronous. We have also talked about the main difference between the types of systems that move data – direct data synchronization vs. an integration layer. In this installment of the series, we would …