Please share your feedback, and questions if any below.
@biltriq23322 жыл бұрын
Good Tutorial keep it up man
@Vinayakvs Жыл бұрын
Very simple and efficient architecture. Clear and concise explanation. Great job bro !
@mutasemtayeh382Ай бұрын
Great you tube, in a relatively short video you successfully explained complex concepts in simple manner, well done
@ArchitectureBytesАй бұрын
Thanks!
@abdellaouikhoubaib3987 Жыл бұрын
The only video in the youtube database that answers my questions. Greate job bro and keep going
@koushikr1596 Жыл бұрын
Probably, you can make a video on how to do this using single table design by leveraging the concept of index overloading.
@rashedjony8108 Жыл бұрын
Thanks for the video. It's really very clear overview architecture eCommerce on AWS. Thanks Again!
@klowdboss1026 Жыл бұрын
This is great work AB! Looking forward to seeing more of your videos.
@codemaverick695 ай бұрын
What tool do you use for your high-level architecture diagram? Your content is clean and precise. No noisy data
@9elitemarketingservicesllc57521 күн бұрын
Great video! 👏👏👏👏 If someone wanted to find a job designing websites like this in AWS what would this role be called? What kind of skills would one need to learn to do projects like these?? 🤔 This is amazing!!!
@lets_learn8843Ай бұрын
I love your contents.
@mersaldev10 ай бұрын
very good explanation thanks
@venkatasaikrishnayarabolu5765 Жыл бұрын
Your voice and your videos are nice. Great efforts sir kudos 👏
@OmpalSingh-pw7mc Жыл бұрын
Very Nice Explanation👏👏
@eduardovergara1490 Жыл бұрын
Nice video! It would be awesome if you could expand this video, giving some introduction to the implementation of warehouse management and logistics systems on AWS. It would be awesome to learn that too. Thanks!!
@ArchitectureBytes Жыл бұрын
Sure.. will look into that too! Thanks.
@amitsinha6988 Жыл бұрын
This really good. Really helpful.
@ashutoshshukla53444 ай бұрын
Helpful content ❤
@trivargadhathripalla8545 ай бұрын
Good video ! Could you please do a similar one for Card issuing platform and Payments?
@K71947 Жыл бұрын
Thanks for the video ..how much the startup cost for it in aws?..can you explain?
@ArchitectureBytes Жыл бұрын
Pls see AWS Pricing Calculator: calculator.aws/
@rajeshsahu605 Жыл бұрын
I appreciate the quality of your content and the effort you put in. However, I am unsure of the benefit of using opensearch in this case, as we can use the customerId primary key to quickly look up specific customer orders. In contrast, searching using opensearch would have a time complexity of log N. Could you please provide a brief explanation of the purpose of using opensearch in this context?
@ArchitectureBytes Жыл бұрын
If you are searching on a specific field - yes you could go to the database directly. OpenSearch is good with semi-structured data. For example product names, descriptions, customer reviews and so on. In addition it helps with AutoComplete functionality (for eg. product names) and the OpenSearch Dashboard provides useful quick visualizations too. This has not been explicitly articulated in the video though.
@rajeshsahu605 Жыл бұрын
@@ArchitectureBytes got it that's what I am looking for thanks for your explanation...do you have the architecture diagram or you have real time project as well for above...i just want to understand how you are managing the orders as we have to maintain tracking, when customer can cancel,return and download invoice order ...if you have a real time project it would be great if you can share your knowledge
@mewithmylove Жыл бұрын
Nice Video! Can you highlight how to maintain admin, customer and cart session without using available ecommerce platform?
@ArchitectureBytes Жыл бұрын
Authentication is handled at API Gateway. User information can be passed by API Gateway to downstream microservice (eg lambda function). The microservice can store/retrieve session/shopping cart information from database (9:00) by logged in user. Hope this answers your question.
@me1kshitij Жыл бұрын
What would be the average costing of this infra?
@ArchitectureBytes Жыл бұрын
Pls see AWS Pricing Calculator: calculator.aws/
@maxpaynestory5 ай бұрын
What if we have a use case in which we have to use 3 services like order service, inventory service, cart service. How would we go around it?
@ArchitectureBytes5 ай бұрын
Your question isn't clear to me - Could you please elaborate? These services are depicted in the architecture.
@anmacdev4 ай бұрын
is possible to use Single-Table Design in DynamoDB?
@ArchitectureBytes4 ай бұрын
Sure!
@freelancerwick5418 Жыл бұрын
Why this architecture could be superior to Wordpress Woocommerce being run on AWS Lightsail ?
@ArchitectureBytes Жыл бұрын
This video presents architecture of a generic eCommerce platform. WooCommerce & Shopify are products/ready-made solutions. Your choice of platform will depend on your own unique needs. Shopify Choose a paid plan, configure - you are ready. Fairly quick setup. WooCommerce Requires you to host solution yourself - Wordpress with WooCommerce plugin. If you need features beyond what is available - you either buy additional paid plugins or make modifications to code yourself. They are great solutions, and power plenty of eComm websites. Since, they are ready-made solutions - you are bound by their ecosystems.
@K71947 Жыл бұрын
@@ArchitectureBytes agree regarding your answer...this architecture more custom and flexible..
@WTF-SHORTS-VIDEOS5 ай бұрын
Hey! why you didnt put a WAF ?
@ArchitectureBytes5 ай бұрын
That's an optional service for web security, not a part of core architecture.
@yjhsjtu9 ай бұрын
I do not think dynamodb is a good choice for product table. Normally product table needs to support a lot of things, for example, search by fields like brandname, price range, color, etc. Dynamodb can only support querying by partition key+ sort key. How did you handle these kind of querying?
@ArchitectureBytes9 ай бұрын
Using DynamoDB Global Secondary Index (GSI) - it is possible to efficiently search on other columns as well. You can of course use a different database too depending on your requirements, expertise etc.