WolfOliver

5 ms·

31.
by WolfOliver 4mo ago
Maybe this aligns with the current direction we are moving with AI. The frontend app itself becomes more and more worthless and in the future every frontend is custom made. linkedrecords makes this very possible especially if you combine it
32.
by WolfOliver 4mo ago
That is a very good observation. see a comment below: > One interesting open question now is: It is easy to say how the backend provider would bill the company for its services. It is harder for the app provider (the SPA) to bill their
33.
by WolfOliver 4mo ago
Thank you for pointing it out. Maybe the website does a better job in this then the GitHub repo: https://linkedrecords.com/ But even on the website I guess it could be explained a little bit better. the first question is wh
34.
by WolfOliver 4mo ago
That is true. The load test is now at a scale which supports the app I'm running with it. I also know that the bottleneck is the triblestore which is currently a simple postgresql table with three columns (to put it simply). Now the sy
35.
Show HN: Write SaaS apps where users control where their data is stored(github.com)
70 points by WolfOliver 4mo ago|33 comments
36.
Show HN: Almost all of MonsterWriter's back end is open source(monsterwriter.com)
4 points by WolfOliver 4mo ago|0 comments
37.
by WolfOliver 4mo ago
Thank you for the feedback. It is a personal project and a byproduct of a SaaS I'm running.
38.
Show HN: Write SaaS apps where users control where their data is stored(linkedrecords.com)
6 points by WolfOliver 4mo ago|3 comments
39.
Microservices for the Benefits, Not the Hustle(kiss-and-solid.com)
1 points by WolfOliver 4mo ago|0 comments
40.
Show HN: Graph-Based Firebase Alternative with Real-Time Sync(linkedrecords.com)
3 points by WolfOliver 5mo ago|0 comments
41.
Show HN: Graph-Based Firebase Alternative with Real-Time Sync(linkedrecords.com)
1 points by WolfOliver 5mo ago|0 comments
42.
Write SaaS apps where users control where their data is stored(linkedrecords.com)
2 points by WolfOliver 5mo ago|0 comments
43.
Write SaaS apps where users control where their data is stored(github.com)
2 points by WolfOliver 6mo ago|0 comments
44.
by WolfOliver 6mo ago
This is a quite different approach so its best to keep an open mind when reading it. A little more hands on introduction can be found in the getting started guide: https://linkedrecords.com/getting-started/
45.
Write SaaS apps where users control where their data is stored(linkedrecords.com)
3 points by WolfOliver 6mo ago|1 comments
46.
What if you didn't need to write back end code for your app?(linkedrecords.com)
1 points by WolfOliver 6mo ago|0 comments
47.
What if you didn't need to write back end code for your app?(linkedrecords.com)
3 points by WolfOliver 6mo ago|0 comments
48.
by WolfOliver 6mo ago
Would you be less sceptical if the tutorial would use a publicly hosted instance?
49.
by WolfOliver 6mo ago
You a free to inspect the yaml file which will be passed into the docker compose. Also it is not as dramatic as it looks like as docker compose will just start containers. All the potentially malicious code will be run in containers.
50.
What if you didn't need to write back end code for your app?(linkedrecords.com)
2 points by WolfOliver 6mo ago|3 comments
51.
Authorization as Data, Not Code(monsterwriter.com)
2 points by WolfOliver 6mo ago|0 comments
52.
A back end where you never need migrations or authorization code(monsterwriter.com)
2 points by WolfOliver 6mo ago|0 comments
53.
A back end where you never need migrations or auth code(monsterwriter.com)
1 points by WolfOliver 6mo ago|0 comments
54.
by WolfOliver 6mo ago
for me, using go is the fancy stack
55.
by WolfOliver 6mo ago
20$ vs 300$ does not really matter if you have multiple 10K MRR.
56.
LinkedRecords is now MIT-licensed(github.com)
2 points by WolfOliver 6mo ago|0 comments
57.
Show HN: I stopped designing APIs for my apps(linkedrecords.com)
2 points by WolfOliver 7mo ago|0 comments
58.
Linkedrecords – A fresh take on Backend as a Service (Supabase alternative)(linkedrecords.com)
1 points by WolfOliver 7mo ago|0 comments
59.
Challenging the Single-Responsibility Principle(kiss-and-solid.com)
39 points by WolfOliver 7mo ago|23 comments
60.
Show HN: LinkedRecords – Build SaaS apps like there is no backend(linkedrecords.com)
1 points by WolfOliver 7mo ago|0 comments

More ›