{"action":"created","issue":{"url":"https://api.github.com/repos/Mashape/kong/issues/1787","repository_url":"https://api.github.com/repos/Mashape/kong","labels_url":"https://api.github.com/repos/Mashape/kong/issues/1787/labels{/name}","comments_url":"https://api.github.com/repos/Mashape/kong/issues/1787/comments","events_url":"https://api.github.com/repos/Mashape/kong/issues/1787/events","html_url":"https://github.com/Mashape/kong/issues/1787","id":186699130,"number":1787,"title":"Any plugin could do EIP(enterprise integration patterns) easier?","user":{"login":"kala888","id":1215976,"avatar_url":"https://avatars.githubusercontent.com/u/1215976?v=3","gravatar_id":"","url":"https://api.github.com/users/kala888","html_url":"https://github.com/kala888","followers_url":"https://api.github.com/users/kala888/followers","following_url":"https://api.github.com/users/kala888/following{/other_user}","gists_url":"https://api.github.com/users/kala888/gists{/gist_id}","starred_url":"https://api.github.com/users/kala888/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kala888/subscriptions","organizations_url":"https://api.github.com/users/kala888/orgs","repos_url":"https://api.github.com/users/kala888/repos","events_url":"https://api.github.com/users/kala888/events{/privacy}","received_events_url":"https://api.github.com/users/kala888/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2016-11-02T02:46:01Z","updated_at":"2016-11-02T09:14:16Z","closed_at":null,"body":"### Summary\r\n\r\nI consider a API tools with a lightweight ESB. Kong is so awesome, easy to use and less dependents. But i still need a lightweight tools to do  route(EIP,  like what Apache Camel do). Here is a case\r\n\r\n### Steps To Reproduce\r\n\r\n1. Kong receive a request\r\n2. Route the request to App1 and at the same time copy the request send to App2.\r\n3. Send the App1 repsonse to client\r\n\r\n### Additional Details & Logs\r\n\r\n- Kong version (`$ kong version`)\r\n- Kong debug-level startup logs (`$ kong start --vv`)\r\n- Kong error logs (`<KONG_PREFIX>/logs/error.log`)\r\n- Kong configuration (registered APIs/Plugins & configuration file)\r\n- Operating System\r\n"},"comment":{"url":"https://api.github.com/repos/Mashape/kong/issues/comments/257810493","html_url":"https://github.com/Mashape/kong/issues/1787#issuecomment-257810493","issue_url":"https://api.github.com/repos/Mashape/kong/issues/1787","id":257810493,"user":{"login":"DonMartin76","id":7326883,"avatar_url":"https://avatars.githubusercontent.com/u/7326883?v=3","gravatar_id":"","url":"https://api.github.com/users/DonMartin76","html_url":"https://github.com/DonMartin76","followers_url":"https://api.github.com/users/DonMartin76/followers","following_url":"https://api.github.com/users/DonMartin76/following{/other_user}","gists_url":"https://api.github.com/users/DonMartin76/gists{/gist_id}","starred_url":"https://api.github.com/users/DonMartin76/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/DonMartin76/subscriptions","organizations_url":"https://api.github.com/users/DonMartin76/orgs","repos_url":"https://api.github.com/users/DonMartin76/repos","events_url":"https://api.github.com/users/DonMartin76/events{/privacy}","received_events_url":"https://api.github.com/users/DonMartin76/received_events","type":"User","site_admin":false},"created_at":"2016-11-02T09:14:16Z","updated_at":"2016-11-02T09:14:16Z","body":"You already mention Apache Camel as a potent EIP library. Why would you want to couple that functionality with Kong? I do understand why it would look like a good idea (leveraging Kong as a base for an ESB), but from an architectural point of view I would highly recommend leaving it uncoupled, and treat your EIP implementation as a service end point (API) served by Kong, and not mash them together.\r\n\r\nGetting the EIP functionality into Kong will eventually bloat Kong in such a way that it is no longer lean, fast and awesome.\r\n\r\nI would go for things like Camel in Docker behind Kong; combine that with a dedicated queuing system like Rabbit MQ, and you have your building blocks ready. Doing configuration based EIP implementing is seldom fun for all but the most basic use cases."}}
{"actor":{"display_login":"DonMartin76"}}