Conclusion and Future Development

๐Ÿ“Œ Conclusion and Future Development

๐Ÿ” Conclusion

By deploying and comparing the model using Amazon EC2, S3, and RDS with other deployment methods (such as shared hosting, traditional VPS, or PaaS platforms like Heroku), it is clear that AWS offers significant advantages in scalability, flexibility, and resource management.
EC2 provides powerful and flexible computing capabilities, S3 offers stable and scalable object storage, while RDS simplifies database management with built-in features such as automatic backups, security, and scalability.
However, costs may be higher if resources are not optimized and usage is not monitored regularly.

๐Ÿš€ Future Development

In the future, the deployment process can be enhanced by integrating a CI/CD pipeline using AWS-native services such as:

  • AWS CodePipeline
  • AWS CodeBuild
  • AWS CodeDeploy

These services allow automation of the build, test, and deployment processes, reducing manual operations and speeding up feature releases.
Moreover, adopting Infrastructure as Code (IaC) with AWS CloudFormation or Terraform will improve automation, ensure consistency across environments, and align with modern DevOps practices.


๐Ÿ“Š Deployment Comparison Table

CriteriaAWS (EC2 + S3 + RDS)VPS / Shared HostingHeroku / Vercel / PaaS
PerformanceHighMedium / LimitedDepends on plan
ScalabilityExcellent (Auto Scaling)ManualGood (plan-based)
System ManagementSelf-managed (more control)Limited accessFully managed
Configuration FlexibilityVery flexibleLimitedLimited
CI/CD Integration with AWSDeep integration (CodeBuildโ€ฆ)Difficult or unavailableBuilt-in integration
CostPay-as-you-useLowFree / Expensive (based on plan)
Suitable for large applicationsโœ…โŒโŒ / Moderate
Suitable for learning / MVPโœ… (with Free Tier)โœ…โœ