dozer VS wick

https://github.com/getdozer/dozer/issues/1631#issuecomment-1...

and then something has gone off the rails about the accounting process since

  Trigger.dev

Hi HN,

I'm Matteo and co-founder of Dozer (https://github.com/getdozer/dozer), a backend tool for building data products. Over the past few months we have done good progress with the product development but our documentation needs a lot of work. Myself, my co-founder and the entire team are juggling among many activities, and one of them is producing good documentation, and that is the part where we are bit struggling.

We have tried to hire a couple of tech writers but it's really not working out as we wanted. Our product is a dev product, and it is very hard to find tech writers who have that depth to think what a developer need. At the same time, asking the dev team to write documentation produces low quality docs (obviously devs prefer to write code and they just to go back to that as fast they can).

The result is that I end up writing most of documentation or refactoring the entire content produced by tech writer. But this approach will not scale.

How do you guys solved it? I'm curios to know about the approach of other startups.

Thanks

This blog post explores how to enhance these aspects by implementing a low-latency cache using Dozer and PostgreSQL. We delve into the importance of caching in data management, the limitations of not having a cache, and the unique advantages of using Dozer as a cache layer. We also provide a guide on how to use Dozer for real-time data ingestion from PostgreSQL. This post is a must-read for developers seeking to improve their application's performance and responsiveness, and for those looking to simplify their data infrastructure.

I recently penned a blog post on an interesting topic - leveraging Dozer with PostgreSQL to create a high-speed, low-latency cache. In case you're not familiar with Dozer, it's an open-source data API backend built entirely in Rust, known for its fast processing and lower resource usage.

some time ago I shared about our OSS project Dozer with the group. We just did a presentation and demo at the Python Meetup group here in Singapore and just wanted to share the full video here.

Hey HN,

As one of the co-founders of Dozer (https://github.com/getdozer/dozer), I stumbled upon this awesome article from the Temporal folks (https://temporal.io/blog/saga-pattern-made-easy) and got super excited about the potential synergy between Dozer and Temporal.

While Temporal nails the orchestration of microservices, I couldn't help but notice the challenge of consolidating data across services. In the article, they talk about three services: flight booking, hotel booking, and experience booking. But imagine trying to create a complete trip view by stitching together data from all three services - it can be quite a headache!

And that's where Dozer swoops in to save the day. With Dozer, I can tap into all the change data capture (CDC) events from each microservice, merge the data in real-time, stash it in a cache, and make it available through APIs. The best part? Since Dozer operates in real-time, my cached data is always fresh. Boom! Now I can simply leverage Dozer's APIs to access a comprehensive trip view.

Raise your hand if you've faced this challenge before! Let's hear your thoughts.

👋🏼 Are you looking for a platform that simplifies the process of building and deploying data-driven applications? Look no further than Dozer! 💻 is a powerful Data API backend that simplifies the process of building and deploying data-driven applications & APIs for real-time data processing and analysis, predictive analytics, data caching, and much more. Dozer is a 100% open-source project.

Star our repository and get a chance to win an amazing Swagpack!!🎁🎉 We will announce the winners in our Discord server. So, don’t forget to join.🤗

You can consider using Dozer (https://github.com/getdozer/dozer), an open-source data API backend. Dozer has a PostgreSQL connector that you can use to monitor any changes in your database schema and data. Although Dozer is not specifically designed for ETL tasks, you can still use it for this purpose by using Lambda functions. Dozer provides a Lambda runtime to execute user-defined functions. So you can use PostgreSQL connector ( to capture CDC) with Lambda runtime to load data to snowflake.

Enter Dozer, it simplifies the process of creating low-latency data APIs (gRPC and REST) from any data source easily with OpenAPI specification. Dozer is a real-time data engineering tool built with Rust, which enables seamless integration of data streams(sources), efficient data processing, and lightning-fast response times. This allows developers to focus on building applications without worrying about the complexity of managing real-time data.

> In Wick, we use a script to automatically update inline lint configurations for a few dozen crates.

> https://github.com/candlecorp/wick/blob/28465f8c1492e6588bd2...

Good lord, that is an INCREDIBLE number of lints to disable, and for... what? If you have to disable lints telling you about things like unused/dead code, intentional validation of the language's conventional style, unused/unnecessary allocations, useless/trivial type casts, ... then I really wonder what kind of code is actually being written.

Disclaimer: I work at this company

Candle just released the Candle Cloud (https://cloud.candle.dev) with a generous free tier. This allows for anyone who knows basic SQL to create a backend api application and host the application on the Internet. This is made possible by our framework Wick (https://github.com/candlecorp/wick)

If anyone has any questions or wants any help getting your own idea deployed, I will be watching here or you can join our Discord (https://discord.gg/candle) and we can help you there.

I can't wait to see what you can build!

Hi Everyone

We've been deep-diving into our project, Wick (https://github.com/candlecorp/wick).

The idea? Use Wick to build a low-code request enrichment HTTP proxy, and then harness that same functionality for a CLI app.

For those wary of low-code, we've got you covered. There's a dedicated section showcasing how to employ Rust to craft a WebAssembly component. This ensures you can seamlessly embed any intricate logic into the same workflow.

Keen to hear your thoughts.