home.social

#databasedesign — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #databasedesign, aggregated by home.social.

  1. Most devs think backend = APIs.
    It’s not.
    It’s:
    • Efficient request handling
    • Clean architecture
    • Smart DB design
    • Caching strategies
    • Security
    • Reliability under load
    Great backend ≠ just code
    It’s systems that don’t break in the real world.
    Tools change. Principles don’t.

    jaswalaryan.space/article/back

    #BackendDevelopment #WebDevelopment #APIDesign #SoftwareEngineering #SystemArchitecture #DatabaseDesign #Caching #Security #PerformanceOptimization #DevOps #Scalability #CodeQuality #Programming

  2. Most devs think backend = APIs.
    It’s not.
    It’s:
    • Efficient request handling
    • Clean architecture
    • Smart DB design
    • Caching strategies
    • Security
    • Reliability under load
    Great backend ≠ just code
    It’s systems that don’t break in the real world.
    Tools change. Principles don’t.

    jaswalaryan.space/article/back

    #BackendDevelopment #WebDevelopment #APIDesign #SoftwareEngineering #SystemArchitecture #DatabaseDesign #Caching #Security #PerformanceOptimization #DevOps #Scalability #CodeQuality #Programming

  3. Most devs think backend = APIs.
    It’s not.
    It’s:
    • Efficient request handling
    • Clean architecture
    • Smart DB design
    • Caching strategies
    • Security
    • Reliability under load
    Great backend ≠ just code
    It’s systems that don’t break in the real world.
    Tools change. Principles don’t.

    jaswalaryan.space/article/back

    #BackendDevelopment #WebDevelopment #APIDesign #SoftwareEngineering #SystemArchitecture #DatabaseDesign #Caching #Security #PerformanceOptimization #DevOps #Scalability #CodeQuality #Programming

  4. Most devs think backend = APIs.
    It’s not.
    It’s:
    • Efficient request handling
    • Clean architecture
    • Smart DB design
    • Caching strategies
    • Security
    • Reliability under load
    Great backend ≠ just code
    It’s systems that don’t break in the real world.
    Tools change. Principles don’t.

    jaswalaryan.space/article/back

    #BackendDevelopment #WebDevelopment #APIDesign #SoftwareEngineering #SystemArchitecture #DatabaseDesign #Caching #Security #PerformanceOptimization #DevOps #Scalability #CodeQuality #Programming

  5. 🤡 "Design Me a Highly Resilient Database" is a riveting tale of one man's epic struggle against the dreaded No-Context Interview #Questions 🤔. Spoiler alert: He knows too much, which is apparently a crime in the tech world 🚨.
    nikogura.com/DatabaseDesign.ht #DesignMeAHighlyResilientDatabase #NoContextInterview #TechStruggles #EpicTale #DatabaseDesign #HackerNews #ngated

  6. #CaseStudy - the Man Group moved from managing one of Europe's largest MongoDB clusters to a truly #serverless architecture with #ArcticDB - no more chasing space, no more annoying upgrades - just a software library connecting directly to S3.

    How do you build a high-performance database without a server? Alex Seaton breaks down the hard-won lessons from the transition:
    • Clock drift is real
    • Sometimes you have to redesign from scratch
    • CRDTs are useful but very subtle things

    🎬 Watch the #InfoQ video and dive into the full architecture behind this shift ⇨ bit.ly/3Z9AiwX

    📄 #transcript included

    #DataEngineering #Database #DatabaseDesign #CRDTs #Python

  7. 🎩✨ Behold the mystical "expand and contract pattern" for database schemas! Because who doesn't love a guide that turns simple schema changes into a quest for the Holy Grail? 🏰🔍 Spoiler: it's just another way to say "do it carefully," but with extra steps and a touch of #wizardry. 🧙‍♂️🗃️
    prisma.io/dataguide/types/rela #expandAndContract #databaseSchemas #schemaChanges #databaseDesign #HackerNews #ngated

  8. Ah, yes, because nothing says "cutting-edge tech" like glorified doodles of your databases in the cloud. 🌥️🖍️ A revolutionary step forward for those who find the command line *too challenging* and prefer to squint at screens full of spaghetti diagrams. 🍝👀
    app.chartdb.io #cuttingedgetechnology #cloudcomputing #databasedesign #spaghetti-diagrams #techhumor #HackerNews #ngated

  9. When starting with a new @couchdb #DatabaseDesign, you’ll need to consider document size and attachment size. Get them wrong… and, you’ll feel it later! 📏 💾

    We’ve put together two #DataModelling tips that expand on why we recommend keeping it small.

    Start with our post on attachment size:
    neighbourhood.ie/blog/2025/02/

  10. 🧠 SQL Mindmap & Daily Life SQL Commands for Developers 🧠

    SQL (Structured Query Language) is a powerful tool used by developers to manage and manipulate databases. Whether you're querying data, updating records, or performing complex joins, SQL is essential in daily development tasks. Let’s break it down!

    #SQL #SQLCommands #DatabaseManagement #DevelopersLife #TechSkills #DatabaseDesign

  11. I've been working on this a bit lately, but getting stuck on the database side of the IPAM relationships. Specifically, how to get a one-to-many relationship working between the network (e.g. 192.168.1.0/24) and the IP entries (192.168.1.[1..254]). Pydantic usually complains about the relationship in some form or other, saying it can't generate the schema.

    One thing that definitely doesn't help is that I define the return types in one file and the Pydantic models in another, so any change I make in one I have to make in another.

    For that reason, I might look at replacing how I interface with the database.

    Thankfully, the testing I have in place will let me change things out easily.

    #rackroot #programming #backend #webdev #databasedesign

  12. Gateway stuff is done for now, so it's time to work on the DHCP range data.

    A network can have 0..n DHCP ranges and each DHCP range should be editable with the CRUD operations.

    C - create: add a new DHCP range, make sure it doesn't overlap with another DHCP range already present on this network. All IPs should be in range, too.
    R - read: render DHCP range information and overall IPAM utilization of the network. A DHCP range covering 200 IPs on a /24 should, for example, show roughly 80% of the IPs are used. Vuetify has UI elements to render stuff like this.
    U - update: change data about the range such as the start/end addresses, name, or description.
    D - delete: remove a DHCP range <--> network association and the associated record(s) from the db.

    Validations:
    DHCP range doesn't overlap other IPs in use on the network, such as the gateway, static IP assignments on that network (which I haven't even gotten to), or other DHCP ranges.

    There's going to be a LOT of testing to go into this and I think that's why I like this kind of stuff. It forces me to think of all the use cases, write tests, add code, and balance all of it together.

    #rackroot #programming #networking #fastapi #python #webdev #fullstackdevelopment #fullstack #vuetify #databasedesign

  13. Dive deep into the world of #DataResidency strategies with this insightful #InfoQ article: bit.ly/482LuxB

    Learn effective implementation tips while ensuring a positive experience for all stakeholders.

    #DatabaseDesign #Database #CloudComputing #SoftwareDevelopment