Microservices using mutliple languages (as with Babylon's tower) for a fake e-commerce
It's managed with a Github Project (beta) to keep track of all of the repositories, [Microservices] Babylon E-Commerce.
I wanted to try out the microservices architecture, and, while doing so, try out and learni different languages and stacks. I wanted to create a project with different services and different languages, not because of maintainability, because it would obviously be something out of hand. But as of a challenge rather.
I've chosed babylon to represent the amount of languages, and I also liked the idea of it's ambicousness, because it could, well likely, be the downfall of this project.
The links and brief explanation of each microservice
- API Gateway - Go(lang) and Gingonic, maybe Janus.
- API Gateway UI - Go(lang) and Gingonic, maybe Janus.
- Carts - PHP (Laravel)
- Catalog - To be defined...
- Comments - To be defined...
- Customers - To be defined...
- Inventory - To be defined...
- Orders - To be defined...
- Payments - To be defined...
- Recommendations - Python + Tensorflow
- Reporting - To be defined...
- Reviews - To be defined...
They're detailed in it's own repository/submodule, so check it out without any problem for the most up-to-date info.
- UI - TypeScript, JavaScript, React (Remix) and Astro
You'll have to clone the repository, but this one, it is a special one. It uses submodules, which are links to other repositories, sort of.
For Git >= 2.13:
git clone --recurse-submodules -j8 git://github.com/jofaval/babylon.git
cd babylon-j8 will allow to download up to 8 submodules at once.
For older Git versions compatibility, this would be the commands:
git clone git://github.com/jofaval/babylon.git
cd babylon
git submodule update --init --recursiveAny specification needed for a given service will be detailed at that specific service.
An explanation about my choices and my reasoning.
As aforementioned, I wanted to try out microservices for the longest, well, that may have been an exaggeration, but they do seem intresting, and something I've never tried, but that makes a ton of sense.
Microservices are now everywhere (almost, so to speak) they're really popular. Not saying it's a good or bad thing. It has it's own pros and cons, clearly stated at the official guide. Not everyone, nor every project fits the microservices pattern, or rather, the pattern doesn't firt the project's or team's requirements and/or needs, which is just fine.
A long question, I've chosen, or at least, it is my idea for now, multirepo. I initially thought of monorepo, because of easeness while looking for the project and exploring it. And it's not something impossible, turborepo it's out there and working just fine, and other solutions made for microservices hosted on a monorepo.
What made me say, let's do multirepo! The fact that, each service should be independant of the other services as much as posible, and they will all have different languages. So, what would be the purpose having a single repository, what could be the scalability of a monorepo (considering I'm not Google nor this is a lifelong project). I'd like to abstract each service with it's own repository, and one repo seems risky to me.
Also, reading different opinions (which there are, and not a clear answer, if something, multirepo seems a little bit more liked), having one repo may contribute to "bad practices" such as sharing common elements. Point of reference.
I'm going to create the least original idea for microservices, simply, because the product for this project it's not going to be it's strongest point, and, I'm learning, I want a starting ground I can base my suppositions around.
That being said, what am I going to do? An E-Commerce!! For real. Sparked by IBM's introduction video to microservices and it's pre-defined structure it provides as an example.
What are Microservices? by IBM Technology
To microservices.io and Chris Richardson
And to IBM's Technology YouTube channel