InfoQ Homepage Microservices Content on InfoQ
-
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.
-
Netflix Zuul Gets a Makeover to a Asynchronous and Non-Blocking Architecture
Rags Srinivas caught up with engineering manager at Netflix, Mikey Cohen, regarding their major re-architecture of their Zuul gateway for microservices. Cohen talks about the journey and walks through the motivation and challenges of this significant effort.
-
MicroProfile Group Holds Discussion Panel Event during JavaOne
On 22nd September, the MicroProfile group held a panel event in San Francisco to discuss the current and future situation. Albeit not being part of JavaOne, the fact that it coincided in time and city made it easy for conference-goers to attend. The panel included representatives from RedHat, Payara, SouJava, Tomitribe, IBM, and the LJC, and speculated about the shape of future Java development.
-
Categories of Monoliths
Derek Ashmore details the different types of monoliths he has come across with a view to subsequently describing how they may be broken down into more manageable components/microservices.
-
Microservices Imply a Distributed System
Moving towards microservices means moving towards distributed systems where you have to deal with latency, authorization and authentication, and messages that do not arrive, argues Sander Hoogendoorn. With microservices you can break down large systems into smaller components to regain control over the architecture.
-
Data is the Hard Part Working with Microservices
One of the hardest problem when creating and developing microservices for an enterprise is their data. Analysing the business domain using Domain-Driven Design (DDD) and reason about what your data represents will help in achieving a microservices architecture, Christian Posta claims in one of a series of blog posts about microservices implementations.
-
Solving Fat JAR Woes at HubSpot
Spring Boot 1.4 and Dropwizard 1.0 were both released at the end of July, using fat JARs. As adoption of such frameworks and microservices increases, fat JARs are becoming a more common deployment mechanism. Earlier HubSpot cited issues where Fat JARs deployments experienced problems with the maven-shade-plugin, and efficiency problems when packaging 100,000 tiny files as a JAR.
-
A Sample Serverless Microservice Architecture from Autodesk
In the webcast entitled "What's Better Than Microservices? Serverless Microservices," Alan Williams (Autodesk), Asha Chakrabarty (Amazon) and Alan Ho (Apigee) discuss the architecture of a serverless microservice built with lambda functions with Apigee end-points running on AWS.
-
Juval Löwy: Why Every Class Should Be a Service
Juval Löwy has pioneered a method of building service-oriented applications in which each class represents a service onto itself. While these applications may initially seem like 'class explosion', they are actually the product of a truly decomposed system; one that has been properly analyzed and designed. Juwal explains his intent and describes how development teams can improve from this process.
-
Lessons Learned from the #api360 Microservices Summit 2016
At the API Academy #api360 Microservice Summit event, held in New York City, a collection of microservice experts presented their thoughts on the current state-of-the-art of microservices and associated architectural and organisational issues, process and technology.
-
Neha Narkhede: Large-Scale Stream Processing with Apache Kafka
In her presentation "Large-Scale Stream Processing with Apache Kafka" at QCon New York 2016, Neha Narkhede introduces Kafka Streams, a new feature of Kafka for processing streaming data. According to Narkhede stream processing has become popular because unbounded datasets can be found in many places. It is no longer a niche problem like, for example, machine learning.
-
Five Ways to Not Mess Up Microservices in Production
Alex Zhitnitsky of Takipi has written about five ways to try to improve the chances of successful deployed of microservices into production. As we will see, they share many similarities with other independent efforts, perhaps leading us to agreement on top areas of concern, if not ways of solving these problems.
-
Searching for the Right Abstraction in a Microservice Platform. Q&A with VAMP creator Olaf Molenveld
Magnetic.io are creating a new open source microservice deployment platform named VAMP, or Very Awesome Microservices Platform, which offers a ‘platform-agnostic microservices DSL’ for deployment, A/B testing, canary releasing, autoscaling, and an integrated metrics and event engine. InfoQ recently sat down with Olaf Molenveld, CEO and co-founder of magnetic.io, the company building VAMP.