introduce node replicas behind a load balancer), as if we tried to get / update a job, we may not get the same node we originally got. The problem with this however, is that we can't as easily scale horizontally (i.e. Indeed, when we were refactoring `athenapdf`, we considered introducing a message queue for workers to pull work from, and to put back when the work completes. I consider asynchronous processing (in this context) as advantageous in some cases. As a plus, it gave us some confidence that if it works for us, it should work for others (obviously, we have come across cases where Docker behaves differently across platforms). We actually went with Docker for the set up because it simplified dependency management tremendously, and it allowed us to deploy on platforms like Kubernetes, Swarm, and ECS. That's interesting feedback! Thank you :) So you don't need to run a service or make API calls for conversions. We also have a CLI assembly that can support custom JavaScript plugins (e.g. Synchronous API calls (`pdf-bot` appears to be mostly asynchronous, with batch processing, and callbacks)ĥ. retry using the same converter or retry using a different converter)Ĥ. Support for different retry mechanisms (e.g. Instrumentation, and metrics (which `pdf-bot` appears to currently lack)Ģ. With our microservice assembly as well, we are focused heavily on ensuring we have:ġ. wkhtmltopdf, LibreOffice, Weasyprint, etc). With `athenapdf` however, we are moving more, and more towards building a toolkit or rather, framework for other people to construct their own conversion processes (or even microservice).Ĭonsequently, we are working towards general abstractions like fetching, converting, and uploading, that can have different implementations (e.g. But, I may be biased.įor example, `pdf-bot` seems to be tied exclusively to a specific converter, and storage backend. I had a quick look at `pdf-bot`, and though we both rely on the same underlying technology (we are only just moving to headless Chromium we were on Electron before), I believe we have slightly different ambitions with our respective project.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |