persei8

6 ms·

1.
by persei8 12y ago
If I could recommend _just_one_ resource from that list, it would be http://www.tigerteam.dk/talks/IDDD-What-SOA-do-you-have-talk...
2.
by persei8 12y ago
amazon.com is pretty traditional web application and they've been doing SOA for ages.
3.
by persei8 12y ago
Service owns it's data. Other services can't access this data directly. Within service, on it's data, you can do as many "joins" as you want.
4.
by persei8 12y ago
Request/Reply pattern makes a poor choice for communication between services - it increases coupling. It doesn't matter much if it comes with HTTP or any other flavour. Again, Jeppe nails it in very detailed post: http:/&#x2
5.
by persei8 12y ago
Transactions spanning several microservices violate their autonomy - one service should not lock resources of another. Jeppe Cramon explains it pretty well in http://www.tigerteam.dk/2014/micro-services-its-not-only-the
6.
by persei8 12y ago
> If the entities in one service are not in strong relationship with one another, it's a sign you can split them in two services. But if two microservices talk to each other so extensively, that the service boundary is becoming a bo
7.
by persei8 13y ago
Is it true that you don't fully buffer body of POST request on router? This limitation works against Unicorn design and makes it hardly a "fix": http://rubyforge.org/pipermail/mongrel-unicorn/2013-April/00...
8.
Rails API - my simple approach(blog.arkency.com)
10 points by persei8 14y ago|0 comments
9.
You don't inject for tests(blog.arkency.com)
19 points by persei8 14y ago|13 comments
10.
by persei8 14y ago
To me framework is a set of libraries, glued together with some infrastructure code. Framework provides some conventions that speed up most common tasks. It may be possible to use framework as a library, though there is no or small benefit.