InfoQ Homepage Design Content on InfoQ
-
Capture - Embed - Protect, Guidelines for Domain-Driven Design
When using the core philosophy and the practices of DDD as guidelines for software design and development, they can be summarized in three principles: Capture – Embed – Protect, Steven A. Lowe claimed in his presentation at this year’s DDD eXchange conference. Capture the domain model. Embed the model in the code. Protect the domain model from corruption from other domains.
-
Q&A with Michael Ong on Cycling and Agile and the Value of UX
Michael Ong is a product and user experience expert based in Singapore. He spoke to InfoQ about his shared passions of cycling and agile and how they are complimentary, the importance of good listening skills in user experience design, the tech industry in Singapore and Indonesia, and his talk at the upcoming Agile Indonesia conference.
-
Google Invests in Cognitive: Cloud Speech API Reaches General Availability
In a recent blog post, Google announced their Cloud Speech API has reached General Availability. The Cloud Speech API allows developers to include pre-trained machine learning models for cognitive tasks such as video, image and text analysis in addition to dynamic translation. The Cloud Speech API was launched, in open beta, last summer.
-
The Importance of Patterns in DDD
There are lots of patterns outside of Domain-Driven Design (DDD) that are important to know, and they will help you design better systems, Cyrille Martraire claimed in his presentation at the recent DDD Europe Conference in Amsterdam when discussing the importance of patterns.
-
Relearning Functional Service Design for Microservices: Uwe Friedrichsen at microXchg
The opening talk of the microXchg microservices conference was delivered by Uwe Friedrichsen, and discussed “Resilient Functional Service Design”. Key takeaways included: microservice developers should learn about fault tolerant design patterns and caching; understanding Domain-Driven Design (DDD) and modularity is vital; and aim for replaceability of components rather than reuse.
-
Eric Evans: DDD is Not for Perfectionists
A problem with Domain-Driven Design (DDD) since the beginning has been the too common hunt for perfect designs, but DDD is not for perfectionists. In order to stop that hunt you need to have some idea of how to create software that is well designed, yet not perfect, Eric Evans noted in his presentation at the recent DDD Europe Conference in Amsterdam.
-
NIST Guidelines Require Second Auth Factor When Using Biometrics
NIST has released a public draft of new Digital Identity Guidelines, described as “a significant update from past revisions.” The guidelines describe acceptable use of multi-factor authentication (MFA). Furthermore, when using biometric data as one authentication factor, it must be combined with something you have, and not something you know, such as a password.
-
The Future of Microservices: Functional Service Design and Observability
In preparation for the upcoming microXchg conference, running 16th and 17th February in Berlin, InfoQ sat down with Uwe Friedrichsen and Adrian Cole and discussed functional service design, the new challenges with observing a distributed system, and what the future holds for the microservice architectural style.
-
The Dangers of If Statements in Domain Logic
The if statement found in most programming languages has two major roles, validating input to protect the domain from erroneous data, and for dealing with business logic inside the domain. Unfortunately, we spend too little time managing the risks from a business or domain perspective, Udi Dahan claimed in his presentation at the recent DDD Europe Conference in Amsterdam.
-
Bringing the Domain Back to Software Development
If you read the business press of today, you will find that the business side of the world sees IT as an impediment that holds them back. To overcome this, we need to shift focus from the machines to the domains and start reading and learning about the domains we are working in, David West noted in his presentation at the recent DDD Europe Conference in Amsterdam.
-
Start with Events and DDD When Building Microservices
Domain-Driven Design (DDD) is a great technique bringing designs closer to the domains we are working in, but too often we make early decisions with a focus on structure, which is not the intention of DDD. Instead we should start with the events in a domain, Russ Miles claims when describing the advantages of going “events-first” when building microservices.
-
Focus on the Process, Not on Individual Microservices
The key to success when working with a microservices based distributed system is to focus on the distributed process as a whole, not on the microservices themselves. The services are the least important part, Eric Ess claimed at the recent Microservices Conference in London, in his presentation on how to monitor distributed processes at jet.com.
-
Large Scale Experimentation at Spotify
When you want to scale the number of A/B tests to do many experiments at the same time, you need to adopt your processes and platform, and it might also impact your culture. Doing product research with controlled experiments helps to confront your ideas about how customers will use your product in reality, and check if those ideas actually impact user behaviour.
-
The Long History of Microservices
Microservices has a very long history, not as short as many believe. Neither was SOA invented in the 90s. We have been working with the core ideas behind services for five decades, Greg Young explained at the recent Microservices Conference in London, during his presentation on working with microservices.
-
Behaviour-Driven Development Anti-Patterns
Behaviour-Driven Development (BDD) can help in improving how business stakeholders and software developers communicate with each other, but there are some common anti-patterns when using Cucumber to run the automated tests, which Aslak Hellesøy, Matt Wynne and Steve Tooke described in a recent discussion.