@@ -68,16 +68,16 @@ You can install Postman via this website: https://www.postman.com/downloads/
- [✓] Commit: `Implement list_all_as_string function in Notification repository.`
- [✓] Write answers of your learning module's "Reflection Subscriber-1" questions in this README.
-**STAGE 3: Implement services and controllers**
- [] Commit: `Create Notification service struct skeleton.`
- [] Commit: `Implement subscribe function in Notification service.`
- [] Commit: `Implement subscribe function in Notification controller.`
- [] Commit: `Implement unsubscribe function in Notification service.`
- [] Commit: `Implement unsubscribe function in Notification controller.`
- [] Commit: `Implement receive_notification function in Notification service.`
- [] Commit: `Implement receive function in Notification controller.`
- [] Commit: `Implement list_messages function in Notification service.`
- [] Commit: `Implement list function in Notification controller.`
- [] Write answers of your learning module's "Reflection Subscriber-2" questions in this README.
- [✓] Commit: `Create Notification service struct skeleton.`
- [✓] Commit: `Implement subscribe function in Notification service.`
- [✓] Commit: `Implement subscribe function in Notification controller.`
- [✓] Commit: `Implement unsubscribe function in Notification service.`
- [✓] Commit: `Implement unsubscribe function in Notification controller.`
- [✓] Commit: `Implement receive_notification function in Notification service.`
- [✓] Commit: `Implement receive function in Notification controller.`
- [✓] Commit: `Implement list_messages function in Notification service.`
- [✓] Commit: `Implement list function in Notification controller.`
- [✓] Write answers of your learning module's "Reflection Subscriber-2" questions in this README.
## Your Reflections
This is the place for you to write reflections:
...
...
@@ -94,97 +94,18 @@ This is the place for you to write reflections:
Rust didesain dengan fokus pada keamanan memori dan thread safety tanpa bergantung pada garbage collector seperti di Java. Di Java, static variable bisa dimutasi lewat static function meskipun tanpa perlindungan bawaan yang kuat, sehingga rawan terjadi race condition ketika diakses oleh banyak thread secara bersamaan. Sebaliknya, Rust secara default mengharuskan variabel static bersifat immutable untuk menghindari potensi inkonsistensi data di lingkungan multi-thread. Untuk mengakomodasi kebutuhan mutasi, Rust menyediakan mekanisme melalui library seperti lazy_static, yang menginisialisasi variabel secara lazy sehingga berperilaku seperti Singleton, dan memastikan bahwa setiap mutasi harus melalui wrapper seperti RwLock<> atau Mutex<>. Pendekatan ini memastikan bahwa setiap perubahan data dikontrol secara eksplisit dengan mekanisme sinkronisasi, sehingga menjamin thread safety dan mencegah race condition.
#### Reflection Subscriber-2
=======
# BambangShopReceiver
1. Have you explored things outside of the steps in the tutorial, for example: src/lib.rs? If not, explain why you did not do so. If yes, explain things that you have learned from those other parts of code.
Ya, saya telah mengeksplorasi file src/lib.rs dan menemukan banyak hal menarik. File ini berperan sebagai modul inti yang menyimpan komponen penting seperti konfigurasi aplikasi, mekanisme error handling, dan root URL. Misalnya, melalui lazy_static, terdapat inisialisasi objek global seperti REQWEST_CLIENT yang dibuat menggunakan ClientBuilder, sehingga memastikan HTTP client dapat digunakan secara efisien di seluruh aplikasi tanpa harus diinisialisasi ulang setiap kali. Selain itu, APP_CONFIG dihasilkan melalui AppConfig::generate(), yang menggabungkan konfigurasi default dengan environment variable secara dinamis menggunakan Figment dan dotenvy, memberikan fleksibilitas dalam mengatur pengaturan aplikasi.
Saya juga mempelajari penggunaan crate getset yang secara otomatis menghasilkan getter untuk field dalam struct, sehingga mengurangi kode boilerplate dan meningkatkan maintainability. Fungsi seperti compose_error_response juga diimplementasikan untuk standarisasi respons error, memudahkan debugging, dan menjaga konsistensi penanganan error di seluruh aplikasi. Pendekatan modular dan terorganisir seperti ini memisahkan logika bisnis dari infrastruktur dasar, sehingga membuat kode lebih mudah dipahami, di-debug, dan dikembangkan ke depannya.
<br><br>
2. Since you have completed the tutorial by now and have tried to test your notification system by spawning multiple instances of Receiver, explain how Observer pattern eases you to plug in more subscribers. How about spawning more than one instance of Main app, will it still be easy enough to add to the system?
## Getting started
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
## Add your files
-[ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
-[ ] [Add files using the command line](https://docs.gitlab.com/topics/git/add_files/#add-files-to-a-git-repository) or push an existing Git repository with the following command:
-[ ] [Set up project integrations](https://gitlab.cs.ui.ac.id/allan.kwek/bambangshopreceiver/-/settings/integrations)
## Collaborate with your team
-[ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
-[ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
-[ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
Use the built-in continuous integration in GitLab.
-[ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/)
-[ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
-[ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
-[ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
-[ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
***
# Editing this README
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
## Suggestions for a good README
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
## Name
Choose a self-explaining name for your project.
## Description
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
## Badges
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
## Visuals
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
## Installation
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
## Usage
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
## Support
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
## Roadmap
If you have ideas for releases in the future, it is a good idea to list them in the README.
## Contributing
State if you are open to contributions and what your requirements are for accepting them.
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
Penerapan Observer Pattern memudahkan penambahan subscriber baru karena sistem dirancang berdasarkan prinsip Open-Closed. Artinya, kita dapat menambahkan jenis subscriber yang berbeda tanpa perlu mengubah kode inti pada publisher. Setiap subscriber hanya perlu didaftarkan ke publisher dan akan secara otomatis menerima notifikasi saat terjadi perubahan.
## Authors and acknowledgment
Show your appreciation to those who have contributed to the project.
Untuk kasus jika ada lebih dari satu instance Main App, setiap instance dapat mengelola daftar subscriber-nya sendiri secara independen. Selama proses pendaftaran subscriber melalui API berjalan dengan baik, tiap instance akan menangani notifikasi secara terpisah. Jika diperlukan notifikasi lintas instance, maka solusi seperti sistem pub/sub terpusat atau komunikasi antar instance dapat diterapkan untuk menjaga fleksibilitas dan skalabilitas sistem secara keseluruhan.
## License
For open source projects, say how it is licensed.
3. Have you tried to make your own Tests, or enhance documentation on your Postman collection? If you have tried those features, tell us whether it is useful for your work (it can be your tutorial work or your Group Project).
## Project status
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
\ No newline at end of file
Ya, saya sudah mencoba melakukan testing dan menambahkan dokumentasi pada Postman collection ketika proyek kelompok PBP. Fitur testing di Postman memungkinkan verifikasi respons API terhadap berbagai skenario, termasuk validasi error handling dan struktur data, sehingga memastikan setiap endpoint berjalan sesuai harapan. Selain itu, dokumentasi yang lengkap dengan deskripsi endpoint, parameter, contoh request-respons, dan penjelasan error memudahkan anggota tim untuk memahami cara kerja API dan meningkatkan kolaborasi. Fitur automated testing dan unit tests juga membantu menjaga konsistensi fungsionalitas aplikasi seiring iterasi pengembangan, sehingga penggunaan Postman sangat berguna baik untuk proyek tutorial maupun proyek kelompok.
