{"action":"opened","issue":{"url":"https://api.github.com/repos/martinfowler-cn/trans-tasks/issues/105","repository_url":"https://api.github.com/repos/martinfowler-cn/trans-tasks","labels_url":"https://api.github.com/repos/martinfowler-cn/trans-tasks/issues/105/labels{/name}","comments_url":"https://api.github.com/repos/martinfowler-cn/trans-tasks/issues/105/comments","events_url":"https://api.github.com/repos/martinfowler-cn/trans-tasks/issues/105/events","html_url":"https://github.com/martinfowler-cn/trans-tasks/issues/105","id":387533107,"node_id":"MDU6SXNzdWUzODc1MzMxMDc=","number":105,"title":"The LMAX Architecture","user":{"login":"TARS-robot","id":45490639,"node_id":"MDQ6VXNlcjQ1NDkwNjM5","avatar_url":"https://avatars1.githubusercontent.com/u/45490639?v=4","gravatar_id":"","url":"https://api.github.com/users/TARS-robot","html_url":"https://github.com/TARS-robot","followers_url":"https://api.github.com/users/TARS-robot/followers","following_url":"https://api.github.com/users/TARS-robot/following{/other_user}","gists_url":"https://api.github.com/users/TARS-robot/gists{/gist_id}","starred_url":"https://api.github.com/users/TARS-robot/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/TARS-robot/subscriptions","organizations_url":"https://api.github.com/users/TARS-robot/orgs","repos_url":"https://api.github.com/users/TARS-robot/repos","events_url":"https://api.github.com/users/TARS-robot/events{/privacy}","received_events_url":"https://api.github.com/users/TARS-robot/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-12-04T23:58:58Z","updated_at":"2018-12-04T23:58:58Z","closed_at":null,"author_association":"COLLABORATOR","body":"https://martinfowler.com/articles/lmax.html\nThe LMAX Architecture\n\n12 July 2011\nLMAX is a new retail financial trading platform. As a result\nit has to process many trades with low latency. The system is built on\nthe JVM platform and centers on a Business Logic Processor that can handle 6 million\norders per second on a single thread. The Business Logic Processor\nruns entirely in-memory using event sourcing. The Business Logic\nProcessor is surrounded by Disruptors - a concurrency\ncomponent that implements a network of queues that operate without\nneeding locks. During the design process the team concluded that\nrecent directions in high-performance concurrency models using queues are\nfundamentally at odds with modern CPU design."}}
{"actor":{"display_login":"TARS-robot"}}