DISCLAIMER: MINTY IS ARCHIVED!
Archived as of 2021-07-29
Here’s why you should care:
Available alternatives are great for their purposes. Minty doesn’t exist to succeed any of these alternatives such as: DataStore2, ProfileService, QuickSave, DiceDataStore, and MANY MORE!
However Minty’s core values are inherently different. Session-locking is amazing, it is the second best-thing to transactions. But in hindsight, that’s not the end of item duplication that can instance from trading. Minty provides a solution. Minty currently runs on the principle of Two Phase Commit Protocol. A pattern to implement synchronous transactions to NoSQL databases. At the moment, it should be your reason to use it!
Minty is for big-production games, it is currently being deployed into a game with a huge codebase, implementing features CAN be detrimental and break things you never expected to break. Which is why Minty is a typescript-first implementation.
Huge games, expect huge data. Minty has auto-sharding, meaning on read it will divide up data into manageable chunks when necessary! Sometimes a dataset is too large to be stored into a single datastore, sharding allows a datastore cluster to scale along with its data and traffic growth!
Finally the last feature worth mentioning is read-replication. Incidents will happen no matter how good the software is! Hence why we use read replicas to copy a primary instance that reflects changes to the primary key in real-time. Read replication lets you offload read request or analytics traffic from the primary easily and Minty provides advanced tooling to let you interface with that data at any moment from anywhere. Example: Hear about an incident regarding a player’s data being corrupted? Simple command through the Minty discord bot can let you rollback its state.
We developers have lives, and Minty exists to help handle data in an easy way but most importantly with safety.
Why Roblox-TS (typescript)
Minty
Roblox-TS.
Roblox-TS aligns with our vision a lot. Typescript is ideal for huge codebases managed by teams but roblox-TS gives us developers confidence that when implementing features that we won’t make some silly mistake.
Available for download?
No. At least not yet. The more users of Minty, our online tooling gets slower. The team behind Minty actively works on setting up server routes to make sure Minty is always available. There’s limited available data and we don’t have the necessary funds to infinitely open more servers and increase the bandwidth.
Hence Minty won’t be free, not anytime soon. With more supporters, there’s a chance we provide a freemium model where the online tooling is available only for premium users. We don’t know but hopefully we get enough support from you guys to know that there is a market in need of Minty
.
Have any questions? Please ask below and I will do my best to answer them.
I have decided to archive Minty for a few reasons.
- As of today, we deployed it in a production project and the company that I worked for has acquired rights to the software, and thus I am no longer the rightful owner of the software and cannot distribute it for open source use.
- Minty tried to become too much, it was a caching library, it was an AI bot, it was Live-Ops, Real-Time Analytics. It grew to an overwhelming size and it honestly became too expensive for myself to maintain.
- I had very unrealistic goals and I poured a lot of time into it, but it turned out second-rate in comparisons to competitors because it wasn’t specialized in one thing.
Although there was a lot of promise for the project, and I felt like I let everyone down, thus I have rewritten the caching library part of the system which I believed to have been the most important part from scratch and renamed it to ‘Prophet’.
Prophet will still feature Minty’s most sought after features, transactions, persistent retries, proper error handling, read replicas for disaster recovery, mutation sentry and more. However this time kept simple in the core and most importantly, will be for everyone’s use for free!



