Programming

Jonas Bonér, CTO of LightBend and creator Akka, discusses using Akka when developing distributed systems. He talks about the Actor Model, and how every Microservice needs to be viewed as a system to be successful. 

Why listen to this podcast:

 - Akka is JVM-based framework design for developing distributed systems leveraging the Actor Model - an approach for writing concurrent systems that treat actors as universal primitives and the most successful model with abstraction has been streaming
 - Circuit breakers in Akka are a backup and retry policy; they protect you by capturing failure data and allow you to roll back 
 - Every Microservice needs to be viewed as a system, it needs to have multiple parts that run on different machines in order to function and be fully resilient - thus is a Microsystem
 - Two different trends have emerged when it comes to hardware and environments: one is the trend toward Multi-core, the is a movement toward virtualized environments and the cloud
 - Saga pattern of managing long running transactions in a distributed system fits very well with messaging style architectures

Notes and links can be found on: http://bit.ly/2kwB2eB

Akka
The Actor Model
When Akka and the Actor Model is the perfect choice
Circuit breakers patterns in distributed systems
Two trends toward Multi-core
Reactive Manifesto
Event Driven vs. Message Driven
Reactive Programming and Streams
Microliths to Microsystems
What do you have to get right before you start trying to deploy a distributed systems?
Working with ML / AI at Lightbend to understand tracing through distributed system
Saga Pattern

More on this:
Quick scan our curated show notes on InfoQ http://bit.ly/2kwB2eB

You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq

InfoQ Podcast

Show Notes

Jonas Bonér on the Actor Model, Akka, Reactive Programming, Microservices and Distributed Systems

In this episode of the O’Reilly Programming Podcast, I talk with Matt Stine, global CTO of architecture at Pivotal. He is the presenter of the O’Reilly live online training course "Cloud-Native Architecture Patterns," and he has spoken about cloud-native architecture at the recent O’Reilly Software Architecture Conference and O’Reilly Security Conference.

Matt Stine on Cloud-Native Architecture

This week’s podcast features a chat with Vitor Olivier. Vitor is a partner at NuBank (a technology-centric bank in Brazil). This podcast hits on topics from several of Nubank’s recent QCon talks and includes things like: Nubank’s stack, functional programming, event sourcing, defining service boundaries, recommendations on reasoning about services, tips (or tweaks) on the second iteration of their initial architecture and more.

Why listen to this podcast:

- Property-based testing and Schemas (or Clojure.Spec)are complementary.
- Clojure’s functional nature and Datomic’s features are a match for Nubank’s requirements.
 - A (micro)service needs to be able to create the full representation of the core feature it’s handling.
 - GraphQL is useful to abstract away the distributed system complexity from the mobile (or frontend) developers.
 - Nubank’s uses a combination of monitoring and sanity checks in real time at various level to keep systems consistent. 
- Once an invariant is broken, the system will try to fix it automatically.

More on this: Quick scan our curated show notes on InfoQ http://bit.ly/2mnqyfK

You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq

Subscribe: www.youtube.com/infoq
Like InfoQ on Facebook: bit.ly/2jmlyG8
Follow on Twitter: twitter.com/InfoQ
Follow on LinkedIn: www.linkedin.com/company/infoq
Check the landing page on InfoQ: http://bit.ly/2mnqyfK

Architecting a Modern Financial Institution with Vitor Olivier, Thoughts on Immutability, CI/CD, FP

On this week’s podcast, Wes Reisz talks with Chris Swan. Chris is the CTO for the global delivery organisation at DXC Technology. Chris is well versed in DevOps, Infrastructure, Culture, and what it means to put all these together. Today’s topics include both DevOps and NoOps, and what Chris calls LessOps, what Operations means in a world of Serverless, where he sees Configuration Management, Provisioning, Monitoring and Logging heading. The podcast then wraps talking about where he sees validating code in a serverless deployment, such as canaries and blue-green deployments.

Why listen to this podcast:

* Serverless still requires  ops - even if the ops aren’t focused on the technology
* Even with minimal functions, the amount of configuration may exceed it by a factor of three
* Disruptive services often move the decimal point
* ML is the ability to make the inferences and AI is the ability to make decisions based on those inferences

More on this: Quick scan our curated show notes on InfoQ http://bit.ly/2Bff4jU

You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq

Subscribe: www.youtube.com/infoq
Like InfoQ on Facebook: bit.ly/2jmlyG8
Follow on Twitter: twitter.com/InfoQ
Follow on LinkedIn: www.linkedin.com/company/infoq
Check the landing page on InfoQ: http://bit.ly/2Bff4jU

Chris Swan on DevOps and NoOps, plus Operations and Code Validation in a Serverless Environment

Software engineers, architects and team leads have found inspiration to drive change and innovation in their team by listening to the weekly InfoQ Podcast. They have received essential information that helped them validate their software development map. We have achieved that by interviewing some of the top CTOs, engineers and technology directors from companies like Uber, Netflix and more. Over 1,200,000 downloads in the last 3 years.

Chris Swan on DevOps and NoOps, plus Operations and Code Validation in a Serverless Environment

InfoQ

Related tracks