Today’s newsletter focuses on….Tadaaa! Microservices!
Microservices, SOA, and ruxit – A Cheat Sheet
Why the heck are microservices the business of an APM tool you ask? Read this
blog post to find out.
We are proud to present our new microservices digest.
This digest provides an overview of good resources that are well worth
reading. We’ll be updating this page as new content becomes available, so I
suggest you bookmark it.
Also, expect more digests to come on different topics that make all of our
IT-hearts go boom!
Blog post: SOA or Microservices?
(It doesn’t matter a pair of fetid dingo’s kidneys)
Besides being the victim of excessive hype, microservices are also very
controversial. It’s said by some to be nothing more than plain-old SOA
(“Service Oriented Architecture”, not “Sons of Anarchy”) just in new
Top Two Features of Self Healing Microservices
By Martin Goodwell
Microservices-based environments are more complex than their monolithic
counterparts. To operate microservices environments with the same level of
convenience that you’ve come expect from operating self-contained
monolithic application environments, you need to have the right tools in
place and rely on best practices that will keep your microservices healthy.
We’ve noticing an increasing number of microservices environments deployed
by our customers, and the trend only seems to be increasing. We recently
asked some... (more)
This is a no-hype, pragmatic post about why I think you should consider
architecting your next project the way SOA and/or microservices suggest. No
matter if it’s a greenfield approach or if you’re in dire need of
refactoring. Please note: considering still keeps open the option of not
taking that approach. After reading this, you will have a better idea about
whether building multiple small components instead of a single, large
component makes sense for your project.
This post assumes that you have experience with software architecture and
services (you’ll find some words about... (more)
Analyze Node.js Errors Down to the Code Level
By Michael Kopp
Beginning with Ruxit Agent v1.73, Ruxit provides root cause analysis for
Node.js errors down to the code level. As with other services, Ruxit marks
web requests to Node.js as failed based on the accompanying HTTP error code.
Simply click the Failure rate portion of any Node.js service infographic to
view the Failure analysis chart. If you have failures, click the View details
of failures button to see which requests failed along with an overview of
failure reasons sorted by HTTP code. You can select a single request to f... (more)
Newsletter: MongoDB, JMS and RabbitMQ
The ruxit team has been working hard to make your #monitoringlife even more
comfortable. We’re happy to announce monitoring support for MongoDB and
Java messaging services.
Track your MongoDB connections
MongoDB is a popular cross-platform, document-oriented database that is
designed for high availability and automatic scaling. ruxit now supports
tracking and inspection of all MongoDB statements from your Java-based
applications. ruxit also records the row counts retrieved per statement. As
you might guess ruxit also monitor... (more)