![]() So there’s this different dynamic when you write applications with an embedded database, and I kind of miss the sequel side and a lot of that nice management stuff… So SQLite seemed a good middle ground between a raw key-value store embedded database that I had, and a giant Postgres server. Whereas when you have the connection to a query, to Postgres, if you’re even in the same region, in AWS, it can be a full millisecond to do a round trip for a single query. And there’s a stark difference between writing with an embedded database, where everything is super-snappy, because all of your data is just nanoseconds away from you. ![]() I wrote a library called BoltDB in the Go community it’s pretty popular. It’s a super-advanced database, it has all kinds of features, but most of the applications I write have a tiny fraction of the potential of Postgres… And I really love – I used to work in embedded databases a lot. And I don’t have anything against Postgres. Obviously, state sucks, but you’ve got to deal with it, and minimizing that pain is the idea. And that’s my goal too, is I want to make it so that the storage stuff is as invisible as possible. Storage and state are always the most painful thing to deal with, and if they could just make it super-simple for people to ignore that more or less, that’d be great. They just kept coming up in conversations, and then we just chatting with them, we’ve realized we were going down the same road, where they want to build compute and just make it really easy to run stuff, and they don’t want to have to worry about storage. So I started going down that road, and I just kept finding that – you know, I wanted to find a place where I could deploy out applications easily, but also have persistent disks basically like Heroku, but with persistent disks… And everyone kept recommending Fly. ![]() So I have a project called Litestream, where it basically does replication of SQLite databases, and it puts them up to S3, so you can run a single node safely… Because most small projects I have tend to be real small, or medium size, and they don’t get hundreds of requests per second that are writing in, in the tens of requests, or less requests. Deploy your apps instantly and monitor their state - get minimum overhead, maximum impact, and enterprise readiness from day one. The platform is a versatile Kubernetes operator for handling cluster deployments the GitOps way. They’re inviting our listeners to join the closed beta at akuity.io/changelog. See how other teams are using this awesome feature at /code-insightsĪkuity – Akuity is a new platform (founded by Argo co-creators) that brings fully-managed Argo CD and enterprise services to the cloud or on premise. Sourcegraph recently launched Code Insights - now you can track what really matters to you and your team in your codebase. Sourcegraph – Transform your code into a queryable database to create customizable visual dashboards in seconds. Small teams up to 10 people can get started for free with all FireHydrant features included. FireHydrant gives teams the tools to maintain service catalogs, respond to incidents, communicate through status pages, and learn with retrospectives. Incidents impact everyone, not just SREs. Use the code SHIPIT and get the team plan free for three months.įireHydrant – The reliability platform for every developer. From error tracking to performance monitoring, Sentry helps teams see what actually matters, resolve problems quicker, and learn continuously about their applications - from the frontend to the backend. Sentry – Working code means happy customers.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |