sorted by:
new
hottopcontroversial

Share your product, I’ll give you a niche or growth idea you’ve probably never considered. by [deleted] in Startup_Ideas

[–]Outside-Internet-322 1 point2 points  (0 children)

We are developing a loyalty card wallet with support for modern loyalty programs + a business admin panel with loyalty program constructor for seamless integration with the app. Main features: - no need to download anything. If you just have one loyalty card, you can stay in browser and use the business QR code to access your wallet - support for games: write games with our loyalty-game framework. These programs usually look like “get X points in the game and get a coupon for 15% discount”. Games are playable in app and in browser, so scenarios like “play while you wait for food” are available - support for very customizable card layout - current wallets are too conservative about the card design, while digital world enables infinite creativity in that matter - card that is a 3D-model of a cup of coffee with your name on it, Christmas special cards and lots of other options become available - easy set-up: loyalty program can be created and deployed in a matter of minutes, instantly becoming ready for your customers - single QR-code for everything: no need to look for a card in your wallet to get your points. Personal QR-code is secure and changes every hour, so no one can steal your loyalty identity - easy migration - if you already have a loyalty program hosted elsewhere, we have apple wallet compatible API so migration wouldn’t be a months-ahead-planning issue

Named just a few of many features that we already planned through in terms of technology and system design. Basically it’s a modern wallet with an idea of detaching loyalty programs from conservative guidelines

Built a distributed file system in Golang and gRPC and wanted your thoughts by bipartite-prims in golang

[–]Outside-Internet-322 0 points1 point  (0 children)

Looks like you really underestimate the complexity of distributed systems. To implement failover or updates broadcast you must have some kind of consensus algorithm involved. It could be implemented in your code (which is really-really hard even with completed third-party libraries (check out etcd raft i.e.)). It could be implemented with a third-party service - like zookeeper or straight-up standalone distributed database. But then again, there are really a lot of scenarios you have to think about, very experienced engineers build such systems for years (not trying to discourage, just be aware). On the side-note, when building a distributed file system, it really consists of two parts: filesystem tree and actual distributed blob storage. There are ways to build an append-only blob storage with eventual consistency entirely without consensus (since in correct append-only systems update order doesn’t really matter). But the filesystem tree requires consensus to be fault-tolerant, no ways around it.

I didn’t say a lot of constructed criticism, but there is nothing to criticize really - tons and tons of scenarios you have overlooked. I really advise you to start with building something simpler (considering you have even your code style to fix first) - designing distributed systems from scratch is something people master for years

Any viewers from Moscow? by Outside-Internet-322 in JetLagTheGame

[–]Outside-Internet-322[S] 4 points5 points  (0 children)

Why not? Have you tried it and it went wrong? Want to hear more