Good day, everyone
I have started a new company recently and the strategy behind this is to “make things easier”. In my years with SAG I have seen many companies reinvent the wheel and quite a number of other things that should not require reinventing.
As an example, I have taken the topic of file integration. This enterprise integration pattern describes the path from data stored in files to data stored in caches, databases, repositories, events, messages or just other files. And even though we live in the era of real-time processing, I have found that many, or rather most, organizations still have the requirement to do this and still spend a lot of time and effort on it.
I am in the process of publishing a new framework (GA mid September 2016) that runs on top of IS, that allows me to create file integrations, using files of any type, format or size, within half an hour. Tried and tested with 10 GB files at 400,000 records per minute with a 250MB memory footprint. The framework allows developers to focus just on that small part of the project that is actually unique to their “transformation requirement”. All the commodity functionality such as parsing, transport, synchronization, reporting; it is already there. Build for performance and ease-of-use.
Now, my question to you, what other challenges have you seen in your organization, or within your customers’ organization, that a) are common as muck yet still not a commodity when it comes to implementing, b) should be a commidity to implement, and c) are not provided out of the box by the platform.
My reason for asking, as surely I have one, is to validate my understanding of the challenges that SAG users are facing. I have seen many at the 50+ customers I worked with, but I am quite sure there are more and that some of them are not as difficult to resolve as one may think. The end goal is for customers to be able to literally install the webMethods platform and hit the ground running.
To start the list, I am already working (and publishing in the coming weeks) the following:
A service load testing and performance benchmarking tool that helps understand the impact of running a service under high load;
A policy based Flow code design time analyzer and validator (including CI hooks) that helps ensuring code quality and maintainability, and that highlights performance and technical risks (which is especially helpful when development is outsourced);
Your feedback is very welcome and feature suggestions for any of the above as well.
Many thanks, Chris Schuit