# technology stack Published articles for technology stack. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## The 9 best tools for your early-stage startup tech stack in 2026 DevFeed: [The 9 best tools for your early-stage startup tech stack in 2026]() Original publisher: [Read original article]() Author: Alan McGlinchey Published: 2026-08-04T08:00:51Z Content type: article Language: en Sources: [The Intercom Blog]() Topics: [Software](), [Artificial Intelligence](), [migration](), [Claude](), [systems](), [Claude Code]() Tags: [ai](), [ai-tools](), [aws](), [best-practices](), [claude-code](), [code](), [customer-engagement](), [fin](), [growth](), [how-to](), [hubspot](), [integrations](), [migration](), [partner](), [pricing](), [startup](), [startup-advice](), [startups](), [stripe](), [tech](), [tech-stack](), [technology-stack](), [tools]() ### AI overview A guide to choosing a foundational technology stack for early-stage startups, emphasizing scalable, AI-powered tools, manageable costs, integrations, and problem-focused selection. ### Source excerpt Learn how to create a foundational tech stack for your high growth and early-stage startup - starting with these top tools. ## Issued - Small, Fast, Self-Hosted Comic Library Server DevFeed: [Issued - Small, Fast, Self-Hosted Comic Library Server]() Original publisher: [Read original article]() Author: Metalogico Published: 2026-05-10T16:52:11Z Content type: article Language: en Sources: [Noted]() Topics: [servers](), [FastAPI](), [Python](), [htmx](), [Tailwind CSS](), [App](), [browser](), [.NET]() Tags: [app](), [browser](), [htmx](), [performance](), [python](), [self-hosted](), [self-hosted-media-streaming-audio-streaming](), [server](), [tailwind](), [technology-stack]() ### AI overview Issued is a small, self-hosted comic library server built with Python, FastAPI, Tailwind and HTMX. It scans CBZ and CBR files while preserving existing folder structures, provides browser and OPDS-compatible reading, and emphasizes lightweight performance for large collections. ### Source excerpt Issued is a personal comic library server built for a simple, focused reading experience. ## Keeping it boring: the incident.io technology stack DevFeed: [Keeping it boring: the incident.io technology stack]() Original publisher: [Read original article]() Author: Matthew Barrington Published: 2026-02-26T15:28:47Z Content type: article Language: en Sources: [The incident.io Blog]() Topics: [Cloud](), [Kubernetes](), [Containers](), [Google](), [cloud-infrastructure](), [configuration](), [observability](), [Processes]() Tags: [cloud](), [configuration](), [containers](), [customers](), [gcp](), [google-cloud](), [incident](), [incident-channel](), [incident-management](), [incident-response](), [kubernetes](), [observability](), [outage](), [platform](), [post-mortem](), [processes](), [slack-incident](), [software](), [technology-stack](), [virtual-machines]() ### AI overview incident.io describes an intentionally simple technology stack built around managed Google Cloud services and a small platform team. Its default compute environment is GKE Autopilot, while workloads with long-lived processes or substantial storage or resource needs run on Google Compute Engine virtual machines. The article discusses the operational trade-offs of managed Kubernetes, including limitations around node lifetimes, system namespaces, and DNS configuration, and explains the use of Cloud Init for immutable, short-lived hosts. ### Source excerpt This is the story of how incident.io keeps its technology stack intentionally boring, scaling to thousands of customers with a lean platform team by relying on managed GCP services and a small set of well-chosen tools. ## A Happy New Employee DevFeed: [A Happy New Employee]() Original publisher: [Read original article]() Published: 2020-02-07T00:00:00Z Content type: article Language: en Sources: [SoundCloud Backstage Blog]() Topics: [engineering-culture](), [Microservices](), [Cloud Native Ecosystem](), [site-reliability-engineering](), [Tooling](), [Frameworks](), [Back end](), [Front end]() Tags: [backend](), [culture](), [engineering](), [engineering-culture](), [frameworks](), [frontend](), [infrastructure](), [microservices](), [onboarding](), [sre](), [technology-stack](), [tooling]() ### AI overview An iOS engineer describes the first six months at SoundCloud, focusing on engineering practices that made onboarding easier. Supportive culture, self-service exploration of code, documentation, and infrastructure, plus shared frameworks and scripts, helped the engineer learn quickly and contribute across many repositories and services. ### Source excerpt My first six months at SoundCloud as an iOS engineer on the Recommendations team have just finished. In that time, I've already contributed... ## The Web is (finally) a mature platform DevFeed: [The Web is (finally) a mature platform]() Original publisher: [Read original article]() Published: 2016-03-19T00:00:00Z Content type: opinion Language: en Sources: [Adam Bard]() Topics: [Web](), [MEAN](), [web applications](), [LAMP](), [Web Development](), [Node.js](), [PHP]() Tags: [angular](), [applications](), [backend](), [css](), [express](), [html](), [javascript](), [lamp](), [linux](), [mongodb](), [mysql](), [node-js](), [platform](), [technology-stack](), [web]() ### AI overview The article argues that the web has become a mature platform with many established ways to build applications. It contrasts the historically dominant LAMP stack with MEAN and contends that MEAN is a reasonable but not uniquely exceptional technology stack. ### Source excerpt I started my career as a "web developer" circa 2007. I'd dabbled before with Javascript while making sites in HTML/CSS as early as middle school, but that was my first real job as a real software developer. Back in those days, LAMP (Linux/Apache/MySQL/PHP) was about the only sensible way to build a web application. You could use Java servlets, of course, or build applications using CGI, but once PHP was stable and available and straightforward, and it quickly became the obvious choice for a huge range of applications. ## Why FINN.no adopted Node.js and npm for front-end development DevFeed: [Why FINN.no adopted Node.js and npm for front-end development]() Original publisher: [Read original article]() Author: espen Published: 2013-12-03T10:38:00Z Content type: opinion Language: en Sources: [Finn.no]() Topics: [npm](), [Front end](), [front-end-development](), [Development]() Tags: [front-end](), [front-end-development](), [maven](), [npm](), [technology-stack]() ### AI overview FINN.no describes its transition from Java-only front-end tooling to a Node.js and npm-based toolset, motivated by the Node ecosystem and its available modules. The article also discusses using Karma and frontend-maven-plugin to integrate Node projects into existing Java projects, and supporting npm through its scale campaign. ### Source excerpt What? Why is FINN.no donating to scale NPM? I thought you guys were a pure Java shop? It is true, we used to be a pure Java-shop. However over the past three years we have adopted new technologies to solve specific problems. We have used Ruby and Cucumber for some time to make a platform for continuos delivery and it has worked out beautifully! Our front-end developers have been forced to deal with out dated and not suitable tools for doing their job. This is largely due to the fact that all innovation when it comes to front-end development does not happen in the Java community. Most of the exciting tools are written in Node and this has become a frustration and a challenge for us. In the past year FINN have been gradually making a transition away from using only Java-based tools for front-end development and towards a NodeJS powered tool set. We are now at a point were we are on the brink of rolling this out for our projects. Having worked with Node for a while we have learned to appreciate the Node ecosystem which is NPM. Being part of such a vibrant ecosystem of modules makes the transition easier and it also inspires us to become better at giving back. Therefore we are trying to give back to NPM, when we can. When the scale NPM campaign was launched it was obvious that this was something we wanted to be apart of. It is an investment in our own happiness in a sense, as NPM is becoming a very important part for our technology portfolio. Nodeify all the things So were is it that we use Node in our technology stack today? Earlier this year we moved away from JsTestDriver in favor of Karma-runner. This meant that we needed to create a trojan horse containing the goodness of Node/NPM into existing Java projects without causing too many problems for developers with no knowledge of Node. A part of this scheme was the frontend-maven-plugin, which enables us to have control of which Node projects use and allows developers without Node previously installed to build project ## The HackerEarth Data Challenge DevFeed: [The HackerEarth Data Challenge]() Original publisher: [Read original article]() Published: 2013-09-13T00:00:00Z Content type: article Language: en Sources: [HackerEarth]() Topics: [data](), [JSON](), [Database](), [Monitoring](), [Back end](), [servers]() Tags: [api](), [backend](), [code](), [coding](), [data](), [json](), [monitoring](), [server](), [servers](), [technology-stack]() ### AI overview The article announces the HackerEarth Data Challenge, inviting participants to analyze more than 800,000 JSON records collected by monitoring services and stored in a schema-less RethinkDB database. It describes the available servers, tables, access details, and a sample Python-based data-reading workflow. ### Source excerpt 40,000+ programmers use HackerEarth. Everyday, people from all over India and other countries submit code on HackerEarth, solve problems and participate in online coding tests. Our CodeFactory server has processed over 500,000 requests till now. There are different types of challenges running every month. The technology stack consists of multiple servers of different types e.g. search-server, realtime-server, web-server, log-server, etc. running at any time. Over 100,000 lines of code are running to serve your requests, and we deploy a dozen times everyday. And we have been able to achieve that with relatively very high uptime all along. To make this possible, we have written many monitoring services for our backend. The public status page listing few of the services is now publicly available at http://status.hackerearth.com/. To make it even more interesting, we are making the data collected by status monitoring services public. All the data is in JSON format, they are over 800,000 in number, and they are available in a schema-less database - RethinkDB. Are you curious how that data looks like? There might be gold-rush in there, and we invite you to find that gold, to find something interesting out of the data and show what you can do with that in hand. There are umpteen stories to uncover, you just need to dig! ###Data Access The data is available in JSON format in RethinkDB. Following are the details of host, database and table: Endpoint: status-data-challenge.hackerearth.com Port: 80 Database name: careerstack Tables hackerearth_status: for HackerEarth webserver api_status: for HackerEarth API realtime_status: for Realtime server code_checker_status: for CodeChecker server celery_status: for task queue rabbitmq_status: for message queue Web UI: http://status-data-challenge.hackerearth.com:8080/ To get started, you need to install rethinkdb-client drivers on your machine. The query language is very simple and easy to get. You should go through RethinkDB QL for ge ## HackerEarth Technology Stack DevFeed: [HackerEarth Technology Stack]() Original publisher: [Read original article]() Published: 2013-03-20T00:00:00Z Content type: article Language: en Sources: [HackerEarth]() Topics: [Back end](), [Django](), [Open Source](), [Python](), [App](), [Programming](), [Amazon S3]() Tags: [algorithms](), [amazon-s3](), [backend](), [code](), [django](), [open-source](), [python](), [software](), [technology](), [technology-stack]() ### AI overview This article describes HackerEarth's technology stack, centered on a Python/Django backend and extensive use and customization of open-source software. It discusses shared authentication, a generic newsfeed and notification system, user-action polling, modular Django applications, Amazon S3 image delivery, customized search backends, and a code-checker built from scratch. ### Source excerpt Originally posted as Quora answer. This might take a while, so go grab some popcorn. You are going to enjoy this :) At HackerEarth, we deeply believe in open-source. Why not, our roots are in there. We use open-source software, hack it according to our needs and create something amazing out of that. At the same time, we don't fear writing a seemingly complex project from scratch and turn it into beautiful piece of code. And we have done that so many times in a very short span. Our application backend is primarily in Python/Django. We modified django-allauth for some of our custom needs. For example, it allows you to login on all sites - HackerEarth, MyCareerStack, and CodeTable with the same login credentials. We modified the django-threadedcomments for spam control (they can really eat you inside!) and enhanced moderator permissions. We wrote our own generic newsfeed system from scratch which can be plugged with any information schema to generate feeds. For example, the feed that you see on MyCareerStack and the recent submissions that you see on HackerEarth, they all come filtered from the same core engine. This feed engine will form one of the core of the upcoming platform and there are some interesting work being done in there - like faster filtering with advanced algorithms, implementation of relevant feed system, and other exciting stuffs. We wrote a notification engine on top of newsfeed system which generates notifications for you. These are part of MyCareerStack for now but as we integrate everything, they will be core of the whole product. We also wrote a generic poll application which tracks all the actions of a user on any item. For example, upvote/downvote on a question, like/dislike on a tutorial, etc. are all powered and regulated by the same application. These user actions can be easily integrated with any object model e.g. programming problem with small snippets of code. As this application develops, we will make it open-source eventually. We did so