InfoQ Homepage Microservices Content on InfoQ
-
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.
-
Is Gartner's Report of Java EE's Demise Greatly Exaggerated?
Gartner has produced a report called “Market Guide for Application Platforms”, citing Java EE’s “revenue decline” in reporting “a clear shift” in the application platform market. The Java EE community takes issue with those findings, in personal comments to InfoQ.
-
Netflix Conductor, an Orchestration Engine for Microservices
Netflix has developed an orchestration engine called “Conductor”, and has used it internally in production for the last year . During this time they executed some 2.6 million process workflows, starting with linear ones and ending with dynamic ones running over multiple days. Now they have open sourced Conductor, making it available to all those interested in workflow orchestration.
-
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.
-
Authentication Strategies in Microservices Systems
Software security is a complex problem, and is becoming even more complex using Microservices where each service has to deal with security, David Borsos explained at the recent Microservices Conference in London, during his presentation evaluating four end-user authentication options within a microservice based systems.
-
Sharing Experiences from a Microservices Journey
In our continued effort to showcase lessons learned by microservices practitioners, we look at an article Piotr Gankiewicz has recently written with his own tips and tricks. These include references to CQRS, asynchronous architectures, service discovery and how choosing the right database for each service is important.
-
Developer Panel Discusses Microservices, Containers and Serverless at Microsoft Connect
A developer panel was held at Microsoft Connect() following the multiple annoucements of new features and releases. Microservices and containers are in the center of the discussion, along with Azure, serverless architecture and developer tooling.
-
Lawyer.com: Early Adopter of HTTP/2, Speaks to InfoQ
Lawyer.com recently announced that they are adopting the HTTP/2 protocol. Gerald Gorman, tech entrepreneur, CEO, and co-founder of Lawyer.com, spoke to InfoQ about their technology implementation, their position on microservices and lightweight containers, their unique search engine, and their use of social media.
-
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.
-
Microservices and Security
When it comes to application security, we often include it as an afterthought. We have learnt how to add test into the development workflows, but with security we often assume someone else will come and fix it later on, Sam Newman claimed in his keynote at this year’s Microservices Conference in London.
-
Microservices and Stream Processing Architecture at Zalando Using Apache Flink
Javier Lopez and Mihail Vieru spoke at Reactive Summit 2016 Conference about cloud-based data integration and distribution platform used for stream processing in business intelligence use cases. Their solution is based on technologies such as Flink, Kafka and Elasticsearch.
-
Achieving Cloud-Native Operability
To drive operational maturity you need a microservices architecture, continuous delivery process, DevOps culture and platform automation. Together these four help you to transform your whole organization for achieving cloud-native operability to continuously deliver additional value to your customers.
-
Komand Principal Engineer Sean Kelly on Microservice Fallacies
Sean Kelly, a Principal Engineer at Komad, has written about his experiences around microservices and five "truths" which developers believe microservices will bring to their architectures, applications and teams, but which, in his view, are not always the case.
-
Reactive Summit 2016 Conference: Reactive Microservices and Staging Data Pipelines
Reactive microservices, data center scale operating system (DCOS), and staging reactive data pipelines were the highlighted topics at Reactive Summit 2016 Conference held this week. InfoQ team attended the conference and this post is a summary of the first day's events at the conference.
-
Continuous Delivery at Klaverblad Insurance
Continuous delivery should be treated as an agile project as it is about automating your deployment. You have to speed up in small steps and gain trust by doing small deliveries and solve problems fast. The story about how Klaverblad insurance has implemented Agile, DevOps, continuous delivery, and microservices.