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)
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 M... (more)
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)
How to Load-Balance Microservices at Web-Scale
By Martin Goodwell
There’s no shortage of guides and blog posts available to provide you with
best practices in architecting microservices. While all this information is
helpful, what doesn’t seem to be available in such a great number are
hands-on guidelines regarding how microservices can be scaled. Following a
little research and sifting through lots of theoretical discussion, here is
how load-balancing microservices is done in practice by the big players.
Living on the edge
When a web application frontend client communicates with... (more)
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