Łukasz Chruściel, profile picture
Uploaded byŁukasz Chruściel
PDF, PPTX168 views

BoilingFrogs - Rozterki i decyzje. Czego się nauczyliśmy projektując API Syliusa

The document discusses the design decisions and architectural considerations encountered while developing the Sylius API, beginning from its inception in 2020. It compares GraphQL and REST architectures, highlighting their strengths and weaknesses while presenting various API design options and best practices, particularly in handling resources and versioning. The author emphasizes the importance of using Architectural Decision Records (ADRs) and adapting API structures to specific requirements without being constrained by UI mockups.

Technology◦
Related topics:
API Platform•

Embed presentation

Download as PDF, PPTX
@lukaszchrusciel Rozterki i Rozterki i decyzje. decyzje. Czego się nauczyliśmy projektując Czego się nauczyliśmy projektując API Syliusa API Syliusa
@lukaszchrusciel QUIZ QUIZ
@lukaszchrusciel Introduction Introduction
@lukaszchrusciel
@lukaszchrusciel
@lukaszchrusciel
@lukaszchrusciel
@lukaszchrusciel Started in 2020 Started in 2020 1.12 with API Platform 2.7 1.12 with API Platform 2.7 (since 31st of Oct) 1.13 stabilized with API 1.13 stabilized with API Platform 3.0 Platform 3.0
@lukaszchrusciel Decisions & Decisions & consequences consequences
@lukaszchrusciel Strategic design Strategic design
@lukaszchrusciel ADRs ADRs
@lukaszchrusciel QUIZ QUIZ
@lukaszchrusciel Architecture Decision Architecture Decision Records Records
@lukaszchrusciel Architecture Decision Records Architecture Decision Records [short title of solved problem and solution] Status: [proposed | rejected | ... ] Date: [YYYY-MM-DD] Context and Problem Statement Decision Drivers [driver 1, e.g., a force, facing concern, …] … Considered Options [option 1] Good, because [argument a] Bad, because [argument b] … Decision Outcome Chosen option: "[option 1]", because [justification]. References [Link type] [Link to ADR]
@lukaszchrusciel Architecture Decision Records Architecture Decision Records [short title of solved problem and solution] Status: [proposed | rejected | ... ] Date: [YYYY-MM-DD] Context and Problem Statement Decision Drivers [driver 1, e.g., a force, facing concern, …] … Considered Options [option 1] Good, because [argument a] Bad, because [argument b] … Decision Outcome Chosen option: "[option 1]", because [justification]. References [Link type] [Link to ADR]
@lukaszchrusciel Architecture Decision Records Architecture Decision Records [short title of solved problem and solution] Status: [proposed | rejected | ... ] Date: [YYYY-MM-DD] Context and Problem Statement Decision Drivers [driver 1, e.g., a force, facing concern, …] … Considered Options [option 1] Good, because [argument a] Bad, because [argument b] … Decision Outcome Chosen option: "[option 1]", because [justification]. References [Link type] [Link to ADR]
@lukaszchrusciel Architecture Decision Records Architecture Decision Records [short title of solved problem and solution] Status: [proposed | rejected | ... ] Date: [YYYY-MM-DD] Context and Problem Statement Decision Drivers [driver 1, e.g., a force, facing concern, …] … Considered Options [option 1] Good, because [argument a] Bad, because [argument b] … Decision Outcome Chosen option: "[option 1]", because [justification]. References [Link type] [Link to ADR]
@lukaszchrusciel Architecture Decision Records Architecture Decision Records [short title of solved problem and solution] Status: [proposed | rejected | ... ] Date: [YYYY-MM-DD] Context and Problem Statement Decision Drivers [driver 1, e.g., a force, facing concern, …] … Considered Options [option 1] Good, because [argument a] Bad, because [argument b] … Decision Outcome Chosen option: "[option 1]", because [justification]. References [Link type] [Link to ADR]
@lukaszchrusciel Architecture Decision Records Architecture Decision Records [short title of solved problem and solution] Status: [proposed | rejected | ... ] Date: [YYYY-MM-DD] Context and Problem Statement Decision Drivers [driver 1, e.g., a force, facing concern, …] … Considered Options [option 1] Good, because [argument a] Bad, because [argument b] … Decision Outcome Chosen option: "[option 1]", because [justification]. References [Link type] [Link to ADR]
@lukaszchrusciel Conclusion Conclusion Conclusion Conclusion Architecture Architecture Architecture Architecture Decision Records Decision Records Decision Records Decision Records FTW FTW FTW FTW [short title of solved problem and solution] Status: [proposed | rejected | ... ] Date: [YYYY-MM-DD] Context and Problem Statement Decision Drivers [driver 1, e.g., a force, facing concern, …] … Considered Options [option 1] Good, because [argument a] Bad, because [argument b] … Decision Outcome Chosen option: "[option 1]", because [justification]. References [Link type] [Link to ADR]
@lukaszchrusciel GraphQL vs REST GraphQL vs REST
@lukaszchrusciel 2020 2020 GraphQL GraphQL
@lukaszchrusciel Is it still? Is it still?
@lukaszchrusciel
@lukaszchrusciel
@lukaszchrusciel Is it not? Is it not?
@lukaszchrusciel GraphQL GraphQL Solves over fetching Solves over fetching and under fetching and under fetching By design
@lukaszchrusciel GraphQL GraphQL Sends everything with Sends everything with POST POST It is possible to do it with GET
@lukaszchrusciel GraphQL GraphQL Typed, nice Typed, nice documentation documentation out of the box
@lukaszchrusciel GraphQL GraphQL Gracefully deprecation Gracefully deprecation of queries of queries Which was not possible with default REST
@lukaszchrusciel GraphQL GraphQL Promise high Promise high performance performance due to reduction of queries
@lukaszchrusciel REST REST May solve over May solve over fetching and under fetching and under fetching fetching With sparefields sets and/or Vulcain
@lukaszchrusciel REST REST Takes advantage of 30 Takes advantage of 30 years of web cache years of web cache development development Fake data institute™
@lukaszchrusciel REST REST Typed, nice Typed, nice documentation documentation With OpenAPI
@lukaszchrusciel REST REST Gracefully deprecation Gracefully deprecation of queries of queries With OpenAPI and HTTP Headers
@lukaszchrusciel Quiz Quiz
@lukaszchrusciel In 2022 (...) REST API usage in production grew by 10% now at 70% compared to GraphQL 5% increased usage. 1 https://rapidapi.com/guides/2022-state-of-apis-what-developers-are-saying 1.
@lukaszchrusciel Conclusion Conclusion REST is a better default REST is a better default
@lukaszchrusciel High level API High level API design design
@lukaszchrusciel Unification of API Unification of API
@lukaszchrusciel Shop vs Shop vs Admin Admin
@lukaszchrusciel Shop Shop 72 endpoints 72 endpoints 64% of read endpoints 64% of read endpoints 20% of resources have 20% of resources have writable capabilities writable capabilities Admin Admin 128 endpoints 128 endpoints 52% of read endpoints 52% of read endpoints 40% of them are never 40% of them are never exposed in shop exposed in shop
@lukaszchrusciel Option #1 Option #1 Admin & Shop served together Admin & Shop served together /api/products/
@lukaszchrusciel Findings Findings Available fields Available fields Complicated serialisation groups depending on logged in user Requires granular access control Requires granular access control To not allow to access sensitive date for non-admins Hard to define different identifiers Hard to define different identifiers We have resigned from them later Good from REST perspective Good from REST perspective
@lukaszchrusciel Option #2 Option #2 Admin & Shop suffixed Admin & Shop suffixed /api/products/?admin
@lukaszchrusciel Findings Findings Available fields Available fields Depending on logged in user Requires granular access control Requires granular access control To not allow to access sensitive date for non-admins Seems wrong from the REST perspective Seems wrong from the REST perspective If we add suffix for different representation
@lukaszchrusciel Option #3 Option #3 Admin & Shop header split Admin & Shop header split /api/products/ Accept: application/vnd.sylius- admin.api+json
@lukaszchrusciel Findings Findings Available fields Available fields Depending on logged in user Requires granular access control Requires granular access control To now allow to access sensitive date for non- admins REST compilant REST compilant
@lukaszchrusciel Option #4 Option #4 Admin & Shop prefixed Admin & Shop prefixed /api/shop/products/ /api/admin/products/
@lukaszchrusciel Findings Findings Available fields Available fields Depending on logged in user Straightforward access control Straightforward access control Just with security config / / REST compilant REST compilant Disputable / / Easily supported Easily supported By API Platform and by Open API spec
@lukaszchrusciel QUIZ QUIZ
@lukaszchrusciel Conclusion Conclusion Custom headers are the Custom headers are the way to go way to go But But We chose the resource split We chose the resource split
@lukaszchrusciel API versioning API versioning
@lukaszchrusciel What we had What we had /api/v1
@lukaszchrusciel WIP WIP /new-api/
@lukaszchrusciel Option #1 Option #1 URL based versioning URL based versioning /api/v2
@lukaszchrusciel Option #2 Option #2 Accept header with version Accept header with version Accept: application/vnd.sylius.v1+json
@lukaszchrusciel Option #3 Option #3 Custom header Custom header X-Sylius-API-Version: 1
@lukaszchrusciel
@lukaszchrusciel QUIZ QUIZ
@lukaszchrusciel
@lukaszchrusciel Conclusion Conclusion API Evolution API Evolution Version in header Version in header We chose versioning in URL We chose versioning in URL
@lukaszchrusciel API flow API flow design design
@lukaszchrusciel Case #1 Case #1 Add to cart Add to cart
@lukaszchrusciel Simple product Simple product { "product": "/api/products/42", "quantity": 1 }
@lukaszchrusciel Configurable product #1 Configurable product #1 { "product": "/api/products/42", "productVariant": "/api/variants/42", "quantity": 1 }
@lukaszchrusciel Configurable product #2 Configurable product #2 { "product": "/api/products/42", "options": { "SIZE": "SIZE_L", "COLOR": "COLOR_BLUE" }, "quantity": 1 }
@lukaszchrusciel Let’s improve! Let’s improve!
@lukaszchrusciel Simple Simple product product { "product": "/api/products/42", "quantity": 1 } Configurable Configurable product product { "product": "/api/products/8", "productVariant": "/api/variants/864", "quantity": 1 }
@lukaszchrusciel Simple Simple product product { "product": "/api/products/42", "productVariant": "/api/variants/42", "quantity": 1 } Configurable Configurable product product { "product": "/api/products/8", "productVariant": "/api/variants/864", "quantity": 1 }
@lukaszchrusciel Simple & Configurable product Simple & Configurable product { "product": "/api/products/8", "productVariant": "/api/variants/42", "quantity": 1 }
@lukaszchrusciel Simple & Configurable product Simple & Configurable product { "productVariant": "/api/variants/42", "quantity": 1 }
@lukaszchrusciel But what with options? But what with options?
@lukaszchrusciel Price matrix in UI Price matrix in UI or or Ask us Ask us
@lukaszchrusciel Case #2 Case #2 Order details Order details
@lukaszchrusciel
@lukaszchrusciel Apply coupon PATCH /api/orders/TOKEN_VALUE /apply-coupon { "couponCode": "CHRISTMAS_SALE" }
@lukaszchrusciel
@lukaszchrusciel Cart claiming & addressing PATCH /api/orders/TOKEN_VALUE/address { "email": "test@example.com", "billingAddress": { "firstName": "Jane", "lastName": "Doe", "...": "..." } }
@lukaszchrusciel Reasoning? Reasoning? We are used to this separation We are used to this separation Mockups “force” such design Different data required on different pages Different data required on different pages Addressing requires state machine Addressing requires state machine transition transition Adding coupon requires recalculation
@lukaszchrusciel What about order What about order update? update?
@lukaszchrusciel Order update Order update PUT /api/orders/TOKEN_VALUE { "localeCode": "en_US" }
@lukaszchrusciel But it is just order But it is just order drafting! drafting!
@lukaszchrusciel Changed attitude Changed attitude UI Mockups should not force any UI Mockups should not force any design decision design decision We can preload data from more then one endpoint Use partial update Use partial update Don’t use state machine where there Don’t use state machine where there is none is none
@lukaszchrusciel Order update Order update PUT /api/orders/TOKEN_VALUE { "email": "test@example.com", "billingAddress": { "firstName": "Jane", "lastName": "Doe", "...": "..." }, "couponCode": "CHRISTMAS_SALE" }
@lukaszchrusciel Conclusion Conclusion Don't let mockups force Don't let mockups force you API design you API design
@lukaszchrusciel State transitions State transitions
@lukaszchrusciel Case Case Let’s cancel an Let’s cancel an order! order!
@lukaszchrusciel Considered option #1 Considered option #1 PATCH /api/orders/42/ { "state": "cancelled" }
@lukaszchrusciel Considered option #2 Considered option #2 PATCH /api/orders/42/cancel {}
@lukaszchrusciel
@lukaszchrusciel RESTful Archetypes RESTful Archetypes
@lukaszchrusciel RESTful Archetypes RESTful Archetypes Document Document /api/admin/orders/1 Collections Collections Server controlled /api/admin/orders Store Store Client controlled /api/admin/orders/123 Controller Controller /api/admin/orders/1/cancel 1 Based on: REST API Design Rulebook by Mark Masse 1.
@lukaszchrusciel Isn’t there a better way? Isn’t there a better way?
@lukaszchrusciel Considered option #3 Considered option #3 POST /api/orders- cancellation-requests/ {}
@lukaszchrusciel QUIZ QUIZ
@lukaszchrusciel Conclusion Conclusion Express your operation Express your operation as resources as resources
@lukaszchrusciel Takeaways Takeaways Use ADRs Use ADRs And browse them from time to time REST will be with us for the REST will be with us for the long time long time But GraphQL will be there as well Custom logic? New API Custom logic? New API resource! resource! Let’s behave like a tax department! Do not map HTML based Do not map HTML based websites to your API websites to your API I know, it was obvious
@lukaszchrusciel Thank Thank you! you!

