MockMotor
Vladimir Dyuzhev
MockMotor Creator
Why MockMotor Doesn’t Support DB Backends?
DBs protocols are proprietary, and it's impossible to cover them all
Some other mock tools try to support all possible connections to backend applications. Databases. Distributed caches. Messaging systems.
MockMotor only focuses on HTTP-based protocols.
Why?
After all, an application can have a few API dependencies, a database or two, and a queue.
Can’t MockMotor support them all, and thus ensure the mock accounts are in sync with, say, an Oracle DB?
Not going to happen.
Unlike APIs, every DB has its own native protocol. An attempt to mock even one of them is an insurmountable task. That’s why even the best-funded service virtualization companies support only a very limited subset of the existing databases.
I elect instead to focus deeply on HTTP-based protocols.
Besides, the modern fashion is that an application - a microservice - should not connect to external databases. Instead, it may have its own private database (which we don’t need to mock) and retrieve all the external data via APIs.
This fashion may revert, but until then, MockMotor is an API-only tool.
AI created no part of this text. It isn't the Butlerian Jihad, but it is something anyone could do.