home.social

Search

495 results for “zeab”

  1. I'm so ready for . 😎

    is already a scalable thing for . But this would be take on the concept. Treating the problem, it seems, from sharding single tenant style.

    supabase.com/blog/multigres-vi

  2. I'm so ready for #multigres. 😎

    #neon is already a scalable thing for #postgres. But this would be #Supabase take on the concept. Treating the problem, it seems, from sharding single tenant style.

    supabase.com/blog/multigres-vi

  3. I'm so ready for #multigres. 😎

    #neon is already a scalable thing for #postgres. But this would be #Supabase take on the concept. Treating the problem, it seems, from sharding single tenant style.

    supabase.com/blog/multigres-vi

  4. I'm so ready for #multigres. 😎

    #neon is already a scalable thing for #postgres. But this would be #Supabase take on the concept. Treating the problem, it seems, from sharding single tenant style.

    supabase.com/blog/multigres-vi

  5. Kind of wild gets a description from guides posts.

    Not always should you reach for microservices (read never). 😅 But when your company is knee deep, it does help to have some common way for services. Plus dapr follows erlang patterns. 😎

    aws.amazon.com/blogs/opensourc

  6. It finally clicked. All what , , and are; frontends. 😅

    What it means is you can achieve essentially the same on any them.

    The question is more how much you willing to delve into the frontend. To do the features of the others. 🤔

  7. It finally clicked. All what #docker, #dagger, and #buildpack are; #buildkit frontends. 😅

    What it means is you can achieve essentially the same on any them.

    The question is more how much you willing to delve into the frontend. To do the features of the others. 🤔

  8. It finally clicked. All what #docker, #dagger, and #buildpack are; #buildkit frontends. 😅

    What it means is you can achieve essentially the same on any them.

    The question is more how much you willing to delve into the frontend. To do the features of the others. 🤔

  9. It finally clicked. All what #docker, #dagger, and #buildpack are; #buildkit frontends. 😅

    What it means is you can achieve essentially the same on any them.

    The question is more how much you willing to delve into the frontend. To do the features of the others. 🤔

  10. It finally clicked. All what #docker, #dagger, and #buildpack are; #buildkit frontends. 😅

    What it means is you can achieve essentially the same on any them.

    The question is more how much you willing to delve into the frontend. To do the features of the others. 🤔

  11. And continues to be my everything analytics thing. 😅 simply cements this. Basically use , , or . 😏

    If I need more, I have to think REAL hard what I can't accomplish with sharding. 😁

    duckdb.org/2025/05/27/ducklake

  12. Can't say I'm surprised, but is shutting down .

    The service was really good in the early years. But have degraded pretty badly. 🙃

    Enough so, I moved and never looked back. I use now and it has been an outstanding upgrade. 😅

    blog.mozilla.org/en/mozilla/bu

  13. now does compaction. Using s3 condition writes. 😎

    is good, but complex when not in infra. Especially for . Too many moving parts. 😅

    Very happy litestream is getting some love. Makes even more of a no brainer choice. 😏
    fly.io/blog/litestream-revampe

  14. #Litestream now does compaction. Using s3 condition writes. 😎

    #consul is good, but complex when not in infra. Especially for #litefs. Too many moving parts. 😅

    Very happy litestream is getting some love. Makes #sqlite even more of a no brainer choice. 😏
    fly.io/blog/litestream-revampe

  15. #Litestream now does compaction. Using s3 condition writes. 😎

    #consul is good, but complex when not in infra. Especially for #litefs. Too many moving parts. 😅

    Very happy litestream is getting some love. Makes #sqlite even more of a no brainer choice. 😏
    fly.io/blog/litestream-revampe

  16. #Litestream now does compaction. Using s3 condition writes. 😎

    #consul is good, but complex when not in infra. Especially for #litefs. Too many moving parts. 😅

    Very happy litestream is getting some love. Makes #sqlite even more of a no brainer choice. 😏
    fly.io/blog/litestream-revampe

  17. #Litestream now does compaction. Using s3 condition writes. 😎

    #consul is good, but complex when not in infra. Especially for #litefs. Too many moving parts. 😅

    Very happy litestream is getting some love. Makes #sqlite even more of a no brainer choice. 😏
    fly.io/blog/litestream-revampe

  18. Do you write anything with and ? Use !!

    This thing is incredible. You can effectively build out functioning logic extensions with the design pattern you have. 🤯 You'll still likely want to clean up some of it to go your coding style, but still. Feels like the future. 😎

  19. Interesting read on why instead of .

    At the scale of Uber, there's real need for optimizing storage engine. Something that we can't do well with postgres. We are getting much better at it with , but not as swapable as mysql. 😅

    medium.com/databases-in-simple

  20. Interesting read on why #mysql instead of #postgres.

    At the scale of Uber, there's real need for optimizing storage engine. Something that we can't do well with postgres. We are getting much better at it with #orioledb, but not as swapable as mysql. 😅

    medium.com/databases-in-simple

  21. Interesting read on why #mysql instead of #postgres.

    At the scale of Uber, there's real need for optimizing storage engine. Something that we can't do well with postgres. We are getting much better at it with #orioledb, but not as swapable as mysql. 😅

    medium.com/databases-in-simple

  22. Interesting read on why #mysql instead of #postgres.

    At the scale of Uber, there's real need for optimizing storage engine. Something that we can't do well with postgres. We are getting much better at it with #orioledb, but not as swapable as mysql. 😅

    medium.com/databases-in-simple

  23. Interesting read on why #mysql instead of #postgres.

    At the scale of Uber, there's real need for optimizing storage engine. Something that we can't do well with postgres. We are getting much better at it with #orioledb, but not as swapable as mysql. 😅

    medium.com/databases-in-simple

  24. I did not know you can do auto image uploads in . Such a brilliant editor. 😎 I'm going to have to dive into it more. Been using it for years and didn't know any of this. 😅

    jonsully.net/blog/automatic-im

  25. I did not know you can do auto image uploads in #typora. Such a brilliant #markdown editor. 😎 I'm going to have to dive into it more. Been using it for years and didn't know any of this. 😅

    jonsully.net/blog/automatic-im

  26. I did not know you can do auto image uploads in #typora. Such a brilliant #markdown editor. 😎 I'm going to have to dive into it more. Been using it for years and didn't know any of this. 😅

    jonsully.net/blog/automatic-im

  27. I did not know you can do auto image uploads in #typora. Such a brilliant #markdown editor. 😎 I'm going to have to dive into it more. Been using it for years and didn't know any of this. 😅

    jonsully.net/blog/automatic-im

  28. I did not know you can do auto image uploads in #typora. Such a brilliant #markdown editor. 😎 I'm going to have to dive into it more. Been using it for years and didn't know any of this. 😅

    jonsully.net/blog/automatic-im

  29. Really like seeing observability teols making easier.

    is pretty nice. Even nicer now with the auto dashboards and insights. 😅

    You make app, they give magic visibility immediately. How it should be. 😎

    honeybadger.io/blog/elixir-per

  30. Nice. Things calmed down and isn't pursuing anymore pulling away. It was a terrible move to begin with. 🫠 They really should have made their own proprietary fork and that would be completely in their rights to do so. 😅

    prnewswire.com/news-releases/c