Pact JVM
RabbitMQ
Pact JVM | RabbitMQ | |
---|---|---|
25 | 92 | |
1,056 | 11,608 | |
0.6% | 1.0% | |
8.9 | 10.0 | |
9 days ago | 3 days ago | |
Kotlin | Starlark | |
Apache License 2.0 | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Pact JVM
-
Running tests against a different repository (CI/CD)
API Contract Testing might be worth exploring. Gives you the ability to run it quickly locally or in CI/CD. A centralized way to validate if your changes broke another service might also be interesting. That series of videos from the same team is gold: https://docs.pact.io
-
API testing for new project (new to APIs)
We use Pact for contract testing https://docs.pact.io/
-
Why I will stop mocking for most of my Unit Tests in a Spring-Boot Application
The introduction here is quite good: https://docs.pact.io/
-
Does anyone know how to do an integration test on microservices build with asp core?
Pact.Net documentation: https://docs.pact.io/ Mountebank documentation: http://www.mbtest.org/ The Microsoft.AspNetCore.TestHost package on GitHub: https://github.com/aspnet/AspNetCore/tree/main/src/Testing/Microsoft.AspNetCore.TestHost
-
Integration testing best practices for API servers...
There's also https://docs.pact.io/ but I haven't had time yet to really look into it but probably someone else can tell something about it.
-
🤝 Contract Testing with Pact
This PoC shows a step by step implementation of contract testing using Pact.
-
Operation Pact or: How I Learned to Stop Worrying and Love Contract Testing
Contract tests assert that inter-application messages conform to a shared understanding documented in a contract. Without contract testing, the only way to ensure that applications will work correctly together is by using expensive and brittle integration tests.
-
How to Share API Changes with Your Team
If you are updating your API based on user feedback, you can work with your team or stakeholders to build an API contract describing how your API should function. You can use JSON schemas to document your API’s endpoint response codes and set up the contract. The contract must be accepted by all parties. Then, any changes made to the API must pass the contract test before being approved. Contract testing can be automated and incorporated into your CI/CD pipeline. Contract testing tools include Pact and Spring Cloud Contract.
-
Book notes: Turn the Ship Around!
Pact.
-
I have difficulties in unit testing
I have contract tests (https://docs.pact.io/) to ensure the integration works.
RabbitMQ
-
Building Llama as a Service (LaaS)
Although they did not make it into production, I experimented with the RabbitMQ message broker, Python (Django, Flask), Kubernetes + minikube, JWT, and NGINX. This was a hobby project, but I intended to learn about microservices along the way.
-
A Developer's Journal: Simplifying the Twelve-Factor App
Messaging/Queueing Systems (Amazon SQS, RabbitMQ, Beanstalkd)
-
FastStream: Python's framework for Efficient Message Queue Handling
Later, we discovered Propan, a library created by Nikita Pastukhov, which solved similar problems but for RabbitMQ. Recognizing the potential for collaboration, we joined forces with Nikita to build a unified library that could work seamlessly with both Kafka and RabbitMQ. And that's how FastStream came to be—a solution born out of the need for simplicity and efficiency in microservices development.
-
The Complete Microservices Guide
Inter-Service Communication: Middleware provides communication channels and protocols that enable microservices to communicate with each other. This can include message brokers like RabbitMQ, Apache Kafka, RPC frameworks like gRPC, or RESTful APIs.
-
Project Structure Review [.Net] [Console]
This is an implementation of pub/sub. The publisher is on a separate project. The message broker is Azure Service Bus. We use NServiceBus for code implementation. I use rabbitMQ broker for local tests. Nothing I can do about the tech stack. This is more of a high level single project structure review 😅
-
The Role of Queues in Building Efficient Distributed Applications
RabbitMQ is a robust and highly configurable open-source message broker that implements the Advanced Message Queuing Protocol (AMQP).
-
Should I chain calls in backend?
When using third-party services, especially within a "transaction", it's often a good idea to use a persistent Message Queue (MQ) system like RabbitMQ. Go through all their tutorials to get a really good understanding of how message queues work and how they can be used to solve your problem.
- Node still seems better than python after all this time for web server speed but..
-
Delayed events pattern, no more crons
The best technical solution to provide the event queues is to use a message-broker technology like RabbitMQ.
- RabbitMQ 3.12.0 Released
What are some alternatives?
WireMock - A tool for mocking HTTP services
NATS - High-Performance server for NATS.io, the cloud and edge native messaging system.
REST Assured - Java DSL for easy testing of REST services
mosquitto - Eclipse Mosquitto - An open source MQTT broker
Testcontainers - Testcontainers is a Java library that supports JUnit tests, providing lightweight, throwaway instances of common databases, Selenium web browsers, or anything else that can run in a Docker container.
MediatR - Simple, unambitious mediator implementation in .NET
Mockito - Most popular Mocking framework for unit tests written in Java
nsq - A realtime distributed messaging platform
Cucumber - Cucumber for the JVM
BeanstalkD - Beanstalk is a simple, fast work queue.
Karate - Test Automation Made Simple
rq - Simple job queues for Python