Almost all applications that perform anything useful for a given business need to be integrated with one or more applications. With microservices-based architecture, where a number of services are broken down based on the services or functionality offered, the number of integration points or touch points increases massively.
Are you working in a tight development spiral? You make changes to files that propagate to a massive project build. But you just need to verify that the files you're working on will build. Here's an easy way to do that.
Benchmarking HTTP servers is beset by several difficulties: tests may be conducted with unrealistic parameters (e.g., pure overhead v maximum concurrency), and thus yield unuseful results. Our tests are different and produced some interesting outcomes that yielded new learnings about HTTP performance in the wild.
MUnit is a Mule application testing framework which allows us to easily build automated tests. With MUnit, we can create Mule tests by writing common Java code.
JSON is a text-based data interchange format that is lightweight, language independent, and easy for humans to read and write. In the current enterprise, JSON is used for enterprise messaging, communicating with RESTful web services, and AJAX-based communications.
We have less and less time to test products before release. How can we keep up with things like continuous deployment and still deliver quality products? Read on to find out.
As microservices architectures are increasingly optimized for speed and simplicity, developers are increasingly using NATS—a lightweight high-performance, cloud-native messaging system—for inter-service communication. An interesting project developed in the NATS community bridges HTTP and NATS, and is explained in this article by Radomir Sohlic.
When developing RESTful web services, people are often confused with handling exceptions. This post will explain a powerful tactic for using exception mapper with the Dropwizard framework.
CORE
