Having worked almost all my career (so far) within enterprise application integration, could not help but to think about how various apps running within AWS could be integrated. One straight forward approach is to run the middleware solution within cloud such as Oracle SOA Fusion Middleware.
However, from the data integration point of view, IMO, AWS has already a solution in place ("loosely" speaking) in the form of AWS Lambda. So far with the support of Node.js and more specifically Java, it already "qualifies" for an integration tool. So far we know that Lambda can at least integrate the following (And this is far from complete):
1. S3: You put an object to a bucket and trigger Lambda function which can read the object and can work on the information within.
2. Dynamo DB: You can create stream on any table and trigger a lambda function.
3. SNS Notification: As an "Email" integrator.
4. API Gateway: Wrap your function as an HTTP service.
5. Scheduled trigger: Compared to an "Inbound Activation Spec" similar to a typical JCA inbound adapter.
And various others: Cloud Trail, Android, Custom App, VPC and continuing... Business logic in terms of routing and transformation will of course be custom and as part of Lambda will be highly scalable (Assuming written as such)
Best part of Lamda is its cost model, based on the number of requests. On top, you will not have a (usually) heavy weight app server or even any "server box", no OS level maintenance - No "Ops"!
Very eager to know how this Lambda evolve and gets adopted by enterprises.
No comments:
Post a Comment