comp.devel

In this episode of the InfoQ podcast Charles Humble talks to Michael Perry about his book “The Art of Immutable Architecture”.  They discuss topics including the eight fallacies of distributed computing: a set of assertions made by L Peter Deutsch and others at Sun Microsystems describing false assumptions that programmers new to distributed applications invariably make. Other topics include Pat Helland’s paper “Immutability Changes Everything”, Eric Brewer's CAP Theorem, eventual consistency, location independent identity, and CRDTs.  They also discuss how the approach to building distributed systems advocated by Perry could be introduced to a real-world enterprise app that needs to integrate with mutable downstream systems.

Read a transcript of this interview: https://bit.ly/3wWMNvp

Subscribe to our newsletters:
- The InfoQ weekly newsletter: bit.ly/24x3IVq
- The Software Architects’ Newsletter [monthly]: www.infoq.com/software-architects-newsletter/

Upcoming Virtual Events - events.infoq.com/

InfoQ Live:
https://live.infoq.com/
- August 17, 2021
- September 21, 2021
- October 19, 2021

QCon Plus:
https://plus.qconferences.com/
- November 1-5, 2021

Follow InfoQ:
- Twitter: twitter.com/InfoQ
- LinkedIn: www.linkedin.com/company/infoq
- Facebook: bit.ly/2jmlyG8
- Instagram: @infoqdotcom
- Youtube: www.youtube.com/infoq

InfoQ Podcast

Transcript

Michael Perry on Immutable Architecture, CAP Theorem, and CRDTs

In this episode of the InfoQ podcast Charles Humble talks to Lucas Cavalcanti, a Principal Engineer at Nubank, which is the leading FinTech in Latin America and has become the most valuable digital bank in the world. They discuss Nubank’s early architectural choices including starting with Clojure and microservices, the challenges of using public cloud for financial services in Brazil, Nubank’s desire for immutable architecture and use of Alistair Cockburn's Hexagonal Architecture, and lessons learnt as the startup scaled.

Read a transcript of this interview: https://bit.ly/3m6wXMQ

Subscribe to our newsletters:
- The InfoQ weekly newsletter: bit.ly/24x3IVq
- The Software Architects’ Newsletter [monthly]: https://www.infoq.com/software-architects-newsletter/

Upcoming Virtual Events - https://events.infoq.com/

InfoQ Live:
https://live.infoq.com/
- September 21, 2021
- October 19, 2021

QCon Plus online conference:
https://plus.qconferences.com/
- November 1-12, 2021

Follow InfoQ:
- Twitter: https://twitter.com/infoq
- LinkedIn: https://www.linkedin.com/company/infoq/
- Facebook: https://www.facebook.com/InfoQdotcom/
- Instagram: @infoqdotcom
- Youtube: https://www.youtube.com/infoq

Lucas Cavalcanti on Using Clojure, Microservices, Hexagonal Architecture and Public Cloud at Nubank

Charles Humble discusses Moldable Development with its creator Tudor Gîrba.  They discuss Gîrba’s key insight—that developers spend more than half their time reading systems rather than writing them—and how this lead to the creation of a novel development approach, Moldable Development, and a corresponding IDE, Glamorous Toolkit, which has the potential to change both how we reason and make decisions about software systems.

Read a transcript of this interview: https://bit.ly/3Gc2Fjd

Subscribe to our newsletters:
- The InfoQ weekly newsletter: www.infoq.com/news/InfoQ-Newsletter/
- The Software Architects’ Newsletter [monthly]: www.infoq.com/software-architects-newsletter/

Upcoming Virtual Events - events.infoq.com/

QCon London:
https://qconlondon.com/
- April 4-6, 2022 / London, UK

QCon Plus: 
https://plus.qconferences.com/
- May 10-20, 2022
- Nov 29 - Dec 9, 2022

QCon San Francisco
https://qconsf.com/
- Oct 24-28, 2022

InfoQ Live:
https://live.infoq.com/
- Feb 22, 2022
- June 21, 2022
- July 19, 2022
- August 23, 2022

Follow InfoQ:
- Twitter: twitter.com/infoq
- LinkedIn: www.linkedin.com/company/infoq/
- Facebook: www.facebook.com/InfoQdotcom/
- Instagram: @infoqdotcom
- Youtube: www.youtube.com/infoq

Tudor Gîrba on how Moldable Development Offers a Novel Way to Reason About Systems

Each year, InfoQ editors discuss what we’ve been observing across the entire software development landscape, and create several trends reports, each with its own graph of the adoption curve. This helps the editorial team focus its reporting on innovative technologies and ideas, and also provides our readers with a high-level overview of topics to keep an eye on.

You can read the transcript here: https://bit.ly/3uHJf16

Subscribe to our newsletters:
- The InfoQ weekly newsletter: https://bit.ly/24x3IVq
- The Software Architects’ Newsletter [monthly]: https://www.infoq.com/software-architects-newsletter/

Upcoming Events:

QCon Plus online: 
https://plus.qconferences.com/
- May 10-20, 2022
- Nov 29 - Dec 9, 2022

