DocRaptor VS Apache Camel

DocRaptor Reviews

1. Alex_E    

   almost 3 years ago
   Cool app

   I've been using it for a while. It's great to create contracts.

   🏁 Competitors: pdfmatrix.com
2. Megan Mahdavi    

   Principal Consultant at Sunreach | almost 3 years ago
   Great app - resolves the limitations of other doc/merge apps

   We wanted an app that would allow for custom branding and layout, the font of our choice, and merge fields across our main SF objects. Previously we used DocGen, which led to a morass of configuration to put fields in exactly the place they needed to be for the tables, as well as a bunch of SOQL queries to manage conditional logic. The VF doc generator can't accommodate the fonts we use in our branding. And so DocRaptor has been the perfect solution.

   Our developer built the contracts, and we went live within weeks with complete branding, flexibility in the data merges (we were able to remove a ton of bad config) and it's easy to manage.

   👍 Pros:    Flexible|Great customer support|Super fast
3. Amaury Bouchard    

   Founder at Rolis | almost 3 years ago
   The best HTML to PDF solution

   I have been using DocRaptor for 6 years, both for my professionnal and personnal projects. After trying several free and/or open source HTML to PDF solutions, I was happy to find this service. It's the most efficient solution, which generates the most accurate PDF documents.

   Since it's a SaaS service, there is nothing to install, no library dependencies nor experimental software that you're not sure it will be supported in the future.

   There is a lot of options and CSS rules to dig in if you want to get PDF files that exactly matches what you want. But the other solutions I tried didn't have these options, and the result was not good enough.

   🏁 Competitors: pdfmatrix.com, SelectPdf, pdflayer, Api2Pdf, PDFCrowd

   👍 Pros:    Simple api|No dependencies|Best pdf result|A lot of options to help you create the pdf you need|Good customer support

   👎 Cons:    A lot of css rules to learn if you want to get the perfect pdf of your dreams... but at least these rules exist!

Apache Camel Reviews

DocRaptor mentions (4)

• Launch HN: Onedoc (YC W24) – A better way to create PDFs

  It sounds like this is as advanced as DocRaptor[1]. They have what I consider to be the best PDF generation API, giving complete control over the documents you need to create. The pricing is similar. If you'd rather do it for free weasyprint[2] is the best open source alternative. Another more affordable option you might want to consider is Urlbox[3]. (Disclosure: I work on this) Urlbox's rendering engine is based... - Source: Hacker News / about 2 months ago

• How do you generate PDF reports from HTML?

  We built the DocRaptor API to let developers have affordable access to the commercial Prince PDF engine. We have Node code examples throughout the documentation. Source: over 1 year ago

• What is the best online HTML to PDF converter?

  I'd argue our service, DocRaptor, is the best because it's the only one powered by the Prince PDF engine. Unlike open-source, browser-based conversion engines, Prince was custom-built just for converting HTML into PDFs and offers a lot of unique functionality for making more complex PDFs. Source: almost 2 years ago

• Is it possible to render a RazorPage (inc. CSS) to a PDF file and download via WebAPI?

  I work for https://docraptor.com, which is an HTML to PDF API. We have a C# agent. Source: almost 3 years ago

Apache Camel mentions (12)

• Ask HN: What is the correct way to deal with pipelines?

  "correct" is a value judgement that depends on lots of different things. Only you can decide which tool is correct. Here are some ideas: - https://camel.apache.org/ - https://www.windmill.dev/ Your idea about a queue (in redis, or postgres, or sqlite, etc) is also totally valid. These off-the-shelf tools I listed probably wouldn't give you a huge advantage IMO. - Source: Hacker News / 8 months ago

• Why messaging is much better than REST for inter-microservice communications

  This reminds me more of Apache Camel[0] than other things it's being compared to. > The process initiator puts a message on a queue, and another processor picks that up (probably on a different service, on a different host, and in different code base) - does some processing, and puts its (intermediate) result on another queue This is almost exactly the definition of message routing (ie: Camel). I'm a bit doubtful... - Source: Hacker News / about 1 year ago

• Can I continuously write to a CSV file with a python script while a Java application is continuously reading from it?

  Since you're writing a Java app to consume this, I highly recommend Apache Camel to do the consuming of messages for it. You can trivially aim it at file systems, message queues, databases, web services and all manner of other sources to grab your data for you, and you can change your mind about what that source is, without having to rewrite most of your client code. Source: over 1 year ago

• S3 to S3 transform

  For a simple sequential Pipeline, my goto would be Apache Camel. As soon as you want complexity its either Apache Nifi or a micro service architecture. Source: over 1 year ago

• 🗞️ We have just released our JBang! catalog 🛍️

  🐪 Apache Camel : Camel JBang, A JBang-based Camel app for easily running Camel routes. - Source: dev.to / over 1 year ago