P2P Integration Pitfalls to Avoid in the Cloud

Ross Mason

@rossmason, @mulejockey

About Me

1. Build versus Buy

2. Quick fire Integration

3. Embedding integration in your application

4. Creating dependencies between applications

5. Taking the Happy Path

6. It worked yesterday

7. Using independent consultants

8. Creating single points of failure

9. No visibility or Control

10. Creating a Monster

Avoiding the Pitfalls

Integration PaaS

Summary

1. Buy don’t build2. Use a platform3. Separate integration layer4. Loose Coupling is good5. Avoid the happy path, build for failure6. Need Integration you can test7. take ownership or work with a vendor8. Use a platform that scales9. You need to be able to see what’s going on10. P2P integration always turns into a monster

Questions?

• iON free account : http://mulesoft.com/ion

• Twitter: @rossmason, @mulejockey

• Blog: http://blogs.mulesoft.org

• Company: http://mulesoft.com (we’re hiring)