# quick-commerce Published articles for quick-commerce. 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 ## In Focus: Blinkit SRE Engineer Sumanth Reddy on Resilient Software and Scalable Database Migrations DevFeed: [In Focus: Blinkit SRE Engineer Sumanth Reddy on Resilient Software and Scalable Database Migrations]() Original publisher: [Read original article]() Author: Jacob Published: 2023-03-16T03:21:01Z Content type: article Language: en Sources: [Grofers]() Topics: [Resilience](), [SRE](), [DevOps](), [Database]() Tags: [culture](), [database](), [devops](), [engineering](), [people-at-blinkit](), [quick-commerce](), [resilience](), [site-reliability-engineer](), [sre]() ### AI overview An interview with Blinkit SDE 3 Chinthakunta Sumanth Kumar Reddy about his journey, work in Software Resilience Engineering, scalable database migrations, resilient software, and challenges in the instant commerce space. ### Source excerpt A conversation with engineers who help run Blinkit Chinthakunta Sumanth Kumar Reddy is an SDE 3 at Blinkit. He joined us in March 2021 and has since helped us build a resilient application platform at Blinkit. He currently works as a part of Software Resilience Engineering (SRE)-enabling scalable database migrations for Blinkit's applications. Tell us about your background and your journey in Blinkit so far. I have always been curious to learn new things and don't have barriers as long as I can engage with the task. Hailing from a small village in Andhra Pradesh, I have travelled across several cities (Fun fact: My village and family share the same name). I have been working with the SRE team for almost two years. I love the no-nonsense work culture here, which allowed me to raise PR from day 2 in the company. Why did you choose to work in tech? What drove you? Due to my background in the Electronics branch, I have always been fascinated by how the physical transistors click and clack with seemingly intangible software bits. There is a sense of excitement when things spring into action, and I think if there's an equivalent of magic in our world, it will be Tech. What excites you the most about your field? The ability to build resilient software excites me. Imagine seeing a traffic spike and everything scaling up to take the load and winding down when the traffic calms down, all on its own-It's magical, to say the least. While solving a problem, what is the principle you always adhere to? When hit with a problem, take a step back and think through it. Sometimes, it isn't what it appears to be. Problem-solving is all about perspectives. What immediate challenges are we trying to solve in the instant commerce space? Efficiency and localisation. With delivery timelines moving from days to minutes, there is significantly lesser room for errors. Also, since we are nearer to customers, localisation is the key. For example, a top seller in one area might be utterly irreleva ## In Focus: Jay Dihenkar DevFeed: [In Focus: Jay Dihenkar]() Original publisher: [Read original article]() Author: Jacob Published: 2023-02-23T03:01:29Z Content type: opinion Language: en Sources: [Grofers]() Topics: [release engineering](), [SRE](), [CI/CD](), [Resilience](), [Monitoring](), [observability](), [developer-productivity](), [Automation](), [Scalability](), [systems]() Tags: [automation](), [ci-cd](), [culture](), [developer](), [developer-productivity](), [devops](), [monitoring](), [observability](), [people-at-blinkit](), [quick-commerce](), [release-engineering](), [resilience](), [scalability](), [site-reliability-engineer](), [sre](), [systems]() ### AI overview An interview with Blinkit Staff Engineer Jay Dihenkar about his journey from release engineering to site reliability engineering. He discusses CI/CD, developer productivity, production incident debugging, automation, monitoring and alerting, infrastructure costs, application reliability patterns, and challenges in scaling quick-commerce logistics. ### Source excerpt A conversation with engineers who help run Blinkit Jay Dihenkar is a Staff Engineer at Blinkit. He joined us in December 2020 and has helped different teams manage and streamline their build and release processes. He is currently working towards continuously improving the reliability, scalability, observability, developer productivity, and other such aspects of a software system critical for ensuring that the system can meet the needs of its users and stakeholders over time. Tell us something about yourself and your journey in Blinkit so far. I started out as an engineer on the Release Engineering team, working on goals of Software Quality/Stability and streamlining release processes (Continuous Integration/Continuous Deployment or CI/CD). I help make an impact by improving developer productivity while safeguarding the production ecosystem against failures. I later transitioned into the Site Reliability Engineering (SRE) team, where we focused on improving the reliability and resilience of our systems. Being a site-reliability engineer requires one to develop a deep understanding of how the various components of a system work together and how to optimize them. Overall my journey in Blinkit is one of continuous learning and improvement. If you were to describe your experience as a Blinker in one word, what would that be? Growth. Being here is all about continuous learning in a fast-paced environment. What does a typical day at work look like for you? On a typical day, I work on the following domains (though not everything on a single day!): debugging complex problems sprung out of production incidents, putting automation in places where required, setting up monitoring and alerting, as well as responding to alerts, release engineering and developer productivity (CI/CD), System Infrastructure Cost, Working toward implementing Application Reliability Patterns and so on... What are the biggest challenges facing quick commerce today? I believe the "Logistics infrastructure"