4 ms·
When I started building out the back-end of my latest project, I realized its only purpose was to persist data to a NoSQL database. I had a small epiphany and d
by pauljaworski 10y ago
When I started building out the back-end of my latest project, I realized its only purpose was to persist data to a NoSQL database. I had a small epiphany and decided I didn't need to build a server at all - I could just use something like Firebase to accomplish that task.
Now that I'm getting deeper into the project, I need to add in features like PDF generation. No problem! I'll use microservices for that. Well, that means I need to build a Docker container, deploy it to AWS ECS, and configure AWS API Gateway to talk to it. None of these things are what I would consider "front-end" dev work.
Back-end is surely changing, and many of the needs can be shifted to the front-end/BaaS platforms, but there's still plenty of work left! I think we'll see the back-end role transition more toward building and maintaining these microservices and possibly the business logic portions of the front-end.
- nol13 10y agoThat's what jsPDF is for.
- pauljaworski 10y agoI've looked at that, but it doesn't fit my use case.
- nol13 10y agoYa I'm currently doing some client side xlsx reading/writing along with jsPDF. It fits my meager needs but no where near as mature as the server side alternatives.
- fermuch 10y agoAn easier approach IMO would be to create an amazon lambda script to process the pdf and make it run when you upload a file to a bucket in amazon s3. It's easy to do and you don't need to mess with anything more than two simple API.
- pauljaworski 10y agoI initially planned on using Lambda for things like this, but in this scenario, it does not seem appropriate. I'm a total noob to Lambda, so correct me if I'm wrong, but I need a system with Qt installed to use my PDF library, and it doesn't seem like I can accomplish that with Lambda.
- deleted 10y ago[deleted]