# paas-solutions Published articles for paas-solutions. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## India's First Instant Print Store DevFeed: [India's First Instant Print Store]() Original publisher: [Read original article]() Author: Jacob Published: 2023-05-22T07:27:07Z Content type: article Language: en Sources: [Grofers]() Topics: [Raspberry Pi](), [Internet of things](), [Microservices](), [Security](), [Automation]() Tags: [automation](), [backend](), [engineering](), [hardware](), [india](), [iot](), [microservices](), [paas-solutions](), [quick-commerce](), [raspberry-pi](), [security](), [software]() ### AI overview This engineering case study describes an instant print delivery service built with Raspberry Pi devices connected to local printers. It explains how the team addressed hardware reliability, privacy and security, automation, issue detection, and service uptime while integrating the store with existing microservices. ### Source excerpt Leveraging IoT to deliver printouts to your doorstep Setting up our Printout Delivery Store has been highly satisfying. At one end is the joy of customers discovering an easy, home-delivered solution for last-minute printouts. But even more enjoyable is the knowledge that we created a nationwide service with only a Raspberry Pi and a seamless print flow that effectively harnesses the power of our instant delivery. But we did face some challenges along the way. Post-launch, our customers started experiencing many consistency issues, which had to be fixed before we could scale this service. These challenges stemmed from fundamental hardware limitations. Combined with a need for data privacy and security, it led to frequent misses. The root causes were silly things, such as printers not connecting to the Internet, going to sleep, running out of paper, etc. Below are ways we tackled them and made the instant print store a success. What did we need to do? We needed to figure out how to tinker with our existing microservices to integrate them with the Print Store. Hence we set aside the following objectives: Automation: Start the print process once the order has cleared its payment without manual intervention. Security: Delete the files as soon as the print is complete. Agile Response System: Build a detection mechanism to act quickly on issues such as paper jams and low toner levels 99.9% Uptime: Have No service downtime whatsoever. Selecting our Hardware -- Slice of Pi We needed inexpensive, IoT-friendly hardware, naturally drawing us to the lean, mean, fruity machine-The Raspberry Pi. The Pi is the epitome of commodity computing. It's cost-effective, energy-efficient, easy to set up, and has a ton of support for peripheral connectivity. With the Raspberry Pi, we can also sandbox and package our services to be deployed remotely nationwide. Our Software ImplementationStore Printing Controller Service This service is the heart of our operation and runs on our Pi Zeros (run ## Deploying an Uberjar to Dokku DevFeed: [Deploying an Uberjar to Dokku]() Original publisher: [Read original article]() Published: 2023-02-23T19:37:36Z Content type: tutorial Language: en Sources: [Ariya Hidayat]() Topics: [Deployment](), [Platform as a Service (PaaS)](), [Self-hosted](), [Containers](), [Java](), [openjdk]() Tags: [adoptium](), [containers](), [deployment](), [java](), [linux](), [openjdk](), [paas-solutions](), [scala](), [self-hosted]() ### AI overview This tutorial explains how to deploy a Java Uberjar to Dokku by sending the packaged artifact directly instead of creating a container image. It covers the required application files, packaging, Dokku application setup, and an OpenJDK 17 base image example using Metabase. ### Source excerpt Dokku is a self-hosted Platform-as-a-Service (PaaS) that offers a compelling alternative to popular PaaS solutions like Heroku. With built-in support for Linux containers, deploying an application on Dokku is straightforward. However, there is a lesser-known deployment method that involves sending a build artifact, such as a JAR package for Java apps, directly to Dokku.