Developing “RESTful transactions” with Apache Sling
2 likes3,940 views
The document summarizes a presentation by Şenol Taş at the Apache Sling tech meetup, focusing on 'restful transactions' in web development. It discusses the evolution of websites from simple platforms to complex applications that require reliable transaction management, highlighting the principles of ACID (Atomicity, Consistency, Isolation, Durability) and how REST principles can complicate transactions. The presentation emphasizes adapting the approach to transactions and utilizing tools like Adobe CQ and event-driven architecture to enhance functionality.
1 of 28
Downloaded 41 times
Ad
Recommended
Atomic Transactions for the REST of us
Atomic Transactions for the REST of usCesare PautassoAtomic Transactions for the REST of us discusses how atomic transactions can be achieved across multiple RESTful web services without modifying HTTP or requiring special headers. It proposes a client-driven transaction protocol where state transitions go through intermediate "reserved" states that are later confirmed or canceled. This allows transactions to be made up of multiple state changes across services while ensuring atomicity if a failure occurs during confirmation. The protocol guarantees atomicity as long as confirmations complete before reserved states time out.
The New Way of Developing with AEM 6.0 | Sightly | Beautiful Markup
The New Way of Developing with AEM 6.0 | Sightly | Beautiful MarkupSenol TasThis document summarizes the key features of Sightly, a templating language for Adobe Experience Manager (AEM) 6.0. Sightly provides lightweight, secure, code-less templating that allows for separation of concerns between logic and markup. It uses standard HTML5 and an intuitive expression language for logic. Sightly aims to reduce development time and costs through a simplified workflow between designers and developers. The document outlines Sightly's expression language and block statements for building templates.
Adobe Sneak Peak - Introducing HTL @ Evovle'13
Adobe Sneak Peak - Introducing HTL @ Evovle'13Senol TasPresentation with Gabriel @ Evovle'13 CQ Conference in San Diego. Introduction tot he new HTL Template Concept / Prototype for Adobe CQ / AEM
Performance monitoring and call tracing in microservice environments
Performance monitoring and call tracing in microservice environmentsMartin GutenbrunnerThe document discusses challenges with monitoring microservice environments, including tracing calls between services. It describes how custom implementations can be complex due to different technologies. Commercial solutions like Dynatrace Ruxit provide unified monitoring with call tracing across technologies with minimal setup. They automatically detect issues without thresholds and include client-side monitoring.
Rest Vs Soap Yawn2289
Rest Vs Soap Yawn2289Kalyan Vijay Kumar PasumarthiReST is an architectural style defined by a set of constraints including being client-server, stateless, cacheable, and having a uniform interface. It favors directly addressing resources over remote procedure calls and aims to make systems more scalable and loosely coupled. While sometimes seen as weak due to performance and customization issues, ReST architectures also provide benefits like low barriers to entry and being easier to develop and maintain.
ReST Vs SOA(P) ... Yawn
ReST Vs SOA(P) ... YawnoztenThis document discusses Representational State Transfer (REST) and compares it to Service Oriented Architecture (SOA). It provides background on the early web and how REST emerged as a set of constraints for networked applications. It notes that REST is not a technology, standard, or product, but rather an architectural style. The document discusses core REST concepts like resources, representations, and stateless interactions over the uniform interface of HTTP. It addresses some common misconceptions about REST and whether it is only suited for simple use cases.
Ijirsm ashok-kumar-ps-compulsiveness-of-res tful-web-services
Ijirsm ashok-kumar-ps-compulsiveness-of-res tful-web-servicesIJIR JOURNALS IJIRUSAThis document discusses the comparison between SOAP and REST web services, emphasizing how REST, though not standardized, offers a simpler and more scalable approach for web applications. The principles of REST, derived from Roy Fielding's thesis, highlight statelessness and a uniform interface for resource manipulation through standard HTTP methods. The paper concludes by outlining the key strengths and limitations of REST, particularly its suitability for e-commerce applications.
Representational State Transfer (REST)
Representational State Transfer (REST)David KrmpoticREST (REpresentational State Transfer) is an architectural style for building web APIs that relies on HTTP verbs like GET, POST, PUT, and DELETE to manipulate resources identified by URIs. Resources can have multiple representations like JSON or XML, and the appropriate representation is selected via content negotiation. REST aims to provide a simple, lightweight interface and takes advantage of existing web protocols to transfer representations of resources between clients and servers. Key REST constraints include using nouns for resources and HTTP methods for actions, making the interface lightweight, client-server, cacheable, and layered.
RESTful services
RESTful servicesPedram Bashiri1) RESTful web services are applications that are built based on REST architecture principles and use standard HTTP methods like GET, POST, PUT, DELETE to perform CRUD operations on resources identified by URIs.
2) The key principles of REST architecture include statelessness, cacheability, uniform interface, addressability through URIs, and connectedness through hypermedia.
3) To design RESTful web services, resources of the application need to be identified and basic CRUD operations defined for each resource using appropriate HTTP methods and URI design.
RESTful Web Services
RESTful Web ServicesadeppathondurThis document provides an introduction to RESTful web services and architectures. It discusses how REST uses resources identified by URIs and manipulated through their representations. The document outlines the key principles of REST including being stateless, having a uniform interface, and using hypertext as the engine of application state. It also discusses how REST aligns with HTTP and can be applied to distributed systems through its emphasis on scalability, general interfaces, and encapsulation of legacy systems.
Rest
RestPrabhat gangwarRepresentational State Transfer (REST) is a network architectural style that defines best practices for distributed hypermedia systems. It uses HTTP as a transfer mechanism and defines resources, which are any information that can be named, addressed, and linked. Resources are accessed via URIs and represented in different data formats like XML, JSON, and HTML. A RESTful API is designed around resources and uses HTTP verbs like GET, POST, PUT, and DELETE to operate on them. This allows uniform and stateless access to resources in a loosely coupled and scalable way.
Rest surekha
Rest surekhaSurekha AchantaREST (REpresentational State Transfer) is a software architectural style for distributed hypermedia systems such as the World Wide Web. It uses client-server architecture and focuses on stateless operations, caching, and a uniform interface between components. The key advantages of REST include its simplicity, flexibility, and ability to scale to large amounts of users and data.
The Internet as Web Services: introduction to ReST
The Internet as Web Services: introduction to ReSTBruno Kessler FoundationThe document is a presentation by Oscar Zambotti on web services, focusing on the introduction to REST (Representational State Transfer) and its differences with SOAP (Simple Object Access Protocol). It covers topics such as web service definitions, use cases with popular platforms like Twitter and Flickr, and the importance of APIs and HTTP methods in enhancing interoperability. Additionally, it highlights the future of web services in relation to the evolving internet economy and offers examples and code snippets for practical understanding.
REST & RESTful Web Services
REST & RESTful Web ServicesHalil Burak CetinkayaREST (Representational State Transfer) is an architectural style focused on client-server communication that utilizes resources, identified by unique URIs, to facilitate interaction over HTTP. It promotes statelessness, scalability, and a uniform interface for transferring resource states, making it distinct from traditional protocols like SOAP. REST is widely popular for web services due to its simplicity, flexibility, and efficiency, particularly in modern browser-based applications.
Research Topics in Machine Hypermedia
Research Topics in Machine HypermediaMichael KosterThis document discusses research topics in machine hypermedia system design. It investigates RESTful design patterns for interoperable machine interfaces and semantic interoperability. Key research topics include reference system architecture, content format design, RESTful asynchronous communication, and model-based hypertext annotation. The goal is to develop reusable domain schemas and models to enable semantic interoperability between machine systems.
Have Some Rest Building Web2.0 Apps And Services
Have Some Rest Building Web2.0 Apps And ServicesNenad NikolicThe document discusses the principles and practices of REST (Representational State Transfer) as applied to web applications, particularly in the context of Web 2.0. It outlines the architecture, benefits, and examples of RESTful services, emphasizing the use of HTTP protocols and the importance of unique resource addressing. Additionally, it contrasts REST with other web service methodologies like SOAP and RPC, and presents Java technologies and frameworks for implementing RESTful services.
REST e Resource Oriented Architectures
REST e Resource Oriented ArchitecturesGrUSPThe document discusses Representational State Transfer (REST) as an architectural style for web services, emphasizing its principles and how to design RESTful services through resource identification, URI design, and the uniform interface. It highlights the differences between REST and other architectural models, the importance of stateless interactions, and the potential for building applications that are discoverable, testable, and scalable. Through examples, it illustrates how REST applies to a chess game scenario and asserts the relevance of REST in modern web development.
Resource Oriented Architectures
Resource Oriented ArchitecturesGabriele LanaThis document discusses REST (Representational State Transfer) and resource-oriented architectures. It provides examples of designing RESTful APIs and services using common REST constraints like URIs to identify resources, HTTP methods to manipulate resources, and resource representations. The key aspects covered are modeling the domain as resources, designing URIs, exposing a uniform interface, designing representations, and common interaction flows and error conditions.
A Distributed Transaction Model for Read-Write Linked Data Applications
A Distributed Transaction Model for Read-Write Linked Data ApplicationsNandana MihindukulasooriyaThe document presents a distributed transaction model for data-intensive read-write linked data applications, addressing the lack of transaction support in enterprise systems. It outlines the model's key features, including linked data resources, multi-version concurrency control, and the alignment with W3C LDP. The motivation is to enhance the adoption of linked data technologies in enterprise application integration by providing quality-of-service and addressing common transaction scenarios.
Drupal As A RESTful Backend For Client Side Applications
Drupal As A RESTful Backend For Client Side ApplicationsMyplanet DigitalThis document discusses using Drupal as a RESTful backend for client-side applications. It introduces REST (REpresentational State Transfer) as an architectural style with five primary constraints: client-server, stateless, cacheable, layered system, and uniform interface. The document explains that client-side and mobile applications benefit from RESTful APIs as they can load data asynchronously after loading. It also describes Drupal's Services module for creating RESTful endpoints to integrate external applications and access API data. Specific HTTP methods for creating, retrieving, updating, and deleting resources are outlined. Finally, the document mentions improvements to REST support in Drupal 8 using Symfony components.
Oak, the Architecture of the new Repository
Oak, the Architecture of the new RepositoryMichael DürigThe document discusses the architecture and design goals of the Apache Oak repository, emphasizing scalability, customization, and conflict handling in a clustered environment. It covers key concepts such as content merging, commit hooks, and search functionalities, along with different implementations and strategies for access control and sharding. The presentation provides a comprehensive overview of the underlying technology and its applications in large and concurrent deployments.
Applications of the REST Principle
Applications of the REST Principleelliando diasThis document discusses applying REST principles to integrate systems. It provides examples of using REST for basic web publishing, data-intensive integration through microformats and mashups, and process-intensive integration through RESTful workflows. It also describes a case study of developing a RESTful architecture for the Australian lending industry to publish and share loan data in a standardized way.
Real world RESTful service development problems and solutions
Real world RESTful service development problems and solutionsMasoud KalaliThe document discusses various challenges and solutions related to the development of RESTful services, including content negotiation, resource versioning, validation, and caching. It emphasizes the importance of performance, security, and best practices in API design, as well as the benefits and challenges of microservices architecture. Additionally, it covers the REST maturity model and highlights best practices for building scalable and efficient web services.
Unerstanding and Using RESTful APIs
Unerstanding and Using RESTful APIsSocialDevCamp ChicagoThe document discusses the principles and implementation of RESTful APIs, emphasizing their dominance in web 2.0 and social media. It outlines key concepts like statelessness, cacheability, and the use of HTTP methods, along with the comparison between REST and SOAP. Additionally, it highlights the need for improved documentation and tools like WADL for better implementation and discovery of RESTful services.
Rest ful security
Rest ful securityTruong TruongThis document discusses RESTful security and how to align REST architecture with web security and caching. It proposes using directory-specific symmetric encryption keys derived from a root key through a key hierarchy to encrypt content. This allows access-controlled cached content without encrypting repeatedly for each user, improving scalability. The solution separates access control decisions from data requests and encrypts content once per cache lifetime rather than per user session.
BeJUG JAX-RS Event
BeJUG JAX-RS EventStephan JanssenThis document provides an overview of Representational State Transfer (REST) theory and the Java API for RESTful Web Services (JAX-RS). It begins with an agenda that outlines REST principles, anti-patterns, and patterns that will be covered, as well as an introduction to JAX-RS and examples of its code. The document then discusses the core REST principles of addressability, connectedness, uniform interface, representations, and statelessness. It also identifies common REST anti-patterns and provides examples of good REST patterns and practices. Finally, it introduces JAX-RS as an annotation-driven API that helps developers build RESTful web services in compliance with REST principles and J2EE integration.
REST in short
REST in shortAkshay BallarpureREST is an architectural style for building distributed systems based on hypermedia and common web standards. It uses HTTP methods like GET, POST, PUT, DELETE to operate on resources identified by URIs. Resources can have multiple representations like JSON, XML and responses are cacheable. RESTful web services use these concepts and define base URIs, supported formats and operations.
Understanding and Using Rest APIs (SocialDevCamp Chicago 2009)
Understanding and Using Rest APIs (SocialDevCamp Chicago 2009)Pete MoranoRESTful APIs have become integral to technology and dominate web development. While REST is based on simple principles like using HTTP methods and representing resources, there is still a lack of standardization around documentation and discovery. WADL aims to provide a standard like WSDL for REST that would reduce errors and enable code generation.
War_And_Cyber_3_Years_Of_Struggle_And_Lessons_For_Global_Security.pdf
War_And_Cyber_3_Years_Of_Struggle_And_Lessons_For_Global_Security.pdfbiswajitbanerjee38Russia is one of the most aggressive nations when it comes to state coordinated cyberattacks — and Ukraine has been at the center of their crosshairs for 3 years. This report, provided the State Service of Special Communications and Information Protection of Ukraine contains an incredible amount of cybersecurity insights, showcasing the coordinated aggressive cyberwarfare campaigns of Russia against Ukraine.
It brings to the forefront that understanding your adversary, especially an aggressive nation state, is important for cyber defense. Knowing their motivations, capabilities, and tactics becomes an advantage when allocating resources for maximum impact.
Intelligence shows Russia is on a cyber rampage, leveraging FSB, SVR, and GRU resources to professionally target Ukraine’s critical infrastructures, military, and international diplomacy support efforts.
The number of total incidents against Ukraine, originating from Russia, has steadily increased from 1350 in 2021 to 4315 in 2024, but the number of actual critical incidents has been managed down from a high of 1048 in 2022 to a mere 59 in 2024 — showcasing how the rapid detection and response to cyberattacks has been impacted by Ukraine’s improved cyber resilience.
Even against a much larger adversary, Ukraine is showcasing outstanding cybersecurity, enabled by strong strategies and sound tactics. There are lessons to learn for any enterprise that could potentially be targeted by aggressive nation states.
Definitely worth the read!
"Database isolation: how we deal with hundreds of direct connections to the d...
"Database isolation: how we deal with hundreds of direct connections to the d...FwdaysWhat can go wrong if you allow each service to access the database directly? In a startup, this seems like a quick and easy solution, but as the system scales, problems appear that no one could have guessed.
In my talk, I'll share Solidgate's experience in transforming its architecture: from the chaos of direct connections to a service-based data access model. I will talk about the transition stages, bottlenecks, and how isolation affected infrastructure support. I will honestly show what worked and what didn't. In short, we will analyze the controversy of this talk.
More Related Content
Similar to Developing “RESTful transactions” with Apache Sling (20)
RESTful services
RESTful servicesPedram Bashiri1) RESTful web services are applications that are built based on REST architecture principles and use standard HTTP methods like GET, POST, PUT, DELETE to perform CRUD operations on resources identified by URIs.
2) The key principles of REST architecture include statelessness, cacheability, uniform interface, addressability through URIs, and connectedness through hypermedia.
3) To design RESTful web services, resources of the application need to be identified and basic CRUD operations defined for each resource using appropriate HTTP methods and URI design.
RESTful Web Services
RESTful Web ServicesadeppathondurThis document provides an introduction to RESTful web services and architectures. It discusses how REST uses resources identified by URIs and manipulated through their representations. The document outlines the key principles of REST including being stateless, having a uniform interface, and using hypertext as the engine of application state. It also discusses how REST aligns with HTTP and can be applied to distributed systems through its emphasis on scalability, general interfaces, and encapsulation of legacy systems.
Rest
RestPrabhat gangwarRepresentational State Transfer (REST) is a network architectural style that defines best practices for distributed hypermedia systems. It uses HTTP as a transfer mechanism and defines resources, which are any information that can be named, addressed, and linked. Resources are accessed via URIs and represented in different data formats like XML, JSON, and HTML. A RESTful API is designed around resources and uses HTTP verbs like GET, POST, PUT, and DELETE to operate on them. This allows uniform and stateless access to resources in a loosely coupled and scalable way.
Rest surekha
Rest surekhaSurekha AchantaREST (REpresentational State Transfer) is a software architectural style for distributed hypermedia systems such as the World Wide Web. It uses client-server architecture and focuses on stateless operations, caching, and a uniform interface between components. The key advantages of REST include its simplicity, flexibility, and ability to scale to large amounts of users and data.
The Internet as Web Services: introduction to ReST
The Internet as Web Services: introduction to ReSTBruno Kessler FoundationThe document is a presentation by Oscar Zambotti on web services, focusing on the introduction to REST (Representational State Transfer) and its differences with SOAP (Simple Object Access Protocol). It covers topics such as web service definitions, use cases with popular platforms like Twitter and Flickr, and the importance of APIs and HTTP methods in enhancing interoperability. Additionally, it highlights the future of web services in relation to the evolving internet economy and offers examples and code snippets for practical understanding.
REST & RESTful Web Services
REST & RESTful Web ServicesHalil Burak CetinkayaREST (Representational State Transfer) is an architectural style focused on client-server communication that utilizes resources, identified by unique URIs, to facilitate interaction over HTTP. It promotes statelessness, scalability, and a uniform interface for transferring resource states, making it distinct from traditional protocols like SOAP. REST is widely popular for web services due to its simplicity, flexibility, and efficiency, particularly in modern browser-based applications.
Research Topics in Machine Hypermedia
Research Topics in Machine HypermediaMichael KosterThis document discusses research topics in machine hypermedia system design. It investigates RESTful design patterns for interoperable machine interfaces and semantic interoperability. Key research topics include reference system architecture, content format design, RESTful asynchronous communication, and model-based hypertext annotation. The goal is to develop reusable domain schemas and models to enable semantic interoperability between machine systems.
Have Some Rest Building Web2.0 Apps And Services
Have Some Rest Building Web2.0 Apps And ServicesNenad NikolicThe document discusses the principles and practices of REST (Representational State Transfer) as applied to web applications, particularly in the context of Web 2.0. It outlines the architecture, benefits, and examples of RESTful services, emphasizing the use of HTTP protocols and the importance of unique resource addressing. Additionally, it contrasts REST with other web service methodologies like SOAP and RPC, and presents Java technologies and frameworks for implementing RESTful services.
REST e Resource Oriented Architectures
REST e Resource Oriented ArchitecturesGrUSPThe document discusses Representational State Transfer (REST) as an architectural style for web services, emphasizing its principles and how to design RESTful services through resource identification, URI design, and the uniform interface. It highlights the differences between REST and other architectural models, the importance of stateless interactions, and the potential for building applications that are discoverable, testable, and scalable. Through examples, it illustrates how REST applies to a chess game scenario and asserts the relevance of REST in modern web development.
Resource Oriented Architectures
Resource Oriented ArchitecturesGabriele LanaThis document discusses REST (Representational State Transfer) and resource-oriented architectures. It provides examples of designing RESTful APIs and services using common REST constraints like URIs to identify resources, HTTP methods to manipulate resources, and resource representations. The key aspects covered are modeling the domain as resources, designing URIs, exposing a uniform interface, designing representations, and common interaction flows and error conditions.
A Distributed Transaction Model for Read-Write Linked Data Applications
A Distributed Transaction Model for Read-Write Linked Data ApplicationsNandana MihindukulasooriyaThe document presents a distributed transaction model for data-intensive read-write linked data applications, addressing the lack of transaction support in enterprise systems. It outlines the model's key features, including linked data resources, multi-version concurrency control, and the alignment with W3C LDP. The motivation is to enhance the adoption of linked data technologies in enterprise application integration by providing quality-of-service and addressing common transaction scenarios.
Drupal As A RESTful Backend For Client Side Applications
Drupal As A RESTful Backend For Client Side ApplicationsMyplanet DigitalThis document discusses using Drupal as a RESTful backend for client-side applications. It introduces REST (REpresentational State Transfer) as an architectural style with five primary constraints: client-server, stateless, cacheable, layered system, and uniform interface. The document explains that client-side and mobile applications benefit from RESTful APIs as they can load data asynchronously after loading. It also describes Drupal's Services module for creating RESTful endpoints to integrate external applications and access API data. Specific HTTP methods for creating, retrieving, updating, and deleting resources are outlined. Finally, the document mentions improvements to REST support in Drupal 8 using Symfony components.
Oak, the Architecture of the new Repository
Oak, the Architecture of the new RepositoryMichael DürigThe document discusses the architecture and design goals of the Apache Oak repository, emphasizing scalability, customization, and conflict handling in a clustered environment. It covers key concepts such as content merging, commit hooks, and search functionalities, along with different implementations and strategies for access control and sharding. The presentation provides a comprehensive overview of the underlying technology and its applications in large and concurrent deployments.
Applications of the REST Principle
Applications of the REST Principleelliando diasThis document discusses applying REST principles to integrate systems. It provides examples of using REST for basic web publishing, data-intensive integration through microformats and mashups, and process-intensive integration through RESTful workflows. It also describes a case study of developing a RESTful architecture for the Australian lending industry to publish and share loan data in a standardized way.
Real world RESTful service development problems and solutions
Real world RESTful service development problems and solutionsMasoud KalaliThe document discusses various challenges and solutions related to the development of RESTful services, including content negotiation, resource versioning, validation, and caching. It emphasizes the importance of performance, security, and best practices in API design, as well as the benefits and challenges of microservices architecture. Additionally, it covers the REST maturity model and highlights best practices for building scalable and efficient web services.
Unerstanding and Using RESTful APIs
Unerstanding and Using RESTful APIsSocialDevCamp ChicagoThe document discusses the principles and implementation of RESTful APIs, emphasizing their dominance in web 2.0 and social media. It outlines key concepts like statelessness, cacheability, and the use of HTTP methods, along with the comparison between REST and SOAP. Additionally, it highlights the need for improved documentation and tools like WADL for better implementation and discovery of RESTful services.
Rest ful security
Rest ful securityTruong TruongThis document discusses RESTful security and how to align REST architecture with web security and caching. It proposes using directory-specific symmetric encryption keys derived from a root key through a key hierarchy to encrypt content. This allows access-controlled cached content without encrypting repeatedly for each user, improving scalability. The solution separates access control decisions from data requests and encrypts content once per cache lifetime rather than per user session.
BeJUG JAX-RS Event
BeJUG JAX-RS EventStephan JanssenThis document provides an overview of Representational State Transfer (REST) theory and the Java API for RESTful Web Services (JAX-RS). It begins with an agenda that outlines REST principles, anti-patterns, and patterns that will be covered, as well as an introduction to JAX-RS and examples of its code. The document then discusses the core REST principles of addressability, connectedness, uniform interface, representations, and statelessness. It also identifies common REST anti-patterns and provides examples of good REST patterns and practices. Finally, it introduces JAX-RS as an annotation-driven API that helps developers build RESTful web services in compliance with REST principles and J2EE integration.
REST in short
REST in shortAkshay BallarpureREST is an architectural style for building distributed systems based on hypermedia and common web standards. It uses HTTP methods like GET, POST, PUT, DELETE to operate on resources identified by URIs. Resources can have multiple representations like JSON, XML and responses are cacheable. RESTful web services use these concepts and define base URIs, supported formats and operations.
Understanding and Using Rest APIs (SocialDevCamp Chicago 2009)
Understanding and Using Rest APIs (SocialDevCamp Chicago 2009)Pete MoranoRESTful APIs have become integral to technology and dominate web development. While REST is based on simple principles like using HTTP methods and representing resources, there is still a lack of standardization around documentation and discovery. WADL aims to provide a standard like WSDL for REST that would reduce errors and enable code generation.
The Internet as Web Services: introduction to ReST
The Internet as Web Services: introduction to ReSTBruno Kessler Foundation
Have Some Rest Building Web2.0 Apps And Services
Have Some Rest Building Web2.0 Apps And ServicesNenad Nikolic
A Distributed Transaction Model for Read-Write Linked Data Applications
A Distributed Transaction Model for Read-Write Linked Data ApplicationsNandana Mihindukulasooriya
Drupal As A RESTful Backend For Client Side Applications
Drupal As A RESTful Backend For Client Side ApplicationsMyplanet Digital
Real world RESTful service development problems and solutions
Real world RESTful service development problems and solutionsMasoud Kalali
Understanding and Using Rest APIs (SocialDevCamp Chicago 2009)
Understanding and Using Rest APIs (SocialDevCamp Chicago 2009)Pete Morano
Recently uploaded (20)
War_And_Cyber_3_Years_Of_Struggle_And_Lessons_For_Global_Security.pdf
War_And_Cyber_3_Years_Of_Struggle_And_Lessons_For_Global_Security.pdfbiswajitbanerjee38Russia is one of the most aggressive nations when it comes to state coordinated cyberattacks — and Ukraine has been at the center of their crosshairs for 3 years. This report, provided the State Service of Special Communications and Information Protection of Ukraine contains an incredible amount of cybersecurity insights, showcasing the coordinated aggressive cyberwarfare campaigns of Russia against Ukraine.
It brings to the forefront that understanding your adversary, especially an aggressive nation state, is important for cyber defense. Knowing their motivations, capabilities, and tactics becomes an advantage when allocating resources for maximum impact.
Intelligence shows Russia is on a cyber rampage, leveraging FSB, SVR, and GRU resources to professionally target Ukraine’s critical infrastructures, military, and international diplomacy support efforts.
The number of total incidents against Ukraine, originating from Russia, has steadily increased from 1350 in 2021 to 4315 in 2024, but the number of actual critical incidents has been managed down from a high of 1048 in 2022 to a mere 59 in 2024 — showcasing how the rapid detection and response to cyberattacks has been impacted by Ukraine’s improved cyber resilience.
Even against a much larger adversary, Ukraine is showcasing outstanding cybersecurity, enabled by strong strategies and sound tactics. There are lessons to learn for any enterprise that could potentially be targeted by aggressive nation states.
Definitely worth the read!
"Database isolation: how we deal with hundreds of direct connections to the d...
"Database isolation: how we deal with hundreds of direct connections to the d...FwdaysWhat can go wrong if you allow each service to access the database directly? In a startup, this seems like a quick and easy solution, but as the system scales, problems appear that no one could have guessed.
In my talk, I'll share Solidgate's experience in transforming its architecture: from the chaos of direct connections to a service-based data access model. I will talk about the transition stages, bottlenecks, and how isolation affected infrastructure support. I will honestly show what worked and what didn't. In short, we will analyze the controversy of this talk.
June Patch Tuesday
June Patch TuesdayIvantiIvanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
FME for Distribution & Transmission Integrity Management Program (DIMP & TIMP)
FME for Distribution & Transmission Integrity Management Program (DIMP & TIMP)Safe SoftwarePeoples Gas in Chicago, IL has changed to a new Distribution & Transmission Integrity Management Program (DIMP & TIMP) software provider in recent years. In order to successfully deploy the new software we have created a series of ETL processes using FME Form to transform our gas facility data to meet the required DIMP & TIMP data specifications. This presentation will provide an overview of how we used FME to transform data from ESRI’s Utility Network and several other internal and external sources to meet the strict data specifications for the DIMP and TIMP software solutions.
Enabling BIM / GIS integrations with Other Systems with FME
Enabling BIM / GIS integrations with Other Systems with FMESafe SoftwareJacobs has successfully utilized FME to tackle the complexities of integrating diverse data sources in a confidential $1 billion campus improvement project. The project aimed to create a comprehensive digital twin by merging Building Information Modeling (BIM) data, Construction Operations Building Information Exchange (COBie) data, and various other data sources into a unified Geographic Information System (GIS) platform. The challenge lay in the disparate nature of these data sources, which were siloed and incompatible with each other, hindering efficient data management and decision-making processes.
To address this, Jacobs leveraged FME to automate the extraction, transformation, and loading (ETL) of data between ArcGIS Indoors and IBM Maximo. This process ensured accurate transfer of maintainable asset and work order data, creating a comprehensive 2D and 3D representation of the campus for Facility Management. FME's server capabilities enabled real-time updates and synchronization between ArcGIS Indoors and Maximo, facilitating automatic updates of asset information and work orders. Additionally, Survey123 forms allowed field personnel to capture and submit data directly from their mobile devices, triggering FME workflows via webhooks for real-time data updates. This seamless integration has significantly enhanced data management, improved decision-making processes, and ensured data consistency across the project lifecycle.
“From Enterprise to Makers: Driving Vision AI Innovation at the Extreme Edge,...
“From Enterprise to Makers: Driving Vision AI Innovation at the Extreme Edge,...Edge AI and Vision AllianceFor the full video of this presentation, please visit: https://www.edge-ai-vision.com/2025/06/from-enterprise-to-makers-driving-vision-ai-innovation-at-the-extreme-edge-a-presentation-from-sony-semiconductor-solutions/
Amir Servi, Edge Deep Learning Product Manager at Sony Semiconductor Solutions, presents the “From Enterprise to Makers: Driving Vision AI Innovation at the Extreme Edge” tutorial at the May 2025 Embedded Vision Summit.
Sony’s unique integrated sensor-processor technology is enabling ultra-efficient intelligence directly at the image source, transforming vision AI for enterprises and developers alike. In this presentation, Servi showcases how the AITRIOS platform simplifies vision AI for enterprises with tools for large-scale deployments and model management.
Servi also highlights his company’s collaboration with Ultralytics and Raspberry Pi, which brings YOLO models to the developer community, empowering grassroots innovation. Whether you’re scaling vision AI for industry or experimenting with cutting-edge tools, this presentation will demonstrate how Sony is accelerating high-performance, energy-efficient vision AI for all.
PyCon SG 25 - Firecracker Made Easy with Python.pdf
PyCon SG 25 - Firecracker Made Easy with Python.pdfMuhammad Yuga NugrahaExplore the ease of managing Firecracker microVM with the firecracker-python. In this session, I will introduce the basics of Firecracker microVM and demonstrate how this custom SDK facilitates microVM operations easily. We will delve into the design and development process behind the SDK, providing a behind-the-scenes look at its creation and features. While traditional Firecracker SDKs were primarily available in Go, this module brings a simplicity of Python to the table.
FIDO Seminar: Targeting Trust: The Future of Identity in the Workforce.pptx
FIDO Seminar: Targeting Trust: The Future of Identity in the Workforce.pptxFIDO AllianceFIDO Seminar: Targeting Trust: The Future of Identity in the Workforce
Connecting Data and Intelligence: The Role of FME in Machine Learning
Connecting Data and Intelligence: The Role of FME in Machine LearningSafe SoftwareIn this presentation, we want to explore powerful data integration and preparation for Machine Learning. FME is known for its ability to manipulate and transform geospatial data, connecting diverse data sources into efficient and automated workflows. By integrating FME with Machine Learning techniques, it is possible to transform raw data into valuable insights faster and more accurately, enabling intelligent analysis and data-driven decision making.
Turning the Page – How AI is Exponentially Increasing Speed, Accuracy, and Ef...
Turning the Page – How AI is Exponentially Increasing Speed, Accuracy, and Ef...Impelsys Inc.Artificial Intelligence (AI) has become a game-changer in content creation, automating tasks that were once very time-consuming and labor-intensive. AI-powered tools are now capable of generating high-quality articles, blog posts, and even poetry by analyzing large datasets of text and producing human-like writing.
However, AI’s influence on content generation is not limited to text; it has also made advancements in multimedia content, such as image, video, and audio generation. AI-powered tools can now transform raw images and footage into visually stunning outputs, and are all set to have a profound impact on the publishing industry.
FIDO Seminar: New Data: Passkey Adoption in the Workforce.pptx
FIDO Seminar: New Data: Passkey Adoption in the Workforce.pptxFIDO AllianceFIDO Seminar: New Data: Passkey Adoption in the Workforce
Improving Data Integrity: Synchronization between EAM and ArcGIS Utility Netw...
Improving Data Integrity: Synchronization between EAM and ArcGIS Utility Netw...Safe SoftwareUtilities and water companies play a key role in the creation of clean drinking water. The creation and maintenance of clean drinking water is becoming a critical problem due to pollution and pressure on the environment. A lot of data is necessary to create clean drinking water. For fieldworkers, two types of data are key: Asset data in an asset management system (EAM for example) and Geographic data in a GIS (ArcGIS Utility Network ). Keeping this type of data up to date and in sync is a challenge for many organizations, leading to duplicating data and creating a bulk of extra attributes and data to keep everything in sync. Using FME, it is possible to synchronize Enterprise Asset Management (EAM) data with the ArcGIS Utility Network in real time. Changes (creation, modification, deletion) in ArcGIS Pro are relayed to EAM via FME, and vice versa. This ensures continuous synchronization of both systems without daily bulk updates, minimizes risks, and seamlessly integrates with ArcGIS Utility Network services. This presentation focuses on the use of FME at a Dutch water company, to create a sync between the asset management and GIS.
Securing Account Lifecycles in the Age of Deepfakes.pptx
Securing Account Lifecycles in the Age of Deepfakes.pptxFIDO AllianceSecuring Account Lifecycles in the Age of Deepfakes
9-1-1 Addressing: End-to-End Automation Using FME
9-1-1 Addressing: End-to-End Automation Using FMESafe SoftwareThis session will cover a common use case for local and state/provincial governments who create and/or maintain their 9-1-1 addressing data, particularly address points and road centerlines. In this session, you'll learn how FME has helped Shelby County 9-1-1 (TN) automate the 9-1-1 addressing process; including automatically assigning attributes from disparate sources, on-the-fly QAQC of said data, and reporting. The FME logic that this presentation will cover includes: Table joins using attributes and geometry, Looping in custom transformers, Working with lists and Change detection.
Tech-ASan: Two-stage check for Address Sanitizer - Yixuan Cao.pdf
Tech-ASan: Two-stage check for Address Sanitizer - Yixuan Cao.pdfcaoyixuan2019A presentation at Internetware 2025.
Security Tips for Enterprise Azure Solutions
Security Tips for Enterprise Azure SolutionsMichele Leroux BustamanteDelivering solutions to Azure may involve a variety of architecture patterns involving your applications, APIs data and associated Azure resources that comprise the solution. This session will use reference architectures to illustrate the security considerations to protect your Azure resources and data, how to achieve Zero Trust, and why it matters. Topics covered will include specific security recommendations for types Azure resources and related network security practices. The goal is to give you a breadth of understanding as to typical security requirements to meet compliance and security controls in an enterprise solution.
War_And_Cyber_3_Years_Of_Struggle_And_Lessons_For_Global_Security.pdf
War_And_Cyber_3_Years_Of_Struggle_And_Lessons_For_Global_Security.pdfbiswajitbanerjee38
"Database isolation: how we deal with hundreds of direct connections to the d...
"Database isolation: how we deal with hundreds of direct connections to the d...Fwdays
FME for Distribution & Transmission Integrity Management Program (DIMP & TIMP)
FME for Distribution & Transmission Integrity Management Program (DIMP & TIMP)Safe Software
Enabling BIM / GIS integrations with Other Systems with FME
Enabling BIM / GIS integrations with Other Systems with FMESafe Software
“From Enterprise to Makers: Driving Vision AI Innovation at the Extreme Edge,...
“From Enterprise to Makers: Driving Vision AI Innovation at the Extreme Edge,...Edge AI and Vision Alliance
PyCon SG 25 - Firecracker Made Easy with Python.pdf
PyCon SG 25 - Firecracker Made Easy with Python.pdfMuhammad Yuga Nugraha
ReSTIR [DI]: Spatiotemporal reservoir resampling for real-time ray tracing ...
ReSTIR [DI]: Spatiotemporal reservoir resampling for real-time ray tracing ...revolcs10
FIDO Seminar: Targeting Trust: The Future of Identity in the Workforce.pptx
FIDO Seminar: Targeting Trust: The Future of Identity in the Workforce.pptxFIDO Alliance
Connecting Data and Intelligence: The Role of FME in Machine Learning
Connecting Data and Intelligence: The Role of FME in Machine LearningSafe Software
FIDO Alliance Seminar State of Passkeys.pptx
FIDO Alliance Seminar State of Passkeys.pptxFIDO Alliance
Turning the Page – How AI is Exponentially Increasing Speed, Accuracy, and Ef...
Turning the Page – How AI is Exponentially Increasing Speed, Accuracy, and Ef...Impelsys Inc.
FIDO Seminar: New Data: Passkey Adoption in the Workforce.pptx
FIDO Seminar: New Data: Passkey Adoption in the Workforce.pptxFIDO Alliance
Improving Data Integrity: Synchronization between EAM and ArcGIS Utility Netw...
Improving Data Integrity: Synchronization between EAM and ArcGIS Utility Netw...Safe Software
Cyber Defense Matrix Workshop - RSA Conference
Cyber Defense Matrix Workshop - RSA ConferencePriyanka Aash
Securing Account Lifecycles in the Age of Deepfakes.pptx
Securing Account Lifecycles in the Age of Deepfakes.pptxFIDO Alliance
9-1-1 Addressing: End-to-End Automation Using FME
9-1-1 Addressing: End-to-End Automation Using FMESafe Software
Tech-ASan: Two-stage check for Address Sanitizer - Yixuan Cao.pdf
Tech-ASan: Two-stage check for Address Sanitizer - Yixuan Cao.pdfcaoyixuan2019
Security Tips for Enterprise Azure Solutions
Security Tips for Enterprise Azure SolutionsMichele Leroux Bustamante
Ad
Developing “RESTful transactions” with Apache Sling
- 1. APACHE SLING & FRIENDS TECH MEETUP BERLIN, 23-25 SEPTEMBER 2013 “RESTful transactions” with Apache Sling Şenol Taş
- 2. About adaptTo() 2013 2 § My Name is Şenol Taş § Senior Computer Scientist § Adobe in Basel, Switzerland @thelabertasch
- 3. adaptTo() 2013 3 Why such a boring Topic?
- 4. Because websites are… adaptTo() 2013 4 § No longer simple advertisement platforms § Not only “online Business cards” § Not a “nice to have” medium § Not a “Playground” § …..
- 5. Because websites are… adaptTo() 2013 5 § Serious business § Make $$$ § Complex § MUST have § “Real” Applications
- 6. adaptTo() 2013 6 Your Website IS THE Application
- 7. Let’s…. adaptTo() 2013 7 § Find out “what is a transaction?” § Quick reminder about REST § How do this two concepts work together?
- 8. adaptTo() 2013 8 What are Transactions?
- 9. What are Transactions? adaptTo() 2013 9
- 10. adaptTo() 2012 10 “An input message to a computer system that must be dealt with as a single unit of work”
- 11. What are Transactions? adaptTo() 2013 11 § begin transaction § debit checking account § credit savings account § update history log § commit transaction
- 12. What are Transactions? adaptTo() 2013 12 § Late 70s: Jim Gray defined the semantic of reliable transactions § Early 80s: Andreas Reuter and Theo Härder defined the acronym “ACID” in their paper “Principles of Transaction- Oriented Database Recovery”
- 13. ACID adaptTo() 2013 13 § Atomicity § Consistency § Isolation § Durability
- 14. How do tools like hybernate help? adaptTo() 2013 14
- 15. adaptTo() 2013 15 What is REST?
- 16. What is REST? adaptTo() 2013 16 § Representational State Transfer § Stateless § Client-server § Cachable § Scalable § …..
- 17. What is REST? adaptTo() 2013 17 § So? How does this work together with transactions?
- 18. adaptTo() 2013 18 REST and transaction is a oxymoron
- 19. REST and transactions adaptTo() 2013 19 § Atomicity § Consistency § Isolation § Durability
- 20. What are the challenges? adaptTo() 2013 20 § HTTP REQUEST – RESPONSE PATTERN § STATELESS § …..?
- 21. Change your mindset… adaptTo() 2013 21 § Not everything has to be done in one request § If you are using POST.jsp or similar in Sling, most likely something is wrong § Events and Observations are your friends § Use the full power of the Sling Default Post and GET Servlet
- 22. Remember the cheat sheet from Lars? adaptTo() 2013 22
- 23. Example adaptTo() 2013 23 § Resource: /home/senol/profile § Begin transaction § change interests § Commit transaction
- 24. Begin Transaction adaptTo() 2013 24 § Copy the node /home/senol/profile to /home/senol/transactions/profile/*
- 25. Change interests adaptTo() 2013 25 § Update with regular post request
- 26. Commit transaction adaptTo() 2012 26 § With observation or events § Directly
- 27. Things of interest adaptTo() 2012 27 § Communicating with services layer § Distributed transactions § Nested transactions § Locking… § Using Adobe CQ? § Have a look at the Workflow Launcher!
- 28. adaptTo() 2013 28 Thank you and have a RESTful Day!