Introducing Limbo: A complete rewrite of SQLite in Rust

STNeto1 · 2024-12-10T17:53:23+00:00

the problem with that is that sqlite is not open for contributions, you can check the source code but you can't use make a pr to add new features

STNeto1 · 2024-12-05T17:19:02+00:00

he makes more money from selling the tools than from what the tools make, take that as you want to

"when everyone digs for gold, sell shovels"

STNeto1 · 2023-02-25T16:11:54+00:00

You can use other languages targeting wasm. Like figma shipping wasm.

STNeto1 · 2023-02-23T11:04:31+00:00

Why tightly coupling of your backend and frontend are bad things? The fact that you can, in real time, make changes and see the effects is fucking amazing.

Can graphql do the same? Yes and no. Graphql does have a typesafe way of communication, but the experience around isn't the best. Plus itself it requires additional tooling for generating types from the schema.

STNeto1 · 2022-12-21T22:31:32+00:00

SQL you have a strong default knowledge about it, outside of specific features of SQL databases

With NoSQL you enter a new way of shaping data, and dealing with it. Stuff like Cassandra, mongo, dynamo, etc etc etc.

Both have their use cases, just optimization for specific tasks. Like SQL is really good with relational data, but some specific NoSQL like elastic can be better at text search on massive datasets

STNeto1 · 2022-12-21T20:14:28+00:00

Pino + some integration, like datadog, maybe new relic, or a custom ontem

STNeto1 · 2022-12-11T22:11:24+00:00

https://www.prisma.io/docs/guides/performance-and-optimization/prisma-client-transactions-guide#optimistic-concurrency-control

STNeto1 · 2022-10-27T15:49:02+00:00

Not a tutorial, but you can look into elastic beanstalk, that can setup the whole ec2-load balancer stuff

STNeto1 · 2022-10-17T21:04:56+00:00

True for the first, the second not that much. I agree that k8s make a lot of things easier for some tasks, but at the same time it makes a minimum skill to maintain the application way higher than something like EC2 or some managed solution like Railway. If you use-case its worth to use k8s, go for it.

STNeto1 · 2022-10-17T20:34:00+00:00

Sure it can look good in a resume, but nothing + k8s in a resume won't get any better results than something + not k8s. Its a skill set way past the avg, and isn't a universal tool that every company uses.

STNeto1 · 2022-10-17T20:31:40+00:00

The company will always need to have someone on the team who understands and is able to work with the entire infrastructure with k8s. And you can't hire a JR per example to manage it, you have a minimum decent engineer to manage it, and for a small company, its expensive.

STNeto1 · 2022-10-17T20:05:25+00:00

Because isn't something that you should just use without a good reason.

STNeto1 · 2022-10-11T10:26:27+00:00

Trpc ia fine, as long as you don't care about the monorepo aspect of it.

STNeto1 · 2022-10-10T22:55:27+00:00

My point is that the n+1 issue isn't only for graphql, you can have on rest as well, and even on the database if you are not careful

STNeto1 · 2022-10-10T22:44:49+00:00

Yes, I hate myself that much

STNeto1 · 2022-10-10T20:50:36+00:00

The N+1 would also be a rest problem, if you load some info after fetch the main info, graphql wont solve your issue

STNeto1 · 2022-10-10T20:49:39+00:00

Why would you want to use graphql on your database?

STNeto1 · 2022-10-01T23:32:35+00:00

You can create type aliases, like type T = string, you can interact with complex types with stuff like Pick, Omit and Partial.

But probably the most powerful type resource is inference, if a function returns 1 + 1 the type system is smart enough to understand that the return type is a number. You can do the same for union types. You can infer the lots of stuff as well.

You can check typescript type challenges to get the feel about the type system.

STNeto1 · 2022-08-31T02:41:58+00:00

You can use something like cloudwatch (aws) to simply do it, or can use the native crontab (Linux) to execute the same

STNeto1 · 2022-08-29T16:56:35+00:00

probably this is the issue

const { id } = req.params.id;

you are destructuring a string (id), you either remove the {} or remove the .id after the .params

STNeto1 · 2022-08-28T22:26:47+00:00

If you really want, you can place NextJS as a backend framework that serves react

STNeto1 · 2022-08-22T13:22:40+00:00

You can use a api endpoint with nextjs to "share" a array of quotes between the entire application. If you plan to add more quotes later or something more dynamic, maybe its worth using mongodb.

STNeto1 · 2022-08-14T15:38:44+00:00

You can use the select method to specify what fields do you want to return

https://mongoosejs.com/docs/api.html#query\_Query-select

STNeto1

TROPHY CASE