InfoQ Homepage Development Content on InfoQ
-
Can Your Company Benefit from a Progressive Web App?
Progressive web apps is a new concept that bridges the gap between websites and mobile apps. They promise offline capabilities as well as improved speed and performance. In this article, Mark Pedersen reviews the benefits of progressive web apps and how your company can benefit from this emerging technology.
-
Virtual Panel: State of Reactive in JavaScript and Elm
Reactive programming in JavaScript and the web has fairly mature libraries, yet there is much more work to do before it becomes ubiquitous. In this virtual panel, we speak with three experts that work with reactive technologies about where we're at and where we're headed.
-
How to Boost Your Skills to Become a Better Developer
Katas are great for learning new skills or to improve existing ones but don't address the intensity we face at work when there is a raging fire such as a deadline, release date, fixing a bug in huge legacy code, etc. This article covers the skills of good developers and highlights changing your training approach to improve your skills for high-intensity and challenging environments.
-
Q&A with the Author on "Designing the Requirements”, an Alternative Approach
In the book “Designing the Requirements: Building Applications that the User Wants and Needs”, the author Chris Britton proposes an alternative path that goes from understanding the requirements to deliver spot on solutions.
-
How Ousta Simulates Rides within a Two-Minute Test Cycle
Egyptian ride hailing provider Ousta has two mobile apps which interact with an event driven architecture using microservices. The combination of EDA and microservices facilitated a simulation system for automation, and a rapid development and testing cycle.
-
Advanced Use Cases for the Repository Pattern in .NET
In our previous article, we looked at the basic patterns needed to implement a repository. In many cases these patterns were such a thin layer around the underlying data access technology they were essentially unnecessary. However, once you have a repository in place, many new opportunities become available.
-
Language-Level Reactivity with Elm
Reactive programming is becoming more prevalent in the JavaScript programming world. But, it's always added on as an afterthought or a library. But what if it could exist by default, inherent to the language? Richard Feldman shows how the Elm language is just that. Elm doesn't just try to make JavaScript better, it tries to rewrite the developer experience and make it inherently better.
-
The Three Generations of AWS
When building a new system on AWS we are faced with three architectural choices around application packaging, runtime service and load balancing service. This article looks at these three options, and concludes that the Amazon EC2 Container Service provides the best architectural option for today's applications.
-
Testing RxJava
You are ready to explore reactive opportunities in your code but you are wondering how to test out the reactive idiom in your codebase. In this article Java Champion Andres Almiray provides techniques and tools for testing RxJava.
-
The SAM Pattern: Lessons Learned Building Functional Reactive Front-End Architectures
Modern User Experience requires an architecture that is able to continuously “react” not just to user inputs, but also to its broader environment. In this article, Jean-Jacques Dubray and Gunar C. Gessner talk about the lessons learned implementing the SAM pattern with different frameworks and libraries.
-
Implementation Strategies for the Repository Pattern with Entity Framework, Dapper, and Chain
This article will focus on the basic functionality that one would find in a typical repository created with .NET. We’ll look at both general functionality and how that functionality would be implemented using three different styles of ORM: Entity Framework, Dapper, and Tortuga Chain.
-
Virtual Panel: Document and Description Formats for Web APIs
In this virtual panel we hear from 4 individuals deeply involved in the Web API space. Each of them has a unique take on the values, benefits, and costs of documentation and description formats in general, and provide their own unique perspective from their vantage points across the Web. They agree on one thing: something must be done to help developers find their way through the world of Web APIs