How to master remote and asynchronous work environment?
How to master remote and asynchronous work environment?
Ce site Web utilise des cookies pour vous garantir la meilleure expérience. Memo Bank et nos partenaires sélectionnés utilisent des cookies et des technologies similaires (ensemble, les « cookies ») qui sont nécessaires pour vous présenter ce site Web, et pour vous garantir la meilleure expérience. Si vous y consentez, nous utiliserons également des cookies à des fins de statistiques. Consultez no
In this post we will explore how we can use some of Elixir’s more interesting features to implement event sourcing. OTP is the star of this show, enabling us to do some very nice tricks that would be practically impossible with Ruby. OTP stands for Open Telecom Platform, and is Erlang’s answer to the problem of concurrency. OTP relies on immutability of data to provide some very nice abstractions
Background I’ve been interested in Command Query Responsibility Segregation and event sourcing since hearing Greg Young talk on the subject in early 2010. During the past seven years I’ve built an open-source Ruby CQRS library (rcqrs); worked professionally on .NET applications following the pattern; and more recently built an Event Store (eventstore) and CQRS library (commanded) in Elixir. Buildi
Wherein I describe how easy it was to implement the CQRS pattern in Elixir. I am currently implementing a REST API for a California startup (it’s all very hush hush). Since I could pick my own tools, I gleefully chose Elixir and the Phoenix Framework. Note: Elixir can be thought of as a Ruby-ish dialect of Erlang, plus really great meta-programming capabilities The REST API I am responsible for is
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く