On The Architectures Of Microservices – the Next Layer
Please log in to watch this conference skillscast.
In many talks over the years Russel has been presenting "dataflow" and to a lesser extent "actors" as architectures for systems. At last year's μCon Russel gave a presentation on this sort of thing. His proposal for this year is for a continuation of some of the ideas in that talk. Not a rehash, definitely an extension and expansion of the ideas. In particular it is clear that microservices instances are effectively actors, but can it be "actors all the way down". Clearly not because at some point we have to work with real hardware which is very, very rarely an actor system.
Microservices can be implemented in many languages Go, Python, D, Kotlin, Ceylon, C++, Java,… does the choice of programming language have a critical effect on the achitectures of microservices.
The session is about scaling of architectures and at what point there have to be "fault lines" to other architectures and whether this turns out to be seamless or the location of real problems..
YOU MAY ALSO LIKE:
Thanks to our sponsors
On The Architectures Of Microservices – the Next Layer
Russel Winder
Russel is an ex-theoretical physicist, ex-UNIX system programmer, ex-academic, ex-independent consultant, ex-analyst, ex-author, ex-expert witness and ex-trainer. Russel is still interested in programming and programming languages, and all things parallel and concurrent. And build. He's actively involved with GPars, Me TV, and various bits and pieces of SDR. Russel likes working with Python, Ceylon, Kotlin, D, Go, Rust, and C++17.
-
SkillsCast
Please log in to watch this conference skillscast.
In many talks over the years Russel has been presenting "dataflow" and to a lesser extent "actors" as architectures for systems. At last year's μCon Russel gave a presentation on this sort of thing. His proposal for this year is for a continuation of some of the ideas in that talk. Not a rehash, definitely an extension and expansion of the ideas. In particular it is clear that microservices instances are effectively actors, but can it be "actors all the way down". Clearly not because at some point we have to work with real hardware which is very, very rarely an actor system.
Microservices can be implemented in many languages Go, Python, D, Kotlin, Ceylon, C++, Java,… does the choice of programming language have a critical effect on the achitectures of microservices.
The session is about scaling of architectures and at what point there have to be "fault lines" to other architectures and whether this turns out to be seamless or the location of real problems..
YOU MAY ALSO LIKE:
Thanks to our sponsors
-
About the Speaker
On The Architectures Of Microservices – the Next Layer
Russel Winder
Russel is an ex-theoretical physicist, ex-UNIX system programmer, ex-academic, ex-independent consultant, ex-analyst, ex-author, ex-expert witness and ex-trainer. Russel is still interested in programming and programming languages, and all things parallel and concurrent. And build. He's actively involved with GPars, Me TV, and various bits and pieces of SDR. Russel likes working with Python, Ceylon, Kotlin, D, Go, Rust, and C++17.