This is the second article of a two article series in which we try to work from the abstract level of IoT reference architectures towards the concrete architecture and implementation for selected use cases. This second article will show how to apply this architecture to real world use cases - one being in the field of smart homes, one in the field of insurance.
In this week's podcast QCon chair Wesley Reisz talks to Matt Ranney, who is the Chief Systems Architect at Uber, where he's helping build and scale everything he can. Previously, Matt was a founder and CTO of Voxer, probably the largest and busiest deployment of Node.js.
A microservice's efficiency and resource consumption patterns are dramatically affected by its threading model. Choosing the correct model for your solution is a basic requirement for success. 4
In this 2nd installment on diagnosing performance issues, performance guru Andreas Grabner focuses on spotting performance & scalability issues in distributed Microservice Oriented Architecture
New impetus to performance testing: performance split testing as attempt to make performance testing of web services more dynamic by using real-time production traffic and applying the A/B testing. 3
Angular 2 & TypeScript have brought true object oriented development to the world's most popular web development framework. This article provides a high-level overview of Angular 2. 6
For our inaugural podcast QCon chair Wesley Reisz talks to Adrian Cockcroft. Topics include microserivces, “Serverless" computing, Persistent memory and other potentially disruptive trends. 3
This article summarizes the key takeaways and highlights from QCon London 2016 as blogged and tweeted by attendees.
Reveno is a powerful new, performant, JVM based lock-free transaction processing framework based on CQRS and event-sourcing patterns. In this article we develop a simple trading system using Reveno. 1
At the MicroXchg conference in Berlin, Bora Tunca from SoundCloud presented the evolution of SoundCloud’s microservices architecture throughout the years. 3
Beyond any ideal design of your API, reality strikes back with the concrete and differing concerns of varied API consumers. 3