More Related Content

PDF
What we've learned designing new Sylius API
byŁukasz Chruściel
 
PDF
Rest ful tools for lazy experts
byColdFusionConference
 
PDF
INTERFACE by apidays 2023 - API Green Score, Yannick Tremblais, Groupe Rocher
byapidays
 
PDF
4Developers - Rozterki i decyzje.pdf
byŁukasz Chruściel
 
PDF
GlueCon 2018: Are REST APIs Still Relevant Today?
byLaunchAny
 
PDF
Designing Usable APIs featuring Forrester Research, Inc.
byCA API Management
 
PDF
JOSA TechTalks - RESTful API Concepts and Best Practices
byJordan Open Source Association
 
PDF
SymfonyCon - Dilemmas and decisions..pdf
byŁukasz Chruściel
 
What we've learned designing new Sylius API
byŁukasz Chruściel
 
Rest ful tools for lazy experts
byColdFusionConference
 
INTERFACE by apidays 2023 - API Green Score, Yannick Tremblais, Groupe Rocher
byapidays
 
4Developers - Rozterki i decyzje.pdf
byŁukasz Chruściel
 
GlueCon 2018: Are REST APIs Still Relevant Today?
byLaunchAny
 
Designing Usable APIs featuring Forrester Research, Inc.
byCA API Management
 
JOSA TechTalks - RESTful API Concepts and Best Practices
byJordan Open Source Association
 
SymfonyCon - Dilemmas and decisions..pdf
byŁukasz Chruściel
 

Similar to BoilingFrogs - Rozterki i decyzje. Czego się nauczyliśmy projektując API Syliusa

PDF
Api design best practice
byRed Hat
 
PDF
Practical guide to building public APIs
byReda Hmeid MBCS
 
PDF
RESTFul Tools For Lazy Experts - CFSummit 2016
byOrtus Solutions, Corp
 
PDF
Алексей Веркеенко "Symfony2 & REST API"
byFwdays
 
PDF
Building Successful APIs Overnight - Orlando K - Codemotion Rome 2015
byCodemotion
 
PPTX
Microservices architecture overview v2
byDmitry Skaredov
 
PDF
Modern REST API design principles and rules.pdf
byAparna Sharma
 
PPTX
Http and REST APIs.
byRahul Tanwani
 
PDF
Enterprise-Ready FastAPI: Beyond the Basics
byAlexander Ptakhin
 
PDF
Modern REST API design principles and rules.pdf
byAparna Sharma
 
PDF
Designing APIs with Swagger and OpenAPI 1st Edition Joshua S. Ponelat
bytatajebezad
 
PPTX
Building a REST API for Longevity
byMuleSoft
 
