badass-techie/eshoponsteroids

Cloud-native online shop powered by Java 17, Python 3, containers, and Kubernetes 🐋⚓

eshoponsteroids's Issues

Need for a Containerized or Virtualized Dev Environment

Need for a Containerized or Virtualized Dev Environment

The application currently relies on the developers having the same environment and dependencies installed on their local machines. This can lead to issues such as inconsistent versions, incompatible libraries, and configuration errors. It also makes it harder to replicate the production environment and troubleshoot bugs.

A better approach would be to use a containerized or virtualized dev environment that isolates the application from the host system and provides a consistent and portable way to run and test the application. Some possible ways to achieve this are:

• Use Docker to create and run containers for each microservice and the API gateway. Docker can also be used to create a network for the containers to communicate with each other and expose ports for external access. Docker Compose can be used to simplify the management and orchestration of the containers.
• Use HashiCorp Vagrant to create and run virtual machines for each microservice and the API gateway. Vagrant can also be used to provision the virtual machines with the required dependencies and configuration using scripts or tools such as Ansible, Chef, or Puppet. Vagrant can also create a network for the virtual machines to communicate with each other and forward ports for external access.
• Use a cloud-based dev environment such as GitHub CodeSpaces or GitPod that provides a browser-based IDE and terminal to access and run the application on a remote server. These services also offer integration with various cloud services and tools such as AWS EKS, Google Kubernetes Engine, or Azure DevOps.

The pros and cons of each option should be evaluated in terms of cost, performance, security, usability, and compatibility with the application's architecture and design principles.

No Payment Integration

No Payment Integration

The application currently does not support any payment methods for customers to purchase products. This is a major feature gap that needs to be addressed.

Some possible approaches to integrate payments are:

• Create a new Payment Microservice that handles payment processing and communicates with the Order Microservice via the Message Bus. The Payment Microservice could use a third-party payment provider such as Stripe or PayPal to process payments and store payment details securely.
• Add payment functionality to the existing Order Microservice and use a third-party payment provider as above. This would simplify the communication and coordination between the microservices, but also increase the complexity and responsibility of the Order Microservice.
• Use an external payment gateway such as Stripe Checkout or PayPal Express Checkout that redirects customers to a hosted payment page and returns them to the application after payment confirmation. This would reduce the development and maintenance effort of the application, but also limit the customization and control of the payment experience.

The pros and cons of each approach should be evaluated in terms of cost, security, scalability, usability, and compatibility with the application's architecture and design principles.