Taocarts跨境

Posted on

Jun 24

Disassemble the technical architecture of a cross-border e-commerce SaaS system and discuss the engineering practices behind reverse purchasing

After the rise of reverse overseas online shopping in the past two years, there have been a lot more purchasing SaaS systems on the market. I have been running a cross-border independent website for almost three years, and I have tried several systems before and after, and also adopted some open-source solutions for customization.

Recently, I have spent some time studying the overall architecture design of Taocarts system and would like to share some insights from a developer's perspective.

First, let's discuss where the core difficulties of this type of system lie. Cross-border e-commerce systems differ from ordinary e-commerce systems - they are not only about product display and order placement.

What's more troublesome is the "cross-border" aspect: multi-platform product collection, automatic translation, multi-currency settlement, and cross-border logistics tracking. If we build these functions from scratch, just writing the collection crawlers alone could drain the team's resources.

Taocarts has implemented a relatively clear module decomposition in its architecture. The product collection layer has a separate set of plug-in mechanisms to interface with product data from Taobao, JD.com, 1688, and Pinduoduo.

Each platform forms a separate connector, with data standardization achieved through a unified API gateway. The advantage of this approach is that adding new platforms later will not affect the core business code; it suffices to modify the connector.

The order processing flow adopts an event-driven design. From the moment a user places an order, the system breaks down the order into several status nodes: pending review, in procurement, in stock, in packaging, and shipped.

Every state change of a node will push an event to the message queue, which will be consumed by downstream logistics and notification modules respectively. This approach is much cleaner than directly writing a bunch of if-else statements in the controller.

What I find most interesting is its implementation of a "shadow inventory" mechanism. Essentially, it maintains a snapshot layer in the local database, so the upstream platform (such as 1688) does not frequently poll for product inventory updates.

When users browse products, they are reading data from the snapshot layer, and only when they place an order is a real-time verification triggered. This design strikes a good balance between concurrency and real-time performance.

The multi-tenant data isolation adopts a "database-per-tenant" solution. Each settled purchasing agent has an independent database instance, with consistent schema structure but completely physically isolated data.

The cost is increased operational complexity, but the benefit is sufficiently high data security, ensuring that SQL misoperations by one tenant do not affect others.

From the perspective of technology selection, the backend should be the classic combination of PHP (Laravel) + MySQL, while Vue is used for the frontend as a single-page application (SPA). It's not a particularly radical technology stack, but in the field of cross-border e-commerce, stability is more important than chasing the latest trends.

The overall code organization is relatively clear, and the comment coverage is decent, giving the impression that it is not a rushed deliverable.

Of course, it's not perfect. For instance, I estimate that the coverage rate of automated testing is not high, and there is still room for improvement in the documentation.

But for teams aiming to quickly launch a purchasing service, having this set of tools can indeed save at least three to four months of development time.

If you are also working on cross-border-related projects, you can find some inspiration from its modular design. After all, the idea of combining the challenging issues of multi-platform data collection, order processing, and multi-tenant isolation into a SaaS solution is worth pondering.

Top comments

(0)

Subscribe

Personal

Trusted User

Create template

Templates let you quickly answer FAQs or store snippets for re-use.

Submit

Preview

Dismiss

Code of Conduct

•

Report abuse

Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's

permalink

.

Hide child comments as well

Confirm

For further actions, you may consider blocking this person and/or

reporting abuse