-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[EPIC] e-commerce demo scenario #1476
Comments
@raymondfeng @bajtos , are we thinking of having this as monorepo? |
I thought this will be implemented as a single service. I am not sure if it's worth to break this down into multiple micro services. For example, we would have to figure out how to aggregate APIs of individual microservices into a single API server for clients, perhaps using some sort of a gateway. To me, the primary purpose of this demo is to verify easy of use of our solution for integrating with different data sources, not an exercise in micro-services. With that said, there is still a question whether this example should live in our main loopback-next monorepo, or in its own GitHub repo. Considering the cost of setting up a Redis instance, a database server, etc. I think we should keep this example out of our main monorepo. I don't want to start a Docker container with Redis every time I test a change in loopback-next! If we decide to build the example app as a bunch of microservices, then I think the new GitHub repo containing this example should follow monorepo layout. The less GitHub repos we have to watch and maintain, the better for us. |
OK. It's true that the purpose of this demo scenario is to identify any gaps in LB for building a production-ready application, but not to illustrate how the microservices each built by LB app can work together. I agree that it should be a separate repo from Let me update the original description. Thanks! |
This Epic is now complete! 🎉 |
This project aims to represent an online ecommerce platform APIs to validate / test the LoopBack 4 framework readiness for GA. See loopbackio/loopback-next#1476 for more information.
Description / Steps to reproduce / Feature proposal
#1449
APIs to support the front page of a major retail e-shop. Components:
A user sign-up (registration), where the client app is submitting new model data.
It would be great if
This demo scenario is meant to be a single LB application and code resided in a separate repo other than
loopback-next
.The text was updated successfully, but these errors were encountered: