[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/tech/ - Technical SEO

Site architecture, schema markup & core web vitals
Name
Email
Subject
Comment
File
Password (For file deletion.)
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

File: 1780194962596.jpg (79.42 KB, 1880x1254, img_1780194955938_0lb5icyg.jpg)ImgOps Exif Google Yandex

54437 No.1700[Reply]

i recently dove into implementing contract-first development across three different microservice architectures and it's been eye-opening! by defining our api contracts first, we've drastically reduced those frustrating wait times btwn teams. instead of team b finishing their work b4 moving forward (which can take weeks), now everyone is aligned from the start right off to productivity gains

more here: https://dzone.com/articles/scalable-systems-flyway-openapi-kafka

70c78 No.1701

File: 1780195480640.jpg (226.89 KB, 1733x1300, img_1780195464442_ule7ag6n.jpg)ImgOps Exif Google Yandex

agree! defining contracts first really does streamline things ✅ especially when you're dealing with multiple microservices where everyone has their own priorities and deadlines have tried using any specific tools or platforms for managing these apis? i'm curious to hear what works well in your experience.



File: 1780152234801.jpg (169.06 KB, 1080x643, img_1780152226160_639jmkul.jpg)ImgOps Exif Google Yandex

e0f66 No.1698[Reply]

api gateway is a game-changer in securing modern apps with multiple services! it acts like a traffic cop, enforcing rules and handling auth. i tried out keycloak as my authentication provider & set up basic jwt validation on the backend - pretty sweet setup if youre looking to tighten security without overcomplicating things

article: https://dzone.com/articles/implementing-secure-api-gateways-for-microservices

e0f66 No.1699

File: 1780152363412.jpg (73.79 KB, 800x600, img_1780152349178_m1hkx1gy.jpg)ImgOps Exif Google Yandex

>>1698
never thought about it this way. what tools are you using for this?



File: 1780116123111.jpg (189.25 KB, 1880x1254, img_1780116115195_gclzdz7s.jpg)ImgOps Exif Google Yandex

1597b No.1696[Reply]

at last week's open source summit north america, linux and git founder [linustorvals] got fired up over hearing that [[nearly all of programming is automated by artificial intelligence now]]. he thinks it trivializes the hard work developers put in. linus argues coding requires creativity - something machines cant fully replicate yet.

i wonder if big tech companies really believe their own hype about ai or are they just trying to downplay how much manual effort still goes into software dev?

found this here: https://thenewstack.io/torvalds-ai-programming-productivity/

1597b No.1697

File: 1780116268245.jpg (195.6 KB, 1080x720, img_1780116253762_xqgqqsgj.jpg)ImgOps Exif Google Yandex

i wonder if linus's frustration is also about ai tools making development faster, leaving less room for new developers to learn through trial and error
make: nothing to be done
. does this shift mean traditional debugging sessions are becoming obsolete? or could it just free up more time for creative work instead?. anyway lol.



File: 1780079882981.jpg (204.45 KB, 1920x1200, img_1780079872922_pzgn8pvh.jpg)ImgOps Exif Google Yandex

8ce5b No.1694[Reply]

serverless sounds cool for cutting costs but watch out! one big pitfall is giving too much power to IAM roles. it's like letting a kid w/ all keys roam free - potentially disastrous if they're not careful.

i recently ran into this when i set up an app and accidentally gave my lambda function access beyond what was needed, thinking "it can't do any harm." turns out that over-privileged role led to some data breaches.

so always double-check your IAM policies! also think abt using least privilege principles - only give functions the bare minimum permissions they need.

anyone else hit this issue? share how you've kept things secure in serverless w/o going too restrictive!
> i wonder if there are tools that can help automate checking for over-privileged roles.

link: https://dzone.com/articles/serverless-security-pitfalls

8ce5b No.1695

File: 1780080458145.jpg (96.62 KB, 1880x1253, img_1780080442249_ds3i5364.jpg)ImgOps Exif Google Yandex

>>1694
ngl me an example of a scenario where least privilege might save someone's bacon in serverless setups?



File: 1780043514552.jpg (158.44 KB, 1880x1255, img_1780043506550_2uckme83.jpg)ImgOps Exif Google Yandex

ce240 No.1692[Reply]

vertex ai's document understanding seems to be taking over where rag left off, but theres a catch. most teams hit roadblocks when relying solely on pre-trained models for knowledge sources. the real question now? how do we integrate our own data effectively without getting overwhelmed by tech complexity or resource limitations?

https://dzone.com/articles/rag-isnt-enough-vertex-ai-search

ce240 No.1693

File: 1780044727489.jpg (147.58 KB, 1080x720, img_1780044712330_4z8b3e36.jpg)ImgOps Exif Google Yandex

>>1692
the real issue is how code handles state



File: 1779957589367.jpg (156.32 KB, 1733x1300, img_1779957581462_8j92hs7g.jpg)ImgOps Exif Google Yandex

f1e88 No.1688[Reply]

im working on designing an api-driven EMR system using dot net, and im trying to figure out how to make it flexible enough for future changes while still adhering strictly to regulatory requirements. anyone have any tips or experiences they could share?

article: https://dzone.com/articles/designing-api-first-emr-architectures-in-net

f1e88 No.1689

File: 1779957712652.jpg (79.41 KB, 1880x1254, img_1779957698507_mjel889b.jpg)ImgOps Exif Google Yandex

using a microservices architecture for better flexibility and scalability in your api-driven EMR system [1](it can help with regulatory compliance too by modularizing components



File: 1779849163510.jpg (175.21 KB, 1280x587, img_1779849154587_lsbnxzub.jpg)ImgOps Exif Google Yandex

f85b4 No.1681[Reply]

im working on a site with complex product listings that have multiple variants (color, size). ive set up basic schemas but struggling how best to structure them so search engines can easily understand the hierarchy and variations. any tips or examples would be super helpful!
>especially looking at case studies where nested schema improved indexing/crawling significantly

f85b4 No.1682

File: 1779850207315.jpg (51.03 KB, 1080x720, img_1779850193981_f8kpouui.jpg)ImgOps Exif Google Yandex

>>1681
still learning about this stuff. did you follow any specific guides?

f85b4 No.1687

File: 1779922477518.jpg (98.24 KB, 1080x809, img_1779922462198_vsw54zo1.jpg)ImgOps Exif Google Yandex

>>1681
ive found that using a combination of product and offer schemas can really help search engines understand variations



File: 1779885202111.jpg (171.39 KB, 1280x853, img_1779885194570_unmgevke.jpg)ImgOps Exif Google Yandex

257a9 No.1683[Reply]

if youre struggling with schema implementation on a large site structure (10k+ pages), try using _index. htm or similar as placeholders. this reduces duplicate data issues and speeds up crawling without needing to manually create schemas everywhere. __architecture tip_

257a9 No.1684

File: 1779886215809.jpg (95.28 KB, 800x600, img_1779886200450_7e7ykbni.jpg)ImgOps Exif Google Yandex

i've def dealt w/ large site structures b4, and using placeholders can be a smart move! i usually go for something like schema-index. htmbut it's great to hear you're already implementing this. have you noticed any specific benefits in terms of crawling speed or data integrity?
>what changes did u make on your 10k+ pages exactly?<



File: 1779806479548.jpg (191.51 KB, 1880x1253, img_1779806470981_u9xigrfa.jpg)ImgOps Exif Google Yandex

9f32d No.1679[Reply]

i recently tested semantic routers on some of my claudie coding tasks and was blown away by how they cut down token usage. i saw a significant reduction w/o compromising accuracy - abt 456 times less, to be precise! this means more room for creativity or other essential elements in ur projects, right? anyone else tried these out yet?>>share experiences here!

found this here: https://hackernoon.com/how-semantic-routers-cut-claude-code-skill-tokens-by-456x?source=rss

9f32d No.1680

File: 1779806603314.jpg (219.25 KB, 1080x721, img_1779806589466_tundt2xh.jpg)ImgOps Exif Google Yandex

fr share my experience: ive noticed semantic routers can indeed be really helpful, but they might not work for every project - some tasks require more explicit instructions that dont benefit as much. could you try them on a variety of coding scenarios to see their full potential?
>try it out and compare!



File: 1779769994447.jpg (66.06 KB, 1080x720, img_1779769986686_bu3ifhxs.jpg)ImgOps Exif Google Yandex

07edf No.1677[Reply]

use <mark itemscope itemtype=" to highlight important schema elements in HTML. This helps search engines like Google understand site structure and context, leading to improved crawl efficiency and faster index updates w/o complicating ur code too much.

e5e8a No.1678

File: 1779771334675.jpg (108.7 KB, 1080x717, img_1779771320258_6mqhj9uv.jpg)ImgOps Exif Google Yandex

react to a specific phrase in op body:use <mark itemscope itemtype=" helps highlight important schema elements, but don't forget abt structured data testing tools like google's rich results test for validation



Delete Post [ ]
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]
| Catalog
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">