Netflix leverages reactive system concepts to produce highly interactive and engaging User Interfaces. By using functional programming, Rx, and an intentional training method, they are able to ramp up their developers to produce reactive code quickly and with few bugs. Jafar explains how Netflix established this practice and gives a few pointers as to how your company can start its own.
Developer experience(DX) was one of the prime motivators for Web APIs in response to SOA. Now companies such as Apiary are focused on enhancing this experience and improving developer productivity by taking a page from the SOA book around automation through tooling. Jakub Nesetril explains the nuances of what constitutes good DX and how Web APIs need to be designed and implemented in this context.
Francesco Cesarini and Viktor Klang explain the motivation behind the Reactive Manifesto and what exactly it brings to the table. Also: what Erlang and Scala/Akka can learn from each other.
Todd Montgomery talks about improving serialization times and throughput can by understanding how your computer processes and stores data. With this new understanding, architects and developers can build their own protocols to efficiently transmit data. Todd's advice sheds new light on why software developers choose their current serialization and marshaling techniques and how they can improve.
Christian Legnitto describes FB's release process for mobile apps, how FB has no dedicated iOS or Android teams, A/B testing and the Play Beta program, tools used for the build process, and much more.
Xavier Amatriain discusses how Netflix uses specialized roles, including that of the Data Scientist and Machine Learning Engineer, to deliver valuable data at the right time to Netflix' customer base through a mixture of offline, online, and nearline data processes. Xavier also discusses what it takes to become a Machine Learning Engineer and how to gain real experience in the field.
Martin Thompson discusses the buidling of complex systems with regards to the Reactive Manifesto. Many web-based systems are built in a synchronous manner and that way of development may be their greatest barrier to scale and could greatly limit their production lifespan. Martin discusses these shortcomings and gives some advice on how to make systems truly reactive.
Victor Grazi talks to InfoQ about his popular tutorial application Java Concurrent Animated, and other things on his mind including Java, the financial industry, software development lifecycle, and being a Java Champion.
Dave Farley discusses the reasons for Continuous Delivery and Continuous Deployment, the advantages and challenges they pose, and much more.
Mike Amundsen talks about API management, versioning, and discovery. He compares RESTFul and CRUD-style APIs, discusses the notion of 'affordance,' and introduces hypermedia APIs. He examines documentation modelling frameworks for APIs - like Swagger - and also provides his thoughts on API governance, OAuth 2.0, and web single sign-on.