QCon San Francisco:
https://qconsf.com/
- Oct 24-28, 2022
- Oct 2-6, 2023

InfoQ Live:
https://live.infoq.com/
- June 21, 2022
- July 19, 2022
- August 23, 2022

Follow InfoQ:
- Twitter: https://twitter.com/InfoQ
- LinkedIn: https:// www.linkedin.com/company/infoq
- Facebook: https://bit.ly/2jmlyG8
- Instagram: https://www.instagram.com/infoqdotcom/
- Youtube: https://www.youtube.com/infoq

The InfoQ Podcast - 2022 InfoQ Software Architecture & Design Trends

Implementing microservices is really challenging, and there are many ways to fail. Holly Cummins has identified seven ways to fail at microservices, and on this episode of the podcast Thomas Betts asks her to describe them, and how they can be avoided.

Read a transcript of this interview:  https://bit.ly/3KX9B5k

Subscribe to our newsletters:
- The InfoQ weekly newsletter: https://bit.ly/24x3IVq
- The Software Architects’ Newsletter [monthly]: https://www.infoq.com/software-architects-newsletter/

Upcoming Events:

QCon San Francisco:
https://qconsf.com/
- Oct 24-28, 2022
- Oct 2-6, 2023

InfoQ Live:
https://live.infoq.com/
- June 21, 2022
- July 19, 2022
- August 23, 2022

QCon Plus online: 
https://plus.qconferences.com/
- Nov 29 - Dec 9, 2022

QCon London 
https://qconlondon.com/
- March 26-31, 2023

Follow InfoQ:
- Twitter: https://twitter.com/InfoQ
- LinkedIn: https:// www.linkedin.com/company/infoq
- Facebook: https://bit.ly/2jmlyG8
- Instagram: https://www.instagram.com/infoqdotcom/
- Youtube: https://www.youtube.com/infoq

Seven Ways to Fail at Microservices with Holly Cummins

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

Show Notes

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

Rossen Stoyanchev talks to Wesley Reisz about blocking and non-blocking architectures, upcoming changes in Spring including Spring WebFlux, the reactive web stack in Spring framework 5, due this summer.  He also discusses the differences between rxJava and Reactor.

Why listen to this podcast:

 - Spring Framework 5 is due to be released June 25 2017
 - Spring Web Flux provides a web programming model designed for asynchronous APIs
 - Back-pressure is important in a server environment; less so within a UI environment
 - It’s possible to use a Spring Web Flux client within a Spring MVC applciation
 - Managing sets of thread pools is more complicated than having a scalable asynchronous system

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

You can 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
Want to see extented shownotes? Check the landing page on InfoQ: http://bit.ly/2pPgq0G

Rossen Stoyanchev on Reactive Programming with Spring 5 and Spring WebFlux

Today on the podcast, Bernd Rucker of Camunda talks about event sourcing. In particular, Wes and Bernd discuss thoughts around scalability, events, commands, consensus, and the orchestration engines Camunda implemented. This podcast is a primer on considerations between an RDBMS and event-driven systems. 

Why listen to this podcast:
- An event-driven system is a more modern approach to building highly scalable systems.
- An RDBMS system can limit throughput in scalability. Camunda was able to achieve higher levels of scale by implementing an event-driven system.
- Command and events are often confused. Commands are actions that request something to happen. Events describe something that happened. Confusing the two causes confusion in application development of event-driven systems.

Event Sourcing: Bernd Rücker on Architecting for Scale

Today on the InfoQ Podcast, Wes Reisz talks with one of the thought leaders in Microservices, CI/CD, and Cloud -- Sam Newman. The podcast covers many of the topics, techniques, and patterns that Sam writes about in his latest book, Monolith to Microservices: Evolutionary Patterns to Transform Your Monolith. Topics covered in the podcast include understanding the problem you’re trying to solve, organizational/people changes when it comes to microservice architectures, database strategies for decomposing monolithic datastores, and why we’re seeing projects reverting from microservices to monoliths. 

Why listen to this podcast:

 - Fundamentally, microservices are distributed systems. Distributed systems have baggage (complexity) that comes along with them. The best way to deal with this complexity is not to address it. Try to solve the problem in other ways before choosing to take an organization to microservices.
 - A common issue that large enterprises run into that might be a strong indicator for implementing microservices occurs when lots of developers are working on a given problem and they’re getting in each other’s way.
 - A useful structure to follow with microservices is to make sure each service is owned by exactly one team. One team can own more than one service but having clear ownership of who owns a service helps in some of the operational challenges with microservices.
 - A release train should be a stop in the journey towards continuous delivery. It’s not the destination. If you find that you can only release in a release train, you are likely building a distributed monolith.
 - There are challenges of operating microservices when the end customer has to operate and manage it. These challenges are part of why we’re seeing projects move from microservices to process monoliths.

More on this: Quick scan our curated show notes on InfoQ https://bit.ly/2XvGzmF
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: https://bit.ly/2XvGzmF

comp.devel

TCris