This is stuff we needed: - [x] Log dependencies of your ITU-MiniTwit. - [ ] Create a Docker Swarm cluster for your MiniTwit in which all components run as services. - [ ] Implement a rolling update strategy to your build chain. - [x] Refactoring for Clean Subsystem Interfaces - [x] Enhance your CI Pipelines with at least two static analysis tools - [x] Try to develop a high-level understanding of ITU-MiniTwit. - [x] Migrate ITU-MiniTwit to run on a modern computer running Ubuntu 18.04. - [x] Refactor ITU-MiniTwit to another language of your choice. - [x] Start implementing an API for the simulator in your ITU-MiniTwit. - [x] Describe Distributed Workflow - [x] Complete implementing an API for the simulator in your ITU-MiniTwit. - [x] Introduce a DB abstraction layer in your ITU-MiniTwit. - [x] Release and deploy your ITU-MiniTwit. - [x] Complete implementing an API for the simulator in your ITU-MiniTwit. - [x] Creating a CI/CD setup for your ITU-MiniTwit. - [x] The Simulator starts today! - Send a PR with your URLs - [x] Add Monitoring to Your Systems - [x] Adding logging to your system (if you use the ELK stack) - [x] Write an SLA - [x] Start Monitoring Each Others SLA - [x] Pen Test Your System - [x] Test the Security of Your Monitored Team - [x] Enhance your CI Pipelines with a Software Quality Assessment Tool
This is stuff we needed: