Software is eating the world.
Companies large and small are going through a digital transformation journey, as they try to compete in this age of digital disruption. It’s no longer big-fish-eats-small-fish. We’re in a fast-fish-eats-slow-fish world.
One particular development architecture is dominating the discussion: Microservices.
If you’re reading this article, you’re probably familiar with the microservice architecture in some shape or form. Still, it’s nice to occasionally go back to basics and try to define what we are trying to achieve.
I like Chris Richardson’s definition of microservices at microservices.io:
“The microservice architecture is an architectural style that structures an application as a collection of loosely coupled services, which implement business capabilities. The microservice architecture enables the continuous delivery/deployment of large, complex applications. …
The Java Messaging Service (JMS) has been around since 2001. The idea was was simple: separate consumers from producers by introducing a message broker between them. Producers write to a queue or a topic, and consumers subscribe to that queue or topic. The producers and the consumers would thereby be decoupled from each other.
While JMS was great for its time, new technologies provided better performance and new features. …
This is a quick followup on “Deploying Spring Boot App to Pivotal Cloud Foundry”, that is meant to briefly show the available insights you can get from your app inside apps manager.
Apps manager, among other things, lets you obtain deep information about your running application, such its health, the events that occured, metrics etc.
The main page shows you the last events that occurred in the system and the currently running instances. You can also enable autoscaling at the push of a toggle.
Autoscaling can be configured based on various attributes, from CPU utilization to network latency.
The Trace tab shows you the recent REST API calls made to your…