martstech/aeon

Aeon is a modern microservices app that streamlines communication between services

Hi there , I'm Martin Velkov!

• 👨‍💻 A Software Developer experienced with the technologies listed in the toolbox below.
• 🔥 Curious mind. Continuously learning, seeking patterns and connecting dots.
• 🔭 Currently working on improving my programming skills!!
• I’m looking forward to learn from all amazing minds 🧠 in the tech world 🌍!

---

🧰 Toolbox

---

☕ Support

---

⚙ Stats

aeon's Issues

Implement Products API

Project Showcase: Boyan

Here you should include your idea from #2

Refactor Products service to Catalog service

The catalog service should contain only products for now (later we can think of adding filters).

Each product should contain id, title, description, price, discount, category, image and quantity.

The category should be a seperate entity with one the many relationship with the products. For now only id, name and products are required for the category.

Highly recommend following the arhitecture from the weather service . Using it you can have to seperate folders for Products and Categories instead of Forecasts.

Here is a fake store api. Use it to as an example

Also include similer products to the product details endpoint.

Bookmarks service

The bookmarks service should be very similar to the cart service, so view the details on that task

Setup CI with Azure

Seed realistic products to database

Modify product seeder to remove dummy test products and seed real data to make the store look better in preparation of the project defences.

Bookmarks Frontend

Implement comunnication between services

Customer service

We already have authentication implemented, so It is only required to have one endpoint in the customer service for reading the information of the user and later saving any if needed. Communication with other services may be involved depending on the future use cases of the project.

Frontend for for catalog service

Fix deployment docker

Docker seems to need to map the ports of all services in order to work right now. I want to map only the port of the gateway.

Add database to deployments

Currently the deployments does not support databases. See if aws can provide multiple databases without exceeding the free limit, If it is not possible, search for other solution for multiple databases and propose it.

Bug: Some prices display incorrectly

I found a little issue in the displaying of original and discounted prices in the web store frontend.
Some prices, displayed in red striketrough text (which I suppose is meant to symbolise the original price), are way lower than the prices displayed in bold (which, logically, should be the current prices, after the discount is applied).

Examples:

I suppose it is just a swap of the original and discounted prices, but nonetheless we should take a look.

Payment service

Payments with stripe seems like the most easy solution. See how to implement it using .NET and create a secure service for this.

Initialize repository using the microservices architecture

Project Showcase: Martin

Here you should include your idea from #1

Demo communication between 2 microservices

Add Temp Cors Policy

Implement Orders service

Once a payments has succeeded, the ordering service should save the order information and allow the user to view it.

Add reviews to Catalog service

Implement functionality for rating and reviewing products in addition to the current catalog.
Each review contains the product ID, the author's ID, a comment and the user's opinion (positive/negative), allowing for easier filtering of the comments. Comments can be upvoted.
Each product will also have an individual rating, calculated based on the user-submitted ones.

This functionality will be added to the existing Catalog service, so the same technologies/approaches will be used.

Fix services security issues

Project Showcase: Savina

Here you should include your idea from #2

Project Showcase

Here is the list of project categories link

Choose a category and come up with a project idea. Outline different features such as authentication, propose how to split the work on 3 and the project ideas should have 2 parts. One for the first exam and one for the second..

The project should not be too complicated, but it should still take some time for 3 people to build.

• #1
• #3
• #4

Config CI for AWS

Azure seems too painful to work with docker-compose and github actions.

Implement Cart service

The cart feature should have its own id, user id, date and products.

The products be a seperate entiry in the basket feature and should not be a copy from the catalog service. Products should contain productId from the catalog service and quantity.

Use the fake store api cart for example.

Highly recommend following the arhitecture from the weather service . Using it you can have to seperate folders for Carts and Products instead of Forecasts.