heathermiller / dist-prog-book Goto Github PK

The content should probably come close to filling the viewport at this width without so much whitespace on the sides. Also something odd is going on with the menu, title, etc.

What about using https://www.gitbook.com/ ?

The tool to build the book itself is free and open source ( https://github.com/GitbookIO/gitbook ), you can preserve the Markdown syntax, you can integrate it through Travis CI and finally you have a very nice output you can already use as WIP meanwhile you work on it ( by pushing it on gh-pages )

I've attended the strangeloop talk and read the text in this repo, and I find it sad that O'Hare's work on CSP and Milner's pi-calculus are barely mentioned.

Maybe you can choose to keep them out of scope, but I think it would still be important to remind the reader in chapter 4 that Argus' "guardians" are just a custom name for the concept of monitor, invented by O'Hare in 1974, widely used by that time already, and subsequently used with that name in Java and most other concurrent and distributed languages/frameworks afterwards.

Check the latest docs http://www.grpc.io/docs/
gRPC is pretty comprehensive now, supports a lot many languages at par with Thirft.

Section 3. The CAP Theorem.
This image link, essential to the presentation, gets a 404.

Chapter 1:
"able to communication information successfully"
"the complexity of the of this remote procedure has no upper bound."
"Aggregating multiple Filters is alos possible in Finagle."
"is a modified implementation to of the RPC paradigm"
"it’s become very difficult differentiate"

Is the RPC example in Python3, supposed to fail? It's being called without arguments.

Thanks for writing this book. I find it immensely helpful (I'm not done reading it yet though).

What do you think about?
https://github.com/envoyproxy/envoy

We can think of distributed computation as being applied quite differently in typical enterprise applications vs in distributed data analytics and machine learning.

In the former, the boundary is decided by architects and the decision is (arguably) quite removed from the business logic itself.

In the latter, the "business logic" is the algorithm itself and together with the nature and size of big data are (arguably) the main drivers for the distribution decisions.

Given the two are quite distinct and given that traditionally when talking "distributed computing" people think mostly "actors" and "microservices", I suggest we include the latter in the scope of this book.

Great project, I am really looking for the results!

Have you considered a license to use this as open educational resources (or under a Creative Commons license) yet?

There are code blocks all over the place that specify a language like:

```Java
```

But nothing actually gets highlighted based on those specified languages in the final produced book.

Thanks for writing this book. I find it immensely helpful (I'm not done reading it yet though).

What do you think about?
https://github.com/envoyproxy/envoy

hi, heathermiller

I would like to transfer this book into chinese if can got your approvement