Operations | Monitoring | ITSM | DevOps | Cloud

Node.js Microservices: Developing Node.js Apps Based On Microservices

Node.js application developers, in the ever-evolving business landscape, enjoy tangible advantages while incorporating microservices in Node.js apps development. The microservice architecture, or microservices, is a distinct method of software systems development, which attempts to create modules that are single-function, with well-defined operations and interfaces.

Deploying Citrix ADC with Service Mesh on Rancher

As a network of microservices changes and grows, the interactions between them can be difficult to manage and understand. That’s why it’s handy to have a service mesh as a separate infrastructure layer. A service mesh is an approach to solving microservices at scale. It handles routing and terminating traffic, monitoring and tracing, service delivery and routing, load balancing, circuit breaking and mutual authentication.

[KubeCon + CloudNativeCon EU recap] Getting some Thanos into Cortex while scaling Prometheus

Yesterday at KubeCon + CloudNativeCon EU, Grafana Labs software engineer Marco Pracucci, a Cortex and Thanos maintainer, teamed up with Thor Hansen, a software engineer at Hashicorp, to give a presentation called “Scaling Prometheus: How we got some Thanos into Cortex.” In their talk, the pair discussed a new storage engine they have built into Cortex, how it can reduce the Cortex operational cost without compromising scalability and performance, and lessons learned from running Cortex at s

Splunk Redefines Application Performance Monitoring with SignalFx Microservices APM

Splunk has a new Application Performance Monitoring solution purpose-built for monitoring and observability in today’s app-driven world: SignalFx Microservices APM. Learn from Rick Fitz, SVP and GM of IT Markets, and Karthik Rau, Area GM for Application Management, about the new release of SignalFx Microservices APM and how it helps DevOps teams innovate faster, elevate customer experience, and future-proof applications — all while adopting cloud-native technologies and microservices architectures.

How We Use Quarkus With Kafka in Our Multi-Tenant SaaS Architecture

At LogicMonitor, we deal primarily with large quantities of time series data. Our backend infrastructure processes billions of metrics, events, and configurations daily. In previous blogs, we discussed our transition from monolith to microservice. We also explained why we chose Quarkus as our microservices framework for our Java-based microservices. In this blog we will cover.

Q&A with Marek Tihkan, CTO at Dashbird: Leading and managing a Developer team

As we enter into our 4th year, we've decided to get up close and personal with our team to share with you their passion, drivers, lessons learned and significant moments of the past year. We're a young company dedicated to adding value in all corners that we reach, so we hope you find the upcoming series useful! Hey Marek, so can you tell us how long you’ve been at Dashbird and where you were before? M: I’ve been at Dashbird for two years now.

The Ultimate Guide to Microservices Logging

Microservice architecture is widely popular. The ease of building and maintaining apps, scaling CI/CD pipelines, as well as the flexibility it offers when it comes to pivoting technologies are some of the main reasons companies like Uber and Netflix are all in on this approach. As the amount of services in a microservice architecture rises, complexity naturally also rises.

Deploying AWS Microservices

There has been increasing buzz in the past decade about the benefits of using a microservice architecture. Let’s explore what microservices are and are not, as well as contrast them with traditional monolithic applications. We’ll discuss the benefits of using a microservices-based architecture and the effort and planning that are required to transition from a monolithic architecture to a microservices architecture.

Microservices vs. Service Oriented Architecture (SOA)

Technology has a way of circling around to the same ideas over time, but with different approaches that learn from previous iterations. Service Oriented Architecture (SOA) and Microservices Architecture (MSA) are such evolutionary approaches. Where lessons learned made sense, they were reused; and where painful lessons were learned, new methods and ideas were introduced.