API and service life cycle management platform Kong announced its new open-source project Kuma, a universal service mesh designed to increase the adoption of microservices. The problem that early adopters had with the service mesh was that the first generation meshes lacked a mature control plane and required extensive manual work and was often built … continue reading
Red Hat has announced its own service mesh solution to bring an end-to-end developer experience to microservices. Red Hat OpenShift Service Mesh provides the ability to connect, observe and simplify service-to-service communications on Kubernetes. According to the company, it is based on Istio, Kiali and Jaeger projects, and designed to free developers from having to … continue reading
In the world of software, things are getting smaller all the time: smaller teams, smaller bits of code, smaller releases, smaller places for code to live and execute (containers). The point of getting smaller is to allow your organization to think bigger by getting the most advantage out of cloud resources and bringing more value … continue reading
Many organizations say they are moving to microservices, but Gartner says that by the end of 2019, 90 percent of them will think microservices are too disruptive and switch to other methods, such as miniservices. In the meantime, enterprises are looking at how to transition away from monolithic apps, not knowing that microservices may not … continue reading
As part of GitLab’s mission to power the DevOps life cycle, it is laying out its ideal DevOps team model. “The seamless collaboration between Development and IT operations is a beautiful thing. DevOps was designed to remove silos so that these teams could work together to build, test, and deploy software faster. But there’s a … continue reading
The Apollo team wants to help developers adopt GraphQL within their microservice architectures with the announcement of its open-source project Apollo Federation. According to Apollo’s engineering manager James Baxley III, developers want to be able to access data through a single GraphQL query even if that data lives in separate places. Before Apollo Federation, Baxley … continue reading
The adoption of service meshes are giving developers new and smarter ways to connect, secure and control what is going on inside their applications and services. But it is also causing a lot of pain points and lock ins for developers. To address the problems a group of technology companies are coming together to launch … continue reading
Once you hit a stride with microservices and you are able to iterate more quickly, find and fix bugs faster, and introduce new features rapidly — it is crucial not to go overboard. You may want to try to start moving all your pieces of infrastructure to a microservice architecture, but as one company found … continue reading
It can be easy to fall into bad patterns when moving to microservices, according to Chris Richardson, microservices consultant and founder of the transactional microservices startup Eventuate. The important thing is to recognize the mistakes you are making and address them. Some common mistakes or anti-patterns Richardson sees organizations fall into are: Distribution is free: … continue reading
The benefits of microservices are undeniable. Software development companies want to be able to deliver software rapidly, frequently and reliably — and microservices are a means to that end. A recent O’Reilly Media report found that more than 50 percent of software projects are currently using microservices. Of those surveyed, 86 percent have found at … continue reading
It’s safe to say that microservices architecture is no longer an emerging new trend, but a mainstream software development strategy. Microservices aren’t just ideal for developing new applications, but are also optimal when modernizing legacy applications. Writing functionality into bite-sized, reusable components is more efficient and speeds up development. It delivers code that meshes well … continue reading
The work on a microservices project is always stressful. Such projects introduce larger data sets, faster update rates, more requests, more failures, more latency challenges, more service interdependencies, more developers, more documentation, more servers, more networks, more databases. Yet, all that doesn’t mean you should avoid microsevices-based projects. The right organization of your team … continue reading
