infoq

In this interview NGINX's Chris Stetson describes some of the biggest pain points associated with microservices development and describes the various patterns and models - including the Circuit Breaker Pattern - covered in his new book, "Microservices Reference Architecture."  Chris also talks about the fundamental differences between microservices and SOA and how NGINX has extended the 12-Factor App to encompass microservices.  

Chris Stetson, Chief Architect of Microservices Engineering at NGINX, has architected applications for twenty years, including the first versions of Sirius Satellite Radio, Visa.com, Intel.com, Microsoft.com, and Lexus.com. He has built large monolithic systems, service-oriented architecture (SOA) applications, and most recently microservice-based systems. Most recently, Chris has authored The Microservices Reference Architecture eBook, a practical guide that helps solve many of the challenges of building microservices-based applications.

InfoQ Podcast

Chris Stetson on the Microservices Reference Architecture

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

Show Notes

Rossen Stoyanchev on Reactive Programming with Spring 5 and Spring WebFlux

Wesley Reisz talks to Daniel Bryant on moving from monoliths to micro-services, covering bounded contexts, when to break up micro-services, event storming, practices like observability and tracing, and more.

Why listen to this podcast:

- Migrating a monolith to micro-services is best done by breaking off a valuable but not critical part first.
 - Designing a greenfield application as micro-services requires a strong understanding of the domain.
 - When a request enters the system, it needs to be tagged with a correlation id that flows down to all fan-out service requests.
 - Observability and metrics are essential parts to include when moving micro-services to production.
 - A service mesh allows you to scale services and permit binary transports without losing observability.

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

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

Daniel Bryant on Microservices and Domain Driven Design

Wesley Reisz talks to Martijn Verburg, co-founder of the London Java Community and CEO of jClarity, about the JCP EC “no” vote on the Java Platform Module System (JPMS), which is due to be shipped as part of Java 9.  The talk about what JPMS offers, how it works, what the no vote means and what happens next.

Why listen to this podcast:

- Jigsaw isn’t dead
- The “no” vote was based on the submission being a bit early, and without expert group consensus that it should be submitted
- Since the vote started, several amendments have been made which addressed some of the concerns listed by those who voted “no”
- Daily calls with the expert group and interested parties will work to resolve the outstanding issues promptly
- A resubmission is due within 30 days with a future vote expected to go through

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

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

Martijn Verburg on the JCP EC “No” Vote for the Java Modules

Wesley Reisz talks to Sachin Kulkarni, Director of Engineering at Facebook, about the engineering challenges for Facebook live, and how it compares to the video upload platform at Facebook.

Why listen to this podcast:

 - Facebook Infrastructure powers the board family of apps including the Facebook app, Messenger and Instagram.  It is largely a C++ shop.  There is some Java and Python, and the business logic is all done in PHP.  The iOS apps are written in Objective C and the Android apps are in Java.

 - The video infra team at Facebook builds the video infrastructure across the whole company.  Projects include a distributed video encoding platform which results in low latency video encoding, video upload and ingest.

 - Facebook Live does encoding on both the client and the server.  The trade-off between encoding on the client side and the server side is mostly around the quality of the video vs. latency and reliability.

 - Facebook gets around 10x speed-up by encoding data in parallel compared to serial.  

 - They also have an AI-based encoding system which resulted in 20% smaller files than raw H.264.

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

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

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

Want more? Read InfoQ: http://bit.ly/2dcHmpu

Sachin Kulkarni Describes the Architecture Behind Facebook Live

On today’s podcast, Wes Reisz talks with Jason Maude of Starling Bank. Starling Bank is a relatively new startup in the United Kingdom working in the banking sector. The two discuss the architecture, technology choices, and design processes used at Starling. In addition, Maude goes into some of the realities of building in the cloud, working with regulators, and proven robustness with practices like chaos testing.

Why listen to this podcast:

 - Starling Bank was created because the government lowered the barrier to entry for banking startups in reaction to previous industry bailouts.
 - The system is composed of around 19 applications hosted on AWS and running Java and backed by a PostgreSQL database.
 - These applications are not monolithic but are focused around common functionality (such as a Card or Payment Service).
 - Java was chosen primarily because of its maturity and long term viability/reliability in the market.
 - The heart of Starling is every action the system takes happens at least once and at most once. To help with these rules, everything in their system uses as a correlation id (UUID) and are used to make sure these two rules are met.

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

Jason Maude on Building a Modern Cloud-Based Banking Startup in Java

On this week’s podcast, Wes Reisz talks with Brian Goetz. Brian is the Java Language Architect at Oracle. The two start with a discussion on what the six-month cadence has meant to the teams developing Java. Then move to a review of the features in Java 9 through 12. Finally, the two discuss the longer-term side projects (such as Amber, Loom, and Valhalla) and their role in the larger release process for the JDK.

* The JVM’s sixth-month cadence changed the way the JDK is delivered and planned. While it definitely provides more rapid delivery at expected intervals, the release train approach turned out to also improve flexibility and efficiency.
* Oracle JDK and OpenJDK are almost identical. Most of the JDK distributions are forks from OpenJDK with different bug fixes and backports applied. So the difference between the distributions now is largely which bug fixes are picked up.
* Local Variable inference (which was released as part of Java 10) illustrated the tension on making changes to the language. Many people wanted the change, but many others felt it would enable people to write bad code. Oracle had to balance the two views when making the change.
* The number of Java versions allow finer grain decision making on what is appropriate for an application. With the adoption of containers, applications are bundled with an exact JDK version rather than having to use one from a systems level. The different versions give developers more options.
* Incubating features are new libraries added to the JDK. They were offered starting with Java 9 as a way for people to test and offer feedback more rapidly. With Java 12, preview features will be released. Preview features are similar but are core platform and language features.
* Shenandoah and ZGC are both low latency garbage collectors. They originally came from different sources. While both garbage collectors are similar, each has different performance characteristics under different workloads. The two garbage collectors represent options available to JVM developers.
* Most non-trivial JDK features take more than six months to develop. Longer term side projects like Amber, Loom, Valhalla are where these features are developed prior to being released with a version of the JDK. The projects range from language enhancements to concurrency work.

infoq

Josip Gracin