PPTX
REST Api Tips and Tricks
byMaksym Bruner
 
PDF
Creating a RESTful api without losing too much sleep
byMike Anderson
 
PPTX
Cloud Side: REST APIs - Best practices
byNicolas FOATA
 
PDF
Chris Mathias Presents Advanced API Design Considerations at LA CTO Forum
byChris Mathias
 
PDF
Top API Security Issues Found During POCs
by42Crunch
 
PDF
apidays London 2023 - API Green Score, Yannick Tremblais & Julien Brun, Green...
byapidays
 
PPTX
Navigating the Post-OpenAPI Era with Innovative API Design Frameworks - Danie...
byNordic APIs
 
PPTX
REST-Api Design & Develop
bySabbir Rupom
 
Api design best practice
byRed Hat
 
Practical guide to building public APIs
byReda Hmeid MBCS
 
RESTFul Tools For Lazy Experts - CFSummit 2016
byOrtus Solutions, Corp
 
Алексей Веркеенко "Symfony2 & REST API"
byFwdays
 
Building Successful APIs Overnight - Orlando K - Codemotion Rome 2015
byCodemotion
 
Microservices architecture overview v2
byDmitry Skaredov
 
Modern REST API design principles and rules.pdf
byAparna Sharma
 
Http and REST APIs.
byRahul Tanwani
 
Enterprise-Ready FastAPI: Beyond the Basics
byAlexander Ptakhin
 
Modern REST API design principles and rules.pdf
byAparna Sharma
 
Designing APIs with Swagger and OpenAPI 1st Edition Joshua S. Ponelat
bytatajebezad
 
Building a REST API for Longevity
byMuleSoft
 
REST Api Tips and Tricks
byMaksym Bruner
 
Creating a RESTful api without losing too much sleep
byMike Anderson
 
Cloud Side: REST APIs - Best practices
byNicolas FOATA
 
Chris Mathias Presents Advanced API Design Considerations at LA CTO Forum
byChris Mathias
 
Top API Security Issues Found During POCs
by42Crunch
 
apidays London 2023 - API Green Score, Yannick Tremblais & Julien Brun, Green...
byapidays
 
Navigating the Post-OpenAPI Era with Innovative API Design Frameworks - Danie...
byNordic APIs
 
REST-Api Design & Develop
bySabbir Rupom
 

More from Łukasz Chruściel

PDF
Symfony World - Symfony components and design patterns
byŁukasz Chruściel
 
PDF
APIP 2024 - All the Challenges of Sylius Migration to API Platform 3.pdf
byŁukasz Chruściel
 
PDF
SymfonyLive Online 2023 - Is SOLID dead? .pdf
byŁukasz Chruściel
 
PDF
How to optimize background processes - when Sylius meets Blackfire
byŁukasz Chruściel
 
PDF
APIP 2024 - All the Challenges of Sylius Migration to API Platform 3.pdf [REU...
byŁukasz Chruściel
 
PDF
2024 PHPCon - Symfony background processing
byŁukasz Chruściel
 
PDF
Sylius and Api Platform The story of integration
byŁukasz Chruściel
 
PDF
SyliusCon - Typical pitfalls of Sylius development.pdf
byŁukasz Chruściel
 
PDF
Wprowadzenie do fundamentów Sylius 2.0
byŁukasz Chruściel
 
PDF
2024 eCommerceDays Toulouse - Sylius 2.0.pdf
byŁukasz Chruściel
 
PDF
ConFoo 2024 - Sylius 2.0, top-notch eCommerce for customizable solution
byŁukasz Chruściel
 
PDF
Unveiling the Future: Sylius 2.0 New Features
byŁukasz Chruściel
 
PDF
4Developers - Sylius CRUD generation revisited.pdf
byŁukasz Chruściel
 
PDF
Need for Speed: Removing speed bumps in API Projects
byŁukasz Chruściel
 
PDF
Worldwide Software Architecture Summit'23 - BDD and why most of us do it wron...
byŁukasz Chruściel
 
PDF
ConFoo 2024 - Need for Speed: Removing speed bumps in API Projects
byŁukasz Chruściel
 
PDF
Need for Speed: Removing speed bumps from your Symfony projects ⚡️
byŁukasz Chruściel
 
PDF
How to optimize background processes.pdf
byŁukasz Chruściel
 
PDF
A short tale about state machine
byŁukasz Chruściel
 
PDF
Dutch php a short tale about state machine
byŁukasz Chruściel
 
Symfony World - Symfony components and design patterns
byŁukasz Chruściel
 
APIP 2024 - All the Challenges of Sylius Migration to API Platform 3.pdf
byŁukasz Chruściel
 
SymfonyLive Online 2023 - Is SOLID dead? .pdf
byŁukasz Chruściel
 
How to optimize background processes - when Sylius meets Blackfire
byŁukasz Chruściel
 
APIP 2024 - All the Challenges of Sylius Migration to API Platform 3.pdf [REU...
byŁukasz Chruściel
 
2024 PHPCon - Symfony background processing
byŁukasz Chruściel
 
Sylius and Api Platform The story of integration
byŁukasz Chruściel
 
SyliusCon - Typical pitfalls of Sylius development.pdf
byŁukasz Chruściel
 
Wprowadzenie do fundamentów Sylius 2.0
byŁukasz Chruściel
 
2024 eCommerceDays Toulouse - Sylius 2.0.pdf
byŁukasz Chruściel
 
ConFoo 2024 - Sylius 2.0, top-notch eCommerce for customizable solution
byŁukasz Chruściel
 
Unveiling the Future: Sylius 2.0 New Features
byŁukasz Chruściel
 
4Developers - Sylius CRUD generation revisited.pdf
byŁukasz Chruściel
 
Need for Speed: Removing speed bumps in API Projects
byŁukasz Chruściel
 
Worldwide Software Architecture Summit'23 - BDD and why most of us do it wron...
byŁukasz Chruściel
 
ConFoo 2024 - Need for Speed: Removing speed bumps in API Projects
byŁukasz Chruściel
 
Need for Speed: Removing speed bumps from your Symfony projects ⚡️
byŁukasz Chruściel
 
How to optimize background processes.pdf
byŁukasz Chruściel
 
A short tale about state machine
byŁukasz Chruściel
 
Dutch php a short tale about state machine
byŁukasz Chruściel
 

Recently uploaded

PDF
Techbrains Baku 2025 by GoUP - all speaker session
byHusseinMalikMammadli
 
PPTX
Pizza Chain Market Data Scraping for Better Insights Report.pptx
byWeb Data Crawler
 
PDF
Top 10 API Automation Testing Tools: Features, Pros & Cons
byhenrycavill30521
 
PDF
What is Voice User Interface (VUI) Definition & Examples.pdf
byDesign Studio UI UX
 
PPT
HDTV and DTV Standards: The United States Opts for a Digital HDTV Standard
byJeffrey Hart
 
PDF
How Azure DevOps Consultants Dubai Reduce Release Delays.pdf
byLogicEra
 
PDF
MAD (1).pdf Mobile application develipment
byprathiT1
 
PPTX
Large Language Model. LLM Audit Artificial Intelligence
byMANASCHOUDHARY22
 
PPTX
Corporate AI Training to AI Enable a Company Workforce
byStélio Inácio
 
PDF
250 Prompts - ChatGPT acting as your Assistant
byMihir Nagarkar
 
PDF
IAI-Unit1-notes useful.............................
bydinesh620610
 
PPTX
Cyber Security Overview-breif note .pptx
byxbitindiacom
 
PDF
Regenerative Agriculture Finance : Environmental impact
byrose mason
 
PDF
Digital Marketing Trends in 2026: AI, Data, Content & Future Growth
byConacent Consulting
 
PPTX
Cybersecurity Basics: Understanding Threats, Protection Methods, and Safe Dig...
byDhruvManiar3
 
PDF
IAC 500 Sensor - Humidity Measurement Device
byCS Instruments
 
PDF
“Lessons from Yesterday's Tomorrowland” by Scott M. Graffius
byScott M. Graffius
 
PPT
Carole BirdCarole BirdCarole BirdCarole Bird.ppt
byk4n3kictf
 
PPTX
Digital transformation success powered by EPM and NexInfo.pptx
byjayasuryanexinfo
 
PPTX
Document Reconstruction using AI & Deep Learning
bysonjuktaweb
 
Techbrains Baku 2025 by GoUP - all speaker session
byHusseinMalikMammadli
 
Pizza Chain Market Data Scraping for Better Insights Report.pptx
byWeb Data Crawler
 
Top 10 API Automation Testing Tools: Features, Pros & Cons
byhenrycavill30521
 
What is Voice User Interface (VUI) Definition & Examples.pdf
byDesign Studio UI UX
 
HDTV and DTV Standards: The United States Opts for a Digital HDTV Standard
byJeffrey Hart
 
How Azure DevOps Consultants Dubai Reduce Release Delays.pdf
byLogicEra
 
MAD (1).pdf Mobile application develipment
byprathiT1
 
Large Language Model. LLM Audit Artificial Intelligence
byMANASCHOUDHARY22
 
Corporate AI Training to AI Enable a Company Workforce
byStélio Inácio
 
250 Prompts - ChatGPT acting as your Assistant
byMihir Nagarkar
 
IAI-Unit1-notes useful.............................
bydinesh620610
 
Cyber Security Overview-breif note .pptx
byxbitindiacom
 
Regenerative Agriculture Finance : Environmental impact
byrose mason
 
Digital Marketing Trends in 2026: AI, Data, Content & Future Growth
byConacent Consulting
 
Cybersecurity Basics: Understanding Threats, Protection Methods, and Safe Dig...
byDhruvManiar3
 
IAC 500 Sensor - Humidity Measurement Device
byCS Instruments
 
“Lessons from Yesterday's Tomorrowland” by Scott M. Graffius
byScott M. Graffius
 
Carole BirdCarole BirdCarole BirdCarole Bird.ppt
byk4n3kictf
 
Digital transformation success powered by EPM and NexInfo.pptx
byjayasuryanexinfo
 
Document Reconstruction using AI & Deep Learning
bysonjuktaweb
 

BoilingFrogs - Rozterki i decyzje. Czego się nauczyliśmy projektując API Syliusa