1,936 karma · joined March 27, 2007
Creator of hntrends.com
https://www.ryanwilliams.dev
https://bsky.app/profile/ryanwilliams.dev https://hachyderm.io/@ryanwi
@ryanwi
https://www.quora.com/session/David-Heinemeier-Hansson/1?sri...
[1] http://www.oregonlive.com/silicon-forest/index.ssf/2016/07/g...
[1] http://www.ryan-williams.net/hacker-news-hiring-trends/2016/...
[1] http://www.ryan-williams.net/hacker-news-hiring-trends/2016/...
[1] http://www.ryan-williams.net/hacker-news-hiring-trends/2016/...
* https://github.com/airbnb/ruby
* https://github.com/thoughtbot/guides/tree/master/style/rails
[1] http://www.programmableweb.com/news/banksimple-banking-servi...
* All RESTful services must be up and running for application to be fully up and running * application must have all knowledge of RESTful services it calls
With messaging (and PubSub), services don't need to be running at all times and you can add as many services you'd like without the application needing to know. Applications just says "hey, something happened" and services go to work.
I agree with you, in either case, it is important to code defensively and be aware of possible request version mismatches. Deployment coordination is probably awash between the 2 approaches. I think testing is more of a challenge with message oriented too, as most integration testing tools are geared towards HTTP interactions.
[1] http://martinfowler.com/articles/microservice-trade-offs.htm...
Are you referring to mashups in that the application is using external APIs? I'd say that's similar with the difference being you don't have to coordinate the deployment part. With mashups you still have the testing challenge and reliance on another system to be running that comes with a microservice architecture.
Compare that to synchronous services where the application has be aware of all of them and coordinate calling them all. It is easier to use synchronous when the application requires an output from the service to respond.
Transactions across services are certainly not easy:
"Distributed transactions are notoriously difficult to implement and and as a consequence microservice architectures emphasize transactionless coordination between services, with explicit recognition that consistency may only be eventual consistency and problems are dealt with by compensating operations." [1]
Ahh, right, car-free commute is a good point.
> Fort Collins was something else that looked pretty interesting, but I didn't see many jobs there.
My reaction to Fort Collins was similar, really liked it too, but seemed more like Bend as far as lack of jobs/backup-plans go. I like smaller cities and I work remotely, so backup plans shouldn't matter as much as it does to me. I'm probably too risk-averse in that sense, as I also had the same fears when looking at a move to Corvallis before. I suppose I'll always need to be near a bigger city to compensate.
I'll be on the lookout for meetups as well.