Promiscuous integration is known as a pub-sub framework in which we replicate the data, in the Ruby applications. In this way, out or order updates are removed and new updates are being replicated time to time thus the subscriber always see the updated updates.
How it works
If you are into CI (continuous integration) when it comes to dealing with dependencies what strategy you are planning to use? Many questions are going to arise when you are dealing with dependencies. Now when you check in to the binary dependency then it is quite difficult for you to get the updates time to time. This is the time when you need to make a strategic decision so that all the difficulties can be managed.
PI is providing you with many benefits over CI and you will face less difficulties with working on any project. You can get the updates and it will be your choice that when do you want to get updates.
- It can replicate from Postgres, Mongo, Redis and ElasticSearch
- From one application to another it can observe the model changes and known as remote observer.
- It is able to publish the virtual attribute as well.
Why is it different from Continuous integration?
We need to figure out the fact that on what basis PI is better or different from CI and under what circumstances.
First of all, we will discuss about CI so that we will be able to know how is it different from PI. When you are working with CI, you will not be able to use the VCS. However, the mainline is said to be healthy hence you will be able to release after any commit safely. If you have made a feature which you do not want to release then it will not affect the other functionalities of CI, but it will require to do some masking if you do not want it to be seen.
While working with PI, it will give you many features to work with. You can release the feature with ease and if you do not want to do that then you can hide it from the UI easily, there will not be any kind of hassle for you.
— Slimane Zouggari