@@ -113,3 +113,28 @@ Using models only to handle everything in BambangShop would impact the codebase
Personally, this has helped me alot in API testing. It allows me to make repeated requests quickly, which gives me more time to analyze and debug where my program went wrong. The environment variable interests me alot, as this feature lets us define certain variable such as BASE_URL and PORT which then can be used in the request creation.
#### Reflection Publisher-3
##### Push vs Pull model
In this tutorial, we use the Push Model variation of the Observer pattern. This can be seen from the following facts:
- The publisher actively sends the complete product data to all subscriber
- The subscriber receive HTTP POST request
- The subscriber don't need to make additional request to receive notifications
##### Advantages/Disadvantage of using a Pull Model
**Advantages**
1. Better Error Handling: if a data retrieval fails, it can be retried.
2. More Control for Subscribers: They have the option to pick when to fetch data.
**Disadvantages**
1. Complex: requires two separate endpoints
2. High Latency: 2 round-trips to get updated information
3. Increased Server Load: Publisher must handle individual data retrieval requests
###### Impact of Single-Threading Notifications
The usage of single-threading notifications would impact the program negatively. The notificaitons will be sent sequentially, after one another. If there's an unresponsive or slow subscriber, it'll delay the following subscribers to receive the notifications. As the program increase in users, the delay would increase proportionally.
