technology

infoq

Infoq

microservices

Support the show, consider donating: 1JqE3eCwn7PeFNZUq6U2LExwxFqGBS9eqM (http://bit.ly/2gl9HIP)

In their relatively short lifespan, blockchain technologies have already undergone significant milestones. Bitcoin’s blockchain, often referred to as Blockchain 1.0, features a simple database ledger that records transactions in a chronological order and represents the state of the network to participants. Ethereum, or Blockchain 2.0, introduced the notion of smart contracts. Microsoft’s Bletchley Project introduces a new modular architecture which might mark a new milestone for blockchain technologies.

Marley Gray, Principal Program Manager Blockchain at Microsoft, joins us to talk about Microsoft’s approach to blockchain architecture. With enterprise in mind, Bletchley introduces the concept of “Cryptlets”, the core building blocks for introducing a secure middleware tier into blockchain application infrastructure. These computational units, running off-chain, on secure trusted container enclave hardware, could provide trusted data to on-chain smart contract logic.

Topics discussed in this episode:
- Marley’s background and experience at Microsoft
- Why Microsoft is aggressively pursuing blockchain technologies (compared to other large tech companies like Amazon, Google, Facebook, etc)
- Microsoft’s Azure Blockchain-as-a-Service offering
- Project Bletchley, its goals and the problems it is trying to address
- The primary use cases in which Bletchley may provide value
- How Bletchley addresses the issue of deploying consortium style blockchains
- What are Cryptlets and how do they relate to Bletchley
- How Cryptlets are different from Oracles
- How Cryptlets could provide data to Ethereum-style smart contracts

Links mentioned in this episode: 
- Bletchley Whitepaper: https://github.com/Azure/azure-blockchain-projects/blob/master/bletchley/bletchley-whitepaper.md
- Blockchain as a Service (BaaS) | Microsoft Azure: https://azure.microsoft.com/en-us/solutions/blockchain/

Sponsors: 
- Jaxx: Wallets that Unify the Blockchain Experience Across Devices - http://jaxx.io

This episode is also available on :
- Epicenter.tv: https://epicenter.tv/161
- YouTube: http://youtu.be/avAouD1UHH4
- Souncloud: http://soundcloud.com/epicenterbitcoin/eb-161

Watch or listen, Epicenter is available wherever you get your podcasts.

Epicenter is hosted by Brian Fabian Crain, Sébastien Couture & Meher Roy.

161 – Marley Gray: Project Bletchley - Microsoft's Blockchain 3.0 Architecture

In this week’s podcast, Thomas Betts talks with Chris Richardson, a developer, architect, Java Champion and author of POJOs in Action. Before his workshop on Microservices w/ Spring Boot and Docker at QCon San Francisco 2016, Richardson took time to discuss his ideas on how to use DDD and CQRS concepts as a guide for implementing a robust microservices architecture.

Why listen to this podcast:

 - "Microservice architecture" is a better term than "microservices".   The latter suggests that a single microservice is somehow interesting
 - The concepts discussed in Domain-Driven Design are an excellent guide for how to implement a microservices architecture
 - Bounded Contexts correspond well to individual microservices
 - Event sourcing and CQRS provide patterns for how to implement loosely coupled services
 - When converting a monolith to microservices, avoid a big bang rewrite, in favor of an iterative approach

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

11m:51s - Microservices must be loosely coupled, usually creating a model with one database per service.
12m:45s - There is a business requirement to maintain data consistency across services, and using an event driven architecture is a good way to achieve that.
13m:38s - Event sourcing is specific technique for persisting domain objects as a series of events.
14m:11s - Just as transactions don’t like to be split across microservices, queries cannot simply join across multiple data sources. CQRS provides a solution that accommodates querying via microservices and materialized views.

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

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

Chris Richardson on Domain-Driven Microservices Design

Web service is a method of communication between two electronic devices over the internet. It follows the client server architecture. SOAP and REST are the two major classes of web services. SOAP stands for Simple Object Access Protocol and REST is the acronym for Representational State Transfer.

The key takeaways from this podcast are:

•	Understanding SOAP and REST Basics
•	Advantages and disadvantages of SOAP and REST web services
•	Difference between SOAP and REST web services
•	Choosing the best web service

About the speaker:
Mr. Vidhut Singh is a Technical Architect at MSys Technologies. He has over 10 years of experience in designing and developing Storage Host Integration products. He also has a sturdy expertise in storage integration with other enterprise products.

SOAP vs REST: Which is better and why? Expert speak..

Dan Nelson, Head of Data at Ocado Technology, is responsible for developing systems that allow Ocado - a well known, UK-based online grocer that provides home delivery - to harvest it's data both locally and in the cloud. In this interview, Dan shares examples of how Ocado is using machine learning (ML), natural language processing, and Tensorflow. He describes what Ocado is doing today with Data Science, Google Cloud, and AWS, and how he sees the ML and deep learning space evolving over the next several years.

Dan Nelson: Machine Learning & Data Science Innovation at Ocado Technology

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.

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

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

In this interview, Qlik Evangelist Rey Riel explains some of the key concepts - and challenges - a developer should be aware of when getting started with data visualization. He describes how Qlik - business Intelligence software for data visualization and guided analytics - addresses many of these challenges. He also introduces Qlik Playground, a free programming environment that allows you to use, explore, and quickly test your most complex and innovative data driven application ideas using Qlik technology.

Rey Riel serves as an Evangelist on the Developer Relations team at Qlik. Responsible for keeping Qlik Branch and Qlik Playground awesome places for developers to connect and share their creations, he is well-versed in JavaScript, SQL, HTML and has touched on over a dozen different languages in the last decade. He is also certified by Code School in Node.js, Angular.js, Express.js, MongoDB, Ruby Rails and JavaScript ES2015.

Rey Riel: Getting Started with Data Visualization and Qlik

Wesley Reisz talks with Sam Newman about microservices.  They explore the current state of the art with regards the architectural style and corresponding tooling and deployment platforms. They then discuss how microservices increase the surface area of where sensitive information can be read or manipulated, but also have the potential to create systems that are more secure.

Why listen to this podcast:

 - Different organisations have different risk appetites for new technology, so what may be appropriate for one organisation may not be appropriate technology choices for another. 
 - If you are deploying micro services then you need to know why you are doing it and what benefits you expect to get from deploying them.
 - Micro services are defined by their independently deployable units rather than their size. 
 - Using a cryptographic token that is verifiable off line is a common pattern for passing authentication contexts around to different services.
 - Serverless architectures redeuce the need to monitor server patching but does not diminish the need for monitoring application runtime or library dependencies from security patching.

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

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/2v8NJg6

Security Considerations and the State of Microservices with Sam Newman

In this podcast, Nicole Bryan, Vice President of Product Management at Tasktop Technologies, introduces the concept of software lifecycle integration, and how it enables the seamless flow of information - and software artifacts - between different tools and end users.  She describes how it  affects DevOps toolchain improves traceability between requirements and software artifacts (e.g. features, epics, stories), and explores some of the most common software lifecycle integration patterns being used today.  Finally, she talks about what's new in TaskTop integration Hub and the role of Value Stream Networks.  

Bio:

Nicole Bryan is Vice President of Product Management at Tasktop Technologies with extensive technical background and demonstrated leadership and management skills. Proven ability as both a thought leader and executor resulting in visionary, well thought out products primarily focused on data analytics and business intelligence, data visualization and software development processes. Unique, well rounded combination of experience as both technical and business practitioner and manager in both industry and consulting roles.

Nicole Bryan: Software Lifecycle Integration, Value Streams, and the DevOps Toolchain

In this podcast, Roland Plaszowski, Head of OSP Retail Systems at Ocado Technology, introduces the Ocado Smart Platform (OSP) and delves into its overall architecture.

He describes how both AWS and Google Cloud Platform are being used, how cloud has impacted the way his team works, and how data and machine learning have been useful in the context of a cloud-based, grocery retailer such as Ocado.  

He talks about the evolution of OSP’s microservices architecture and explains what skills software engineers need to have as a result of widespread cloud adoption.

Roland Plaszowski: A Look Inside the Cloud and Microservices Architecture at Ocado

Software is changing the world and we think our mission is to help progressive software-development teams adopt new technologies and practices. We do this by providing our audience with unbiased, practitioner-driven conferences, content, and an online community.

Chris Stetson on the Microservices Reference Architecture

InfoQ Industry Solutions Podcast