Adobe Experience Manager Flashcards
What is NoSQL ?
A NoSQL (often interpreted as Not Only SQL) database provides a mechanism for storage and retrieval of data that is modeled in means other than the tabular relations used in relational databases. Motivations for this approach include simplicity of design, horizontal scaling and finer control over availability. SQL (Structured Query Language) is a special-purpose programming language designed for managing data held in a relational database management system (RDBMS), or for stream processing in a relational data stream management system (RDSMS).
What is Restful architecture?
Representational state transfer (REST) is an abstraction of the architecture of the World Wide Web; more precisely, REST is an architectural style consisting of a coordinated set of architectural constraints applied to components, connectors, and data elements, within a distributed hypermedia system. REST ignores the details of component implementation and protocol syntax in order to focus on the roles of components, the constraints upon their interaction with other components, and their interpretation of significant data elements.[1][2] The term representational state transfer was introduced and defined in 2000 by Roy Fielding in his doctoral dissertation at UC Irvine.[1][3] REST has been applied to describe desired web architecture, to identify existing problems, to compare alternative solutions and to ensure that protocol extensions would not violate the core constraints that make the web successful. Fielding developed REST in collaboration with his colleagues during the same period he worked on HTTP 1.1 and Uniform Resource Identifiers (URI).[4][5][6] The REST architectural style is also applied to the development of web services.[7] One can characterize web services as “RESTful” if they conform to the constraints described in the architectural constraints section.[8] See the applied to web services section if you are only interested in the application of REST to web APIs.
What are the Multi Site Manager capabilities?
Multi Site Manager (MSM) enables you to
- easily manage multiple web sites that share common content.
- define relations between the sites so that content changes in one site are automatically replicated in other sites.
- reduce the time it takes to manage your websites
- increase the re-use of common content:
- Efficiently manage different language versions of a website.
- Automatically update one or more sites based on a source site:
- Enforce a common base structure and use common content across multiple sites.
- Maximize the use of available resources.
- Maintain a common look and feel.
- Focus efforts on managing the content that differs between the sites.
The content and structure that a site inherits from the source site can be managed at a page and paragraph level. Generally, using MSM involves performing the following tasks:
- Identifying the source content.
- Identifying the location of the copy.
- Configuring what items of source content are automatically updated in the copy.
- Configuring when content updates occur in the copy.
Which Adobe Marketing Cloud solution uses OSGi?
What is it?
OSGiは何ですか
どのAMCソリューションで使われているか
スタンドアロンの Java/VM 環境に欠けている完全で動的なコンポーネントモデルを実装している。アプリケーションソフトウェアや（「バンドル; bundle」形式で配布される）コンポーネントは遠隔からインストール・起動・停止・（リブートせずに）アンインストールできる。Javaのパッケージやクラスの管理は詳細に規定されている。ライフサイクル管理は、遠隔から管理ポリシーをダウンロードすることでAPIを経由して行われる。サービスレジストリにより、バンドルが新たなサービスや消滅したサービスを自動検出して適切に対応する。
The OSGi (Open Service Gateway initiative) specification describes a modular system and a service platform for the Java programming language that implements a complete and dynamic component model, something that does not exist in standalone Java/VM environments.
Applications or components, coming in the form of bundles for deployment, can be remotely installed, started, stopped, updated, and uninstalled without requiring a reboot; management of Java packages/classes is specified in great detail. Application life cycle management is implemented via APIs that allow for remote downloading of management policies. The service registry allows bundles to detect the addition of new services, or the removal of services, and adapt accordingly.
The OSGi specifications have evolved beyond the original focus of service gateways, and are now used in applications ranging from mobile phones to the open-source Eclipse IDE. Other application areas include automobiles, industrial automation, building automation, PDAs, grid computing, entertainment, fleet management and application servers.
AEM & OSGi : (from RSG)
“Out of the box, AEM is a Java application that uses Adobe’s own CRX (Content Repository eXtreme) as the repository, Apache Felix (the OSGi implementation) as a services container, and Java Server Pages (or a new templating framework called “Sightly”) exposed through a custom servlet engine — plus application logic implemented in custom Java Servlets and OSGi Services. Note that you can substitute COTS products for many of the open source pieces. Many customers use Tomcat as the servlet container, and Adobe publishes detailed instructions for installing AEM into JBoss, WebSphere, and WebLogic appservers.
Abstraction of the storage layer is one of the prime motivations behind JCR: Applications don’t have to know or care about the underlying storage. Adobe offers connectors to Documentum, SharePoint, and other popular repositories, so that in many cases, organizations can keep their physical data exactly where it is, and still use AEM to provide a repository view into the content, with versioning and other services provided via CRX. This is a major selling point for organizations that have made a significant prior investment in other repositories but who want a WCM system to manage it all.”
Who is Roy Fielding ?
Roy Thomas Fielding (born 1965) is an American computer scientist,[1] one of the principal authors of the HTTPspecification, an authority on computer network architecture[2] and co-founder of the Apache HTTP Server project.
In 1999, he was named to the MIT Technology Review TR100 as one of the top 100 innovators in the world under the age of 35.[3] He received a doctorate from the University of California, Irvine in 2000.
Architectural Styles and the Design of Network-based Software Architectures, Fielding’s doctoral dissertation, describes Representational State Transfer (REST) as a key architectural principle of the World Wide Web, and received a large amount of attention. People now frequently hold up REST as an approach to developing Web services,[4] as an alternative to other distributed-computing specifications such as SOAP. Fielding has also been heavily involved in the development of HTML and Uniform Resource Identifiers. Fielding was a co-founder of the Apache HTTP Server project[5][6] and was a member of the interim OpenSolaris Boards until he resigned from the community in 2008, disappointed that Sun would not let the community influence development decisions.[7] He was the chair of the Apache Software Foundation for its first three years and was a member of its board of directors until May 2014.[8] Currently he works as a Principal Scientist at Adobe Systems in San Jose, California.
Who is David Nuescheler?
David Nuescheler, VP of Enterprise Technology at Adobe (former Day CTO and cofounder) — spearheaded JSR 170, and was the spec lead on version 2.0 of that specification, better known as JSR 283 (or simply JCR, the Java Content Repositories)
