[spencer-p]

This article could use a disambiguation. Distributed systems are systems "whose components are located on different networked computers, which communicate and coordinate their actions by passing messages to one another"[0].

This article appears to be focused on running many components on a single computer under the same process tree. Perhaps a better title would be "No more DSLs: Implement and deploy microservices as a monolith".

[0] https://en.wikipedia.org/wiki/Distributed_computing

[catern]

No, this is distributed; see this line in the introduction:

>Functionality for distributed execution and monitoring is shared through libraries rather than by delegating to external orchestration systems, making a single-program system completely self-contained.

and this section in the examples: http://catern.com/caternetes.html#thread

[spencer-p]

The quote you pulled out mentions "distributed execution" being completely contained in a "single-program system" - isn't a single-program system, by definition, not a distributed system?

With the emphasis on distributed systems, I was waiting to see how the approach would help synchronization, replication, network dependencies, etc. But all the examples show calling other services as functions or spawning new processes. At the end orderd starts listening for requests, but I don't see any example in the article where the example program talks to another computer in the system. Perhaps I am missing something?

[pmontra]

That section is about threads. This is not a distributed system (running on different machines), it's a concurrent system (running in one machine.)

Anyway there is overlap between the two terms so strictly speaking the author is not wrong. But is anything with threads a distributed system? If so I built many of them, even with Python .

https://en.wikipedia.org/wiki/Concurrency_(computer_science)

https://en.wikipedia.org/wiki/Distributed_computing