How to Avoid Integration Platform Teething Problems
Integration platforms bring numerous benefits to businesses, but in the beginning it can be tough. So is there a way to avoid the problems of start-up?
If you’re like many people, you’ll know the biggest problem with integration platforms is starting out. Typically, you’ll have a lot of configuration, downloads and compiling to do and this can be a real pain, especially when all you want to do is use the patterns that make integration platforms really useful. Ever since base2Services began working on integration platforms back in 2005, I’ve been searching for a way to avoid these issues. So is it possible?
The answer is yes, but it has taken me a long time (and plenty of wrong turns and dead ends) to find it. At one point I even considered building a SaaS based integration platform with Apache Camel. If done right, it would make event style messaging a breeze, but in the end, I’m glad I didn’t spend any time doing this. I did approve the build of Kagura, with the aim of removing the mess that reporting tools create - things like bloating, running slow and only having a singular way of doing things – but more on Kagura another time.
I was excited when Amazon Web Services released SNS and SQS, but unfortunately they really only solved one part of the integration problem - the message itself. On the other hand, the Beta release of Lambda works like a charm – but the downside is, it doesn’t have a nice project structure to work with and is fairly primitive.
But now, at last, the answer has finally come. With the release of Serverless Framework, the world has really started to change (for Lambda anyway). You can build web, mobile and IoT applications with serverless architectures via AWS Lambda and API Gateway. Although it’s still in Beta modes, it has removed the problems that many encountered when starting out with integration platforms. It’s brilliant work, and is definitely worth checking out.