# service In computing and engineering, a service is a self-contained unit of functionality exposed through a defined interface that accepts inputs and returns outputs. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## How to Migrate a Legacy Monolith Incrementally Without a Big-Bang Rewrite DevFeed: [How to Migrate a Legacy Monolith Incrementally Without a Big-Bang Rewrite]() Original publisher: [Read original article]() Author: Hugo Teijiz Published: 2026-09-17T23:27:03Z Content type: tutorial Language: en Sources: [freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More]() Topics: [Legacy Modernization](), [migration](), [Refactoring](), [Testing](), [Integration testing](), [observability](), [Routing (disambiguation)](), [Transactions](), [TypeScript](), [API](), [service](), [Dependency injection]() Tags: [artificial-intelligence](), [how-to](), [incremental](), [integration-testing](), [legacy](), [legacy-code](), [migrate](), [migration](), [monolith](), [refactoring](), [rewrite](), [routing](), [software-architecture](), [transactions]() ### AI overview A tutorial on migrating a legacy monolith incrementally by moving one business capability at a time. It covers characterization tests, boundaries between legacy and new code, parallel implementations, progressive traffic, observability, rollback paths, data ownership, and removing migrated behavior. ### Source excerpt Large legacy migrations often fail long before the final cutover. The failure usually starts when the migration is framed as a single event. Move the application. Move the database. Move all the users ## Neon launches a production-ready backend suite with Postgres, storage, functions, auth, and AI Gateway DevFeed: [Neon launches a production-ready backend suite with Postgres, storage, functions, auth, and AI Gateway]() Original publisher: [Read original article]() Author: Bryan Clark Published: 2026-09-17T12:00:00Z Content type: release Language: en Sources: [Blog -- Neon Docs]() Topics: [Back end](), [Databases](), [Database](), [service](), [functions](), [gateway](), [deploy](), [autoscaling](), [Provisioning]() Tags: [ai-models](), [autoscaling](), [backend](), [backends](), [ci-cd](), [company](), [database](), [databases](), [deploy](), [functions](), [gateway](), [github](), [product]() ### AI overview Neon announces that its backend suite is generally available for production. The suite combines Lakebase Postgres, Object Storage, Functions, Managed Better Auth, and AI Gateway around a shared architecture designed for developer and coding-agent workflows. ### Source excerpt Neon is now a complete suite of backend primitives built around the database and rooted on the lakebase architecture: Lakebase Postgres, Object Storage, Functions, Managed Better Auth, and AI Gateway. All tools are GA and ready for production. Tell your agent to deploy them. ## Welcoming the Sri Lankan Government to Have I Been Pwned DevFeed: [Welcoming the Sri Lankan Government to Have I Been Pwned]() Original publisher: [Read original article]() Author: Troy Hunt Published: 2026-08-23T06:39:45Z Content type: news Language: en Sources: [Troy Hunt]() Topics: [monitor](), [service](), [data]() Tags: [cyber](), [data](), [data-breaches](), [government](), [have-i-been-pwned](), [monitor](), [public-sector](), [service](), [visibility]() ### AI overview Have I Been Pwned has onboarded Sri Lanka as its 48th government customer for the free HIBP service. Sri Lanka CERT can monitor government domains for exposed accounts and respond to new data breaches. ### Source excerpt Today, we welcome the 48th government onboarded to Have I Been Pwned's free gov service: Sri Lanka. Sri Lanka CERT now has access to monitor Sri Lankan government domains against the data in HIBP, helping identify exposed government accounts and respond when they appear in new data breaches. ## LibreQoS 2.2 is out DevFeed: [LibreQoS 2.2 is out]() Original publisher: [Read original article]() Author: j2sw Published: 2026-08-20T15:11:31Z Content type: release Language: en Sources: [Justin Wilson (j2sw)]() Topics: [changelog](), [Network](), [service](), [browser](), [interface](), [sessions](), [API]() Tags: [2-2](), [api](), [browser](), [changelog](), [improvements](), [interface](), [libreqos](), [network](), [network-engineering-resources](), [service](), [sessions]() ### AI overview This changelog describes LibreQoS 2.2, released on August 18, 2026, and its changes since version 2.1. It covers browser-based installation and setup, visual topology building, subscriber shaping from RADIUS sessions, traffic comparisons, and related improvements to LibreQoS Insight and the paid LibreQoS API. ### Source excerpt LibreQoS 2.2 ChangeLog LibreQoS 2.2: What Changed Since 2.1 LibreQoS 2.2 guides operators from a fresh install through admin creation, interface selection, network preview, and service startup in the browser. Operators can build topology visually, shape subscribers created from RADIUS sessions, and compare queued demand with traffic that actually crossed the wire. This changelog covers ... Read more The post LibreQoS 2.2 is out appeared first on Justin Wilson (j2sw). ## History of SpaceX: The Category-Dominating Commercial Spinoff and the Internalization of Anchor Demand DevFeed: [History of SpaceX: The Category-Dominating Commercial Spinoff and the Internalization of Anchor Demand]() Original publisher: [Read original article]() Author: Brendan Sechter Published: 2026-08-04T09:00:00Z Content type: article Language: en Sources: [Brendan A R Sechter's Development Blog]() Topics: [communications](), [Deployment](), [service]() Tags: [aerospace](), [beta](), [business](), [capacity](), [customer](), [deployment](), [history](), [international](), [launches](), [operational](), [partnership](), [regulatory](), [revenue](), [service](), [spacex](), [subscriber]() ### AI overview This article examines SpaceX's commercial spinoff as the internalization of an anchor customer. It explains how the spinoff consumes the parent's launch output at marginal cost, traces its deployment, service rollout, integration, subscriber and revenue development, direct-to-cell expansion, capital requirements, and regulation, and compares the configuration with other satellite-constellation businesses. ### Source excerpt This article is the eleventh in the History of SpaceX series and the third and last treating the capital-formation legs that the series opener introduced. The category-dominating commercial spinoff concerns the business the venture built on top of its own capability, and the article's organizing claim is that the spinoff is not a diversification into an adjacent market but the internalization of an anchor customer. Where the Anchor Demand article A283 treats a government customer buying launches, this article treats the venture becoming the customer it had previously needed someone else to be. The decisive economic property is not that the spinoff grew large. It is that the spinoff consumes the parent's output at marginal cost while every competitor attempting the same business must pay a market price the parent sets. The article walks the January 2015 announcement and the capacity argument that motivated it, the deployment sequence from the first operational batch of May 2019 through the service beta of 2020 and the commercial rollout of 2021, the vertical integration and the internal transfer price that the whole arrangement turns upon, the coupling between constellation deployment and launch cadence, the subscriber and revenue trajectory across the 2020 through drafting-date period, the direct-to-cell extension beginning with the carrier partnership announced in 2022, the capital intensity and the replenishment obligation that a short-lifetime constellation imposes, and the regulatory position across the Federal Communications Commission, the International Telecommunication Union, and the national regulators whose authorizations the service requires. The article contrasts the configuration against the Iridium and Globalstar precedents, in which comparable constellations were built without a captive launch capability, and against the OneWeb and Kuiper cases, in which competitors attempted the business while buying launch at market. The article closes with an expli ## What Interviewers Listen for in Behavioral Interviews DevFeed: [What Interviewers Listen for in Behavioral Interviews]() Original publisher: [Read original article]() Author: Stephane Moreau Published: 2026-07-19T11:12:27Z Content type: tutorial Language: en Sources: [Blog for Engineering Managers]() Topics: [Job](), [incident](), [service](), [connection pool]() Tags: [connection-pool](), [engineering](), [guide](), [how-to](), [incident](), [influence](), [interviews](), [junior](), [scope](), [service](), [teams]() ### AI overview This article explains how interviewers assess behavioral answers, emphasizing the scope of ambiguity, influence across teams, trade-offs, and whether candidates actively discovered problems. It argues that these signals can distinguish mid-level engineers from Staff-level engineers before the stated outcome. ### Source excerpt What I'm actually listening for when you answer. ## Telegram's Short-Link Domain Was Temporarily Suspended by Montenegro's .me Registry DevFeed: [Telegram's Short-Link Domain Was Temporarily Suspended by Montenegro's .me Registry]() Original publisher: [Read original article]() Published: 2026-07-14T00:00:00Z Content type: article Language: fr Sources: [Blog de Stéphane Bortzmeyer]() Topics: [domain](), [client](), [service]() Tags: [article](), [client](), [dns](), [domain](), [telegram]() ### AI overview Telegram's short-link domain became unavailable after Montenegro's .me registry stopped publishing it in DNS. The article examines the resulting NXDOMAIN responses, resolver caching, and the domain's later reactivation. ### Source excerpt Si vous utilisez le service de messagerie instantanée Telegram, vous avez sans doute vu aujourd'hui 14 juillet 2026, que des services ne marchaient pas, notamment les liens vers des ressources diverses (images, etc). C'est parce que le registre de noms de domaine du Monténégro l'avait décidé. Voyons les détails. ## Weekly Update 511: The limits of services that remove data from brokers DevFeed: [Weekly Update 511: The limits of services that remove data from brokers]() Original publisher: [Read original article]() Author: Troy Hunt Published: 2026-07-08T13:54:46Z Content type: opinion Language: en Sources: [Troy Hunt]() Topics: [data](), [service]() Tags: [data-breaches](), [marketing](), [service](), [update](), [weekly-update]() ### AI overview This weekly commentary discusses data breaches and the limits of services that try to remove personal information from legally operating data brokers. It also criticizes the marketing behind those services and their product-placement outreach. ### Source excerpt How's this for a location?! I mean, last week was nice with Scott in Mallorca, but Marrakech is, well, wow 😮 Anyway, about those data breaches... This week I'm talking about the futility of attempting to remove piss from a pool, yet here we are, with ## Don't forget Google SAS retires June 2027. DevFeed: [Don't forget Google SAS retires June 2027.]() Original publisher: [Read original article]() Author: j2sw Published: 2026-06-23T19:34:33Z Content type: news Language: en Sources: [Justin Wilson (j2sw)]() Topics: [SAS](), [Google](), [Google Cloud Platform (GCP)](), [migration](), [service]() Tags: [2026](), [3ghz](), [cbrs](), [cloud](), [deployments](), [existing](), [google](), [google-cloud](), [migration](), [net-11](), [network-operations](), [operational](), [retirement](), [sas](), [service](), [wireless-networking]() ### AI overview Google Cloud Spectrum Access System (SAS) is being retired. It stopped accepting new customers on June 10, 2026, will remain operational for existing customers during the transition, and is scheduled to shut down on June 10, 2027. ### Source excerpt In case you forgot: RETIREMENT NOTICE Google Cloud Spectrum Access System (SAS) is being retired. Starting June 10, 2026, we are no longer accepting new customers. The service will remain fully operational for existing customers during the transition period and will be shut down on June 10, 2027. Please review the migration steps below for instructions on ... Read more The post Don't forget Google SAS retires June 2027. appeared first on Justin Wilson (j2sw). ## Track customer loyalty points with durable workflows DevFeed: [Track customer loyalty points with durable workflows]() Original publisher: [Read original article]() Author: Cecil Phillip Published: 2026-06-03T00:00:00Z Content type: tutorial Language: en Sources: [Temporal Blog]() Topics: [account](), [business logic](), [Database](), [real-time](), [locking](), [retry](), [service](), [upgrade](), [Mobile]() Tags: [account](), [business-logic](), [customer](), [database](), [locking](), [loyalty](), [loyalty-points](), [mobile](), [process](), [query](), [real-time](), [retry](), [service](), [temporal](), [temporal-concepts](), [upgrades](), [workflows]() ### AI overview This article explains how to track customer loyalty points with durable Entity Workflows in Temporal. Each customer has a persistent workflow that maintains points, tier status, and activity history, while Signals handle accruals, Updates validate redemptions, and Queries read current balances. ### Source excerpt Track loyalty points with durable Entity Workflows in Temporal. See how to handle accruals, tier upgrades, and redemptions for each customer. ## Digitale autonomie: wat kunnen organisaties NU doen DevFeed: [Digitale autonomie: wat kunnen organisaties NU doen]() Original publisher: [Read original article]() Published: 2026-05-21T11:30:00Z Content type: opinion Language: nl Sources: [Bert Hubert's writings]() Topics: [Software as a service](), [cloud-infrastructure](), [data](), [datacenter](), [Server](), [servers](), [Software](), [service]() Tags: [analytics](), [autonomie](), [data](), [datacenters](), [marketing](), [privacy](), [servers](), [service](), [software](), [trackers]() ### AI overview This Dutch opinion article discusses practical steps organizations can take to improve digital autonomy after years of dependence on American big tech. It recommends stopping unnecessary migrations, retaining viable European-hosted systems, consulting internal critics of data transfers, and removing American trackers from websites and apps. ### Source excerpt De zorgen over digitale autonomie nemen toe, en steeds vaker krijg ik van (grote) organisaties de vraag: wat kunnen we NU doen? Nou heb ik wel een lijstje, maar voor we beginnen, besef dat we 15 jaar lang alles naar Amerika hebben geschoffeld. Of, we hebben het uitbesteed, en DIE mensen stuurden het naar Amerika. 15 jaar is een lange tijd, en we zijn niet 1 2 3 weer "in vorm" om de zaken weer anders aan te pakken. ## Re: Dependency Injection vs. Service Locators DevFeed: [Re: Dependency Injection vs. Service Locators]() Original publisher: [Read original article]() Author: Zac Sweers Published: 2026-02-20T05:10:16Z Content type: opinion Language: en Sources: [Zac Sweers]() Topics: [Dependency injection](), [Dagger](), [koin](), [Kotlin](), [service](), [multiplatform]() Tags: [dagger](), [dependency-injection](), [koin](), [kotlin](), [metro](), [service]() ### AI overview The article compares dependency injection frameworks with service locators, focusing on compile-time validation, testing, isolation, generated performance, and the tradeoff of requiring more explicit code. It discusses Metro, Dagger, Hilt, Anvil, kotlin-inject, Koin, and manual dependency injection. ### Source excerpt This is a port of a write-up I did in the Kotlin Lang slack here in response to the question "Dagger vs. Hilt vs. Koin vs. Metro vs. . Serious question: Are there any compelling reasons to switch from Koin to Metro in a ## Designing a hierarchical Authorisation system DevFeed: [Designing a hierarchical Authorisation system]() Original publisher: [Read original article]() Author: Authorisation Published: 2025-09-20T00:00:00Z Content type: tutorial Language: en Sources: [Gaurav Sarma's Blog]() Topics: [Actor](), [object](), [structure](), [service](), [properties]() Tags: [actor](), [apis](), [billing](), [finance](), [object](), [recursion](), [service](), [structure]() ### AI overview This article explains how to design a hierarchical authorization system for Goiter. It contrasts a flat mapping of users, objects, and actions with a hierarchical model in which groups can have multiple parents and inherit rules. The article notes that recursive parent lookup can reduce rule bloat, while assuming a maximum recursion depth of 10. ### Source excerpt . [Designing a Hierarchical Authorisation System](designing-a-hierarchical-authorisation-system-cover... ## Des services de DNS secondaires gratuits DevFeed: [Des services de DNS secondaires gratuits]() Original publisher: [Read original article]() Published: 2024-08-30T00:00:00Z Content type: article Language: fr Sources: [Blog de Stéphane Bortzmeyer]() Topics: [service]() Tags: [cause](), [dns](), [services](), [solutions]() ### AI overview The article explains why DNS zones should use multiple authoritative servers with geographic, network, and organizational diversity. It discusses secondary DNS servers, single points of failure, and free or cooperative options for organizations with limited resources. ### Source excerpt Pour des raisons de robustesse, il est fortement recommandé d'avoir plusieurs serveurs faisant autorité (serveur-dns-faisant-autorite.html) pour une zone DNS. Mais ce n'est pas tout : il faut aussi de la diversité, pour éviter que la même cause ne rende plusieurs serveurs injoignables. Il est donc très souhaitable d'avoir des serveurs secondaires en dehors de son réseau habituel. Si on est une grosse organisation, il existe des offres commerciales pour cela. Et si on est une petite organisation, avec peu de moyens ? Des solutions existent quand même. ## PostmarketOS reports progress integrating systemd DevFeed: [PostmarketOS reports progress integrating systemd]() Original publisher: [Read original article]() Published: 2024-07-24T00:00:00Z Content type: article Language: en Sources: [postmarketOS Blog]() Topics: [systemd](), [boot](), [service](), [Requirements](), [maintenance](), [Repository](), [Pipewire]() Tags: [boot](), [bugs](), [postmarketos](), [repository](), [requirements](), [service](), [systemd](), [update]() ### AI overview The postmarketOS team reports progress integrating systemd, including booting GNOME Shell and KDE Plasma. It is working to manage services through systemd, resolve desktop-environment integration issues, automate package maintenance, and merge the work into the main codebase. ### Source excerpt It's been a bit since our last systemd post, but we've been hard at work, so here's an update! We've made good progress. The basics are in place and we can boot into both GNOME Shell and KDE Plasma. However both DEs start services themselves and don't do so using systemd. We instead want to have all services managed by systemd: this will make it easier to understand and maintain and also for users to modify running services. We've figured out how to disable this autostarting of services on GNOME, but haven't yet found an equivalent with Plasma. If you know a way, please tell us in the tracking issue. A big topic has been figuring out an elegant way to enable services, that is more robust than the post-install and post-upgrade scripts approach we are currently using with OpenRC. With the current approach, either users can't override if they want to have a service enabled or not or we cannot automatically enable a new service that may be needed on upgrade. The latter is needed if for example a UI needs a new daemon to run properly, or when switching from pulseaudio to pipewire, etc. So we've learned a thing or two about our own requirements for this, and have been trying to design a way to do the things using systemd-isms. We are working hard on making the end result more resilient, and it has been quite an adventure so far that has taken us through the depths of systemd's documentation (where we couldn't find much about the integration level) and into tearing apart other distros to see what they do to solve these problems. Now we are pretty close to a solution! The systemd functionality currently lives in a separate branch of pmaports. This being separate from the main codebase means we have to manually keep them in sync and there's extra manual work to build a systemd image. So we're also prioritizing getting the systemd work merged into pmaports' master branch (for which the biggest blocker is the split systemd repository in bpo). With the change to systemd, there ## Deciding Which ICT Tasks to Keep In-House or Outsource DevFeed: [Deciding Which ICT Tasks to Keep In-House or Outsource]() Original publisher: [Read original article]() Published: 2024-03-02T16:30:55Z Content type: opinion Language: en Sources: [Bert Hubert's writings]() Topics: [service](), [Server](), [amazon](), [cloud-infrastructure]() Tags: [amazon](), [autonomy](), [employees](), [management](), [organizations](), [outsourcing](), [servers](), [service]() ### AI overview This opinion article discusses how organizations decide whether to keep ICT tasks in-house or outsource them. It argues that prolonged indecision can lead to the loss of internal expertise and recommends making deliberate decisions while retaining a smaller core ICT team. ### Source excerpt The short version: organizations often hesitate for many years before outsourcing tasks, particularly in the field of ICT (Information and Communication Technology). During those years, valuable ICT employees leave because constantly justifying their own existence is frustrating. In the long run, something will eventually go wrong, making the decision to outsource much easier: "We can't and don't want to do this ourselves anymore." However, by hesitating for so long, you have created the situation yourself. ## Designing software with AI DevFeed: [Designing software with AI]() Original publisher: [Read original article]() Author: Mike Published: 2023-06-14T03:36:00Z Content type: tutorial Language: en Sources: [Dev Details]() Topics: [Artificial Intelligence](), [Software](), [coding](), [App](), [prompt](), [prompting](), [service](), [ChatGPT](), [Code Challenge](), [client]() Tags: [ai](), [analytics](), [application](), [chatgpt](), [coding](), [guide](), [mapping](), [practical](), [prompt](), [prompting](), [real-world](), [service](), [software]() ### AI overview Part 2 of a practical series showing how to use AI as a collaborator when designing software. The article uses a URL shortener as a practical example and demonstrates how ChatGPT 3.5 guides problem-context and use-case discussions, with ChatGPT 4 producing better results in a test run. ### Source excerpt Part 2 of a practical example of using AI for coding ## postmarketOS v22.12 SP1 updates mobile Linux devices, kernels, firmware, and power management DevFeed: [postmarketOS v22.12 SP1 updates mobile Linux devices, kernels, firmware, and power management]() Original publisher: [Read original article]() Published: 2023-02-26T00:00:00Z Content type: release Language: en Sources: [postmarketOS Blog]() Topics: [upgrade](), [Kernel](), [Mobile](), [Pine64](), [changelog](), [Pinephone](), [service](), [boot](), [cpu]() Tags: [boot](), [changelog](), [cpu](), [firmware](), [kernel](), [mobile](), [pine64](), [pinephone](), [postmarketos](), [service](), [upgrade]() ### AI overview postmarketOS v22.12 SP1 updates Phosh and Plasma Mobile, device kernels, U-Boot, ARM trusted firmware, CPU frequency settings, and modem power management across supported phones and tablets. ### Source excerpt With the first service pack for v22.12 you can now reliably take photos of that melting snow chicken/monster in your garden with a Librem 5! Thanks to new Phosh related upgrades, it's also possible to use a bunch of cool widgets on the lockscreen. Enable them in Phosh Mobile Settings, lock your phone and swipe to the left. And there it is, your calendar or emergency contact information or whatever you have configured! And there's more, find the detailed changelog below. Contents New device: Samsung Galaxy Grand Max Phosh: Upgrade Phosh from 0.22.0 to 0.24.0 Upgrade Phoc from 0.21.1 to 0.24.0 Upgrade phosh-mobile-settings 0.21.1 to 0.24.1 Upgrade feedbackd 0.0.1 to 0.0.3 Upgrade feedbackd-device-themes 0_git20220202 to 0.0.3 OnePlus 6: fix no ringtone on incoming call, no sound on SMS (#1928) Plasma Mobile: Upgrade Plasma from 5.26.4 to 5.26.5 Purism Librem5: Upgrade kernel from 6.1.1 to 6.2.0 (!3896) Fix unreliable back camera with millipixels (#1947) Enable MGLRU (!3850) Disable modem power management to make it more reliable (!3902) PINE64 PinePhone & PineTab: Upgrade kernel from 6.1.3 to 6.1.9 (!3858) Fix high CPU consumption (#1901) Upgrade U-Boot from 2022.07 to 2023.01 (!3806) Upgrade arm-trusted-firmware from 2.7.0 to 2.8.0 (!3806) Apply this fix by manually upgrading u-boot or installing from a new image that has SP1 included Enable DRAM frequency stats drivers and governors (!3864) PINE64 PinePhonePro: Upgrade kernel from 6.1.0 to 6.1.10 (!3817) Changed default CPU frequency governor to schedutil (!3719) Replace postmarketos-base dependency on sudo with cmd:sudo (!3721) How to get it Find the most recent images at our download page. Existing users of the v22.12 release will receive this service pack automatically on their next system update. If you read this blog post right after it was published, it may take a bit until binary packages and new images are available. Thanks to everybody who made this possible, especially our amazing community members and ups ## postmarketOS Release: v21.06 Service Pack 1 DevFeed: [postmarketOS Release: v21.06 Service Pack 1]() Original publisher: [Read original article]() Published: 2021-08-04T00:00:00Z Content type: release Language: en Sources: [postmarketOS Blog]() Topics: [service](), [Mobile](), [Kernel](), [Pinephone](), [Bluetooth](), [Firefox]() Tags: [bluetooth](), [devices](), [kernel](), [mobile](), [pinephone](), [postmarketos](), [release](), [suspend](), [upgrade]() ### AI overview postmarketOS released v21.06.1, the first service pack for its stable branch. The update brings tested improvements from the edge channel, including upgrades to Sxmo, postmarketOS Tweaks, Firefox Mobile Config, and the Pinephone kernel, along with Bluetooth MPRIS support, wake-from-suspend alarms, and nftables support across stable kernels and devices. ### Source excerpt The first service pack for the current stable branch has been released, v21.06.1. Service packs bring improvements from the edge channel of postmarketOS to the stable release after they have been thoroughly tested. Changes: Sxmo upgrade to 1.5.0 postmarketOS Tweaks upgrade to 0.7.3 Firefox Mobile Config upgrade to 2.2.0 Pinephone kernel upgrade to 5.12.12 Added Bluetooth MPRIS support for media keys GNOME Clocks can now wake the Pinephone from suspend when alarms trigger All kernels/devices in the stable release support nftables For best stability, the service pack contains tried and tested versions of applications and kernels. Find the most recent images at our download page. Existing users of the v21.06 release will receive the service pack changes on their next system update. Comments Mastodon Lemmy HN ## Digital Guru Books DevFeed: [Digital Guru Books]() Original publisher: [Read original article]() Author: Adam Published: 2021-01-15T00:00:00Z Content type: opinion Language: en Sources: [Shostack & Friends Blog]() Topics: [service](), [digital]() Tags: [books](), [conference](), [service](), [small-business](), [technical]() ### AI overview This commentary highlights Digital Guru Books, run by Rupin Gupta, and asks readers to support the small business as conference bookstore activity changes. The business provides a specialty book service for technical conference attendees, publishers, authors, and event organizers. ### Source excerpt Rupin Gupta runs Digital Guru books. He's one of the nicest people you'll ever meet, a real joy to work with, and he works hard to put books on shelves so that you can discover them. With the conference business changing, Digital Guru needs some help. ## Why I love building developer products DevFeed: [Why I love building developer products]() Original publisher: [Read original article]() Author: Map Published: 2019-03-12T20:55:56Z Content type: opinion Language: en Sources: [Craig Kerstiens]() Topics: [Software](), [coding](), [systems](), [scaling](), [service]() Tags: [developer](), [developer-products](), [opinions](), [philosophies](), [product](), [scaling](), [software](), [systems]() ### AI overview An opinion piece explains why the author enjoys building developer-focused products. It highlights the potential for software and systems to improve life at scale, the challenge of serving skeptical developers, and the author's personal familiarity with developer-product work. ### Source excerpt For much of my career I've been focused on building out developer or data focused products with the customer in some form or fashion being a developer on the other end. I fully realize now that I'm destined to spend the rest of my career in that space, either that or trying my hand at wine making. There are a few things that I personally find rewarding about the space that I've shared with a number of people individually lately and thought I would share more broadly. First, software really is eating the world. Often developers and entrepeurs ask about what they could build that would be a good business. The reality is about anything that has not been modernized to as a service and improved with software could be. We have far less developers in the world than we need to execute on all the ways we could improve products and life. To me what is interesting is the last part of that last sentence. It is not that the market for developers is huge, which I do believe it is. It more that when we automate with systems we can get amazing economies of scale. I know folks that reminisce and talk about how we're more stressed being always connected and such and that in the old days people got out and worked the fields and enjoyed the sun. They also absolutely physically exhausted their bodies in the process. The ability to make life better at scale is an interesting one and often done through systems we develop. The second reason is the challenge and the reward. Developers are notoriously tough critics. If it feels/smells like marketing then they have an allergic reaction, and that is probably because much of it is done poorly. If they experience really positive/great marketing they latch on more than the average person. Most developers are by nature a bit skeptical... for some reason this resonates with me. But, I've found they are the largest/biggest supporters once they're excited about something. Personally I'd rather folks more critical and then have a few diehard fans than a ## Watchub DevFeed: [Watchub]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2016-10-06T00:00:00Z Content type: article Language: en Sources: [Carlos Becker]() Topics: [service](), [Repositories](), [Users]() Tags: [commit](), [email](), [production](), [repositories](), [service](), [users]() ### AI overview Watchub is a service that emails users when people follow or unfollow them or star or unstar their repositories. It runs daily and has sent about 200 emails to about 30 users since its production deployment. ### Source excerpt Watchub is a service that notifies you of people who followed/unfollowed you and starred/unstarred your repositories. ## Apps to Services DevFeed: [Apps to Services]() Original publisher: [Read original article]() Author: Map Published: 2012-04-13T20:55:56Z Content type: opinion Language: en Sources: [Craig Kerstiens]() Topics: [Django](), [Scalability](), [service](), [Architecture & Design](), [web applications](), [Hanami](), [Java](), [.NET]() Tags: [communication](), [django](), [engineering](), [java](), [net](), [python](), [rails](), [scalability](), [services](), [web]() ### AI overview The article argues that Django's reusable app model can become difficult to maintain as applications grow, code bases expand, and releases slow. It proposes decomposing larger applications into smaller services that communicate through defined web contracts or APIs, while acknowledging that monolithic applications can scale. ### Source excerpt Update the talk for this is now viewable on YouTube here When I first came across Django I was an immediate fan. It featured: Good documentation Steady but stable progress Community around apps which encouraged DRY I've been a user off and on depending on my needs for nearly four years since discovering it, and throughout that time all of the above have remained true. However, as I've worked on and encountered more complex applications there's one thing that has time and again broke down for me, which is the Django apps model. It hasn't broken down due to Django only though, I've seen it break down in Ruby (Rails), Java, .Net, take you're pick of language or framework. The breakdown of this model is due to several things: Successful applications grow which mean more complex applications and more developers More complex applications often mean larger code bases Deprecating code is good, but not always easy in large code bases More code means more testing, but slower releases At Heroku one way we often describe the platform to others is "A distributed Unix in the cloud." There may be many reasons for this, but one of which is that we love the Unix approach and philosophy of Small sharp tools. Sticking to that, many of our internal pieces are small individual apps that talk across defined contracts or APIs. Back to Django's app structure... Many people build apps and re-use them and often share them with the world. This is truly great for re-usability, which means you can focus on building key features. However, this does not enable your application to be more maintainable in the future nor does it enable scalability. Yes, you can absolutely scale a monolithic application, but it doesn't mean you should. This doesn't mean the app structure is entirely broken, it just means that it is a partial step to where you should be. The real solution is to build more of these pieces of your greater application as services. A Django app is defined as A web application that does some ## Exploring Runlevels DevFeed: [Exploring Runlevels]() Original publisher: [Read original article]() Published: 2011-07-01T00:00:00Z Content type: tutorial Language: en Sources: [Radek Pazdera]() Topics: [Linux](), [Operating system](), [Processes](), [service](), [execution]() Tags: [linux](), [operating-systems](), [process](), [script](), [service]() ### AI overview A tutorial explaining Linux runlevels as operating-system service configurations. It describes conventional runlevel purposes, how to inspect and change the current runlevel, and how init scripts and symbolic links control service startup, shutdown, and execution order. ### Source excerpt I build software products and write on the Internet. [Next page]()