Welcome!

Simply Powerful Performance and Environment Monitoring

Ruxit Blog

Subscribe to Ruxit Blog: eMailAlertsEmail Alerts
Get Ruxit Blog via: homepageHomepage mobileMobile rssRSS facebookFacebook twitterTwitter linkedinLinkedIn


Top Stories by Ruxit Blog

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 my experience on the bottom of this post). I won’t go into the details of Wikipedia’s or Martin Fowler’s definitions per se. Much more I will talk about what microservices and/or SOA could and should do for your project. Microservices? SOA? Both? None? I’ll leave it up to you if they are bot... (more)

Top Two Features of Self-Healing Microservices | @CloudExpo #Cloud #Microservices

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)

Microeconomics For Application Performance By @Ruxit | @DevOpsSummit [#DevOps]

Using Microeconomics to Think About Application Performance About 15 years ago I gave an application performance presentation to some storage guys. Since I was a database jock at the time and didn’t “speak” I/O very well, I had to try a different approach. Rather than speaking over their heads in my own language, or faking it using their language, I tried to pick something neither of us were experts in – microeconomics. What’s interesting is that that presentation became my modus operandi for tuning systems. As I went from customer to customer, each with a different application ... (more)

Three Levels of Network Monitoring for DevOps By @Wall_Dirk | @DevOpsSummit #DevOps

Three Levels of Network Monitoring for DevOps By Dirk Wallerstorfer Network communications are a top priority for DevOps teams working in support of modern globally-distributed systems and microservices. But basic network interface statistics like received and sent traffic aren’t as useful as they once were because multiple microservices may share the same network interface. For meaningful analysis, you need to dig deeper and correlate network-traffic metrics with individual processes. This is however just the beginning … In this article, I’ll show you how deep the network monit... (more)

Play, Elasticsearch and Netty By @Ruxit | @DevOpsSummit [#DevOps]

Play, Elasticsearch and Netty Hello everyone! Your #monitoringlife is about to get better! Next week’s release introduces support for asynchronous I/O in Java through Netty. This enables you to monitor any application that’s built on top of Netty-based technology. Netty is an asynchronous event-driven network application framework designed for rapid development of maintainable high-performance protocol servers and clients. Here are some of the more prominent products that are now available for monitoring: Play framework Play is a high-velocity web framework for Java and Scala. ... (more)