Veniqa

Hi Guys, A while ago I posted in here in regards to open-sourcing the tech behind our failed E-commerce startup Veniqa. We received a lot of constructive feedback from the community and the surge of traffic also pushed Veniqa to spotlight making it one of the top trending projects on Github for a while. Thank you. We have been making a dedicated effort to address a lot of your constructive feedback. We recently added a quickstart mode for developers to launch the entire platform locally in minutes to save grunt work and ease code contribution. So, if anyone in the community wants to make some open-source contributions in this quarantine season, we'd be glad to get your help. https://github.com/Viveckh/Veniqa Our immediate next plans involve: - Trimming down the custom business logic and making the platform a more general-purpose e-commerc

Thanks for the question - for clarity, this is the file I'm referring to in this reply: https://github.com/Viveckh/Veniqa/blob/develop/shopping-serv... 1. The service is a leaky abstraction, it knows about HTTP status codes and presumably the response body format. The point of separating concerns is to make code reusable, HTTP response codes don't make sense outside of a HTTP call. Similarly, any calling code needs to know that `sortRule` is expecting a MongoDB sort parameter. 2. The control flow is super unclear due to mixing async/await and Promise API coding styles. The `.catch()` call on the promise chain means that the `catch` block will never be hit and the API will always return OK, with the error object exposed to the client in the `responseData` - likely exposing implementation details about the server via the stacktrace on the e

What about the myriad of try catch console.log. With the statement in the readme "Database & file-based logging" unless they are overriding console, then I don't even know what they mean. https://github.com/Viveckh/Veniqa/search?q=console.log&unsco...

It might be a good read to see how other people are solving a problem. But I wouldn't use it directly. After looking at the code for a few minutes I noticed this: https://github.com/Viveckh/Veniqa/blob/develop/shopping-serv... It makes sense that awkwardly hard coded hacks like this will exist in a startup's piece of software. But it's possibly full of similar things that might take a lot of effort to find, much less fix. When money is running out and deadlines are looming its hard to have the discipline to not do stuff like this, and a startup's goal tends not to really be to build open source software for everyone to use anyways, so I'm not surprised something like this might exist.

Note, however, that this MIT licensed code includes https://github.com/Viveckh/Veniqa/blob/develop/website/js/is..., which is dual licensed under GPLv3 and commercial. There may be other such components as well. So tread carefully if you'd like to use this for anything practical without having to disclose the entirety of your source code.

Summary: Full-stack e-commerce solution, built using MongoDB, Express.js, Vue.js, Node.js, Mongoose ORM, Redis, Sendgrid, Nodemailer (for fallback), Stripe. Repo: https://github.com/Viveckh/Veniqa Thank you for sharing the work, will enjoy studying it!