No software architect can resist the temptation to talk about their experience with microservices. We launched an interview series with experts who talked about the benefits and challenges of microservices, when people should not use them and what impact they have on an organization. Our first interviewee is Viktor Farcic, Senior Consultant at CloudBees.
Each Monday we take a step back and analyze what has happened in the previous week. Last week we witnessed the birth of AngularDart, the release of IntelliJ IDEA 2016.2.1 and the reassurance that Java maintains its dominant position over other JVM languages. We learned why blockchain may outgrow Bitcoin and we discovered that microservices may not become a default architecture.
This year’s Java Tools and Technologies Landscape Report takes a look at the trends and patterns in the JVM, analyzes the data and makes predictions about the way the JVM landscape will look like in the next few years. We talked to Simon Maple, Head of Developer Advocacy at ZeroTurnaround, about the results of this report and what the numbers mean for developers.
In this article Peter Lawrey, CEO at Higher Frequency Trading Ltd, explains the concept of microservices denial and reveals why adopting best practices is the right thing to do. Whether you love or loath microservices, most likely you are using some best practices.
Microservices and containers such as Docker are among the most discussed topics in the world of enterprise software today. Many DevOps practitioners are looking at these technologies as a key part of delivering large software projects faster. While successful implementations are most common among smaller, “born in the cloud” organizations, larger enterprises can benefit from microservices and containers too — as long as they address some challenges head-on.
In this article Aviran Mordo, the head of back-end engineering at Wix, weighs in on the benefits of microservices and debunks some myths about what they can and cannot do.
Java Champion Peter Lawrey spoke to JAXenter editor Gabriela Motroc at JAX 2016 about when developers should use microservices and when they should choose a monolithic architecture. One of the key learnings from this interview is the following: “If you say ‘everyone has to use microservices’, you may end up using it even when it doesn’t make sense.”
JAX London, the event which brings Java, JVM experts and innovators together returns in October! To give you a taste of what JAX London will be all about, we’ve assembled a program preview which includes 30 sessions and four workshops. Hurry up and save £200! Very Early Bird ends on July 28.
Here are a few scenarios in which microservices can add (unnecessary) weight to your project. However, keep in mind that microservices can also simplify development and bolster a cooperative mindset.
In his keynote at JAX 2016, Rod Johnson, the CEO of Atomist and the creator of Spring, talked about Java’s supremacy and the rise of microservices and went through everything that happened in technology since 2008 —the last time he attended the JAX conference.
Many companies still use expensive proprietary hardware and software to provide load-balancing and routing for their users and services. We talked to JAX DevOps speaker Andrey Sibiryov about how IPVS can be used to automatically configure load balancing and routing for Docker containers using a simple Go daemon and a Docker plugin.
Algorithms are the building blocks of any application. They provide the business logic needed to turn inputs into useful outputs. In this article, we will explain how algorithms give companies a competitive advantage.
The smoldering conflict between the cheerleaders of microservices vs monolith architecture is ongoing as industry professionals cannot decide which should come first. Some claim that one should not start with a monolith if the goal is a microservices architecture while others put their faith in monoliths. Each side has a point, but it’s time to shed some light on this never-ending dilemma.
In this article we’re going to take a broad look at why you might move to implement microservices, and then discuss some of the challenges you’ll have to deal with.