Following the 2010 TYPO3 conference in Dallas, Cast Iron Coding decided to drop development of its internal MVC framework and base all future development on ExtBase. In the past year, we have encountered challenges with ExtBase as well as opportunities, and the purpose of this talk will be to share with the audience the lessons we've learned as well as some of our successes. A large part of the talk will be devoted to showing what's possible with ExtBase in real-world settings, including discussions about
1. using ExtBase with an Oracle database backend and DBAL/ADOB
2. utilizing ExtBase in backend scheduler tasks
3. moving to ExtBase, ExtJS, and ExtDirect for backend module development
4. Replacing HTML elements in the backend with FLUID HTML elements
5. Moving from TemplaVoila to fluid-based page templates; and
6. Our experience using ExtBase with an AJAX-driven frontend plugin that allows users to search data stored in the client's Salesforce account.
Rather than go into great technical detail, I will discuss what we learned from these various examples. However, I will provide audience members with some code examples that may be useful for future projects of their own. Finally, I will discuss how the switch to ExtBase impacted our business from a productivity/revenue standpoint, and discuss what sorts of projects we see as a good fit for ExtBase.
The document discusses sustainable competitive advantage through innovation. It introduces Herr Rosenstiel and Herr Willman to discuss Plex's growth and ability to facilitate business processes through its ERP software. The presentation outlines Plex's unique development process, infrastructure improvement process, and proven engagement process. It provides an overview of Plex's customers, industries served, and growth rate. The document also reviews Plex's work with IMS Gear to automate and improve processes around order to cash, procure to pay, and other key functions.
The document discusses best practices for consumer-brand social media and provides three case studies as examples. It recommends following a five phase methodology for social media strategy that assesses needs, develops data collection and strategy, provides feedback, implements tactics, and re-evaluates over 12-24 months. All data and tools should align between analytics and customer relationship management. The three case studies show successful social media implementations for a visitors bureau, tea company, and book publisher that increased engagement, sales, and author feedback.
Chatham Economic Development Corporation 2015-2020 Strategic Action Agenda presentation, given at the April 2015 joint elected officials meeting at Central Carolina Community College.
To view the full strategic plan, visit www.chathamedc.org. Printed versions are available at the EDC office.
The document discusses sustainable competitive advantage through innovation. It introduces Herr Rosenstiel and Herr Willman to discuss Plex's growth and ability to facilitate business processes through its ERP software. The presentation outlines Plex's unique development process, infrastructure improvement process, and proven engagement process. It provides an overview of Plex's customers, industries served, and growth rate. The document also reviews Plex's work with IMS Gear to automate and improve processes around order to cash, procure to pay, and other key functions.
The document discusses best practices for consumer-brand social media and provides three case studies as examples. It recommends following a five phase methodology for social media strategy that assesses needs, develops data collection and strategy, provides feedback, implements tactics, and re-evaluates over 12-24 months. All data and tools should align between analytics and customer relationship management. The three case studies show successful social media implementations for a visitors bureau, tea company, and book publisher that increased engagement, sales, and author feedback.
Chatham Economic Development Corporation 2015-2020 Strategic Action Agenda presentation, given at the April 2015 joint elected officials meeting at Central Carolina Community College.
To view the full strategic plan, visit www.chathamedc.org. Printed versions are available at the EDC office.
This document summarizes a Pakistani blogger's experience writing about mobile technologies. It outlines the blogger's history starting blogs in 2006 focusing on mobile topics. It lists over 50 sources the blogger draws information and ideas from. The blogger emphasizes the importance of knowledge, innovation, and time for a successful tech blog.
Theme 2 the fear place vocabulary flash cards mod2013PEDH
The document is a vocabulary exercise that provides sample sentences for key words and asks the reader to determine the definitions of those words based on context clues. It includes 14 vocabulary words - adventure, cautious, concentrate, discomfort, dismayed, excitement, immobile, stamina, terrified, unsure, and their definitions. The purpose is to help readers learn new words and their meanings in different contexts.
The document defines and provides examples of several words related to wildlife and the natural environment. It defines the words abundant, aggressive, caribou, subservience, territory, tundra, wariness, and wilderness. For each word it gives a concise definition and includes a related photo to illustrate the term.
There are approximately 1.5 billion Muslims worldwide who come from a vast range of races, nationalities, cultures, and geographic regions. Muslims are united by their common Islamic faith and beliefs. The world's largest Muslim community is in Indonesia, which has over 87% Muslims. Significant Muslim populations can also be found throughout Asia, Africa, as well as minorities in places like Europe, North America, South America, China, and the former Soviet Union.
Q1 2009 Earning Report of Du Pont E I De Nemoursguestc4fcf72
- DuPont reported first quarter 2009 earnings of $0.54 per share, in line with guidance, with strong performance in agriculture and pharmaceuticals offsetting declines in industrial demand.
- In response to weak global economic conditions, DuPont increased its 2009 cost reduction goal to $1 billion and reduced planned capital expenditures by an additional $200 million to $1.4 billion.
- DuPont revised its full-year 2009 earnings outlook to a range of $1.70 to $2.10 per share, expecting difficult market conditions to continue except in global agriculture markets. The company will focus on aggressively reducing costs and capital expenditures.
This document discusses project management and related topics. It begins with an agenda for the document, then defines what a project is, discusses the history and need for project management. It introduces key project management concepts like the work breakdown structure (WBS), triple constraint/project management triangle of balancing scope, time and cost, and critical path method. The document emphasizes learning project management essentials and provides examples to illustrate core concepts. It concludes by recommending further resources for learning more about project management.
Open Content in Kalimantan: Wikipedia and Open Street Map for Transparency Re...Wikimedia Indonesia
Making All Voices Count Open Content in Kalimantan: Wikipedia & Open Street Map for Transparency
http://www.makingallvoicescount.org/project/open-content-in-kalimantan-wikipedia-openstreetmap-for-transparency/
- Venkat is the DevOps Practice Leader at NewtGlobal with over 16 years of experience delivering enterprise projects.
- The webinar will discuss microservices and include a Q&A session. Questions can be asked in the chat window.
- Moving from monolithic to microservices architecture allows individual components to be independently deployed, scaled, and developed using different technologies. This improves agility but also increases complexity.
Following topics will be addressed into presentation:
Motivation and goals of splitting monolith application
Criteria and markers to start splitting process. Is it necessary at all?
Optimal order of extracting microservices
How organize the whole process in closed iterative steps?
What can be done with common libraries and shared code?
Options for technology and deployment of target microservices
How organize and motivate the teams and convince management?
Speaker Bio
Andrei is a Software Architect in VMWare Tanzu Labs. The areas of his interest are REST API design, Microservices, Cloud, resilient distributed systems, security and agile development. Andrei is PMC and committer of Apache CXF and committer of Syncope projects.
Dev Ops for systems of record - Talk at Agile Australia 2015Mirco Hering
Mirco Hering is a DevOps and Agile lead with over 10 years of experience improving IT delivery through automation, methodology, and innovation. The document discusses applying DevOps principles to systems of record like packaged software, non-custom code, and older custom code. It outlines challenges in automating builds, deployments, testing and integrating these systems. It provides examples of automating merges and traceability for a Siebel system to help systems of record adopt DevOps practices and continuous delivery.
The document discusses different dependency injection styles in Spring, including external configuration via XML files versus internal configuration via annotations. It outlines seven key characteristics to consider when choosing a DI style: external vs internal configuration, explicit vs implicit wiring, type safety, non-invasiveness, portability, configurability of third party components, and available tooling support. The document then analyzes each characteristic in more detail and provides examples to illustrate different styles.
The document discusses continuous deployment for machine learning projects using Bodywork. Bodywork enables CI/CD for ML projects by allowing teams to define workflows in a Git repository that can deploy models, pipelines, and services to Kubernetes. It tackles common deployment challenges for ML like managing container images and infrastructure, and allows teams to focus on their code. The talk includes demos of sample ML projects deployed with Bodywork, like serving a model with a REST API and a train-and-serve pipeline.
This document compares and contrasts microservice architecture (MSA) and service-oriented architecture (SOA). SOA defines application components as loosely coupled services that communicate over a network, while MSA develops applications as suites of small services communicating via lightweight mechanisms like REST. The document also discusses Netflix's transition from a monolithic to a microservices architecture led by Adrian Cockcroft, highlighting benefits like speed, autonomy, and flexibility.
Facilitating continuous delivery in a FinTech world with Salt, Jenkins, Nexus...Chocolatey Software
Michel Buczynski, DevOps Coach at TD Securities: Most of the developments in FinTech are hybrid, they rely of both legacy and modern or more agile technologies. We will show how Chocolatey Business Edition can become the centerpiece of a CD pipeline. We will explain in detail how to integrate Chocolatey with Jenkins, Nexus, SaltStack to deploy micro-services both on legacy and cloud platform. We will show how the Chocolatey Agent (Self-Service Installer) with the help of Nexus repos, permit a secure continuous deployment of custom desktop applications on users' workstations and make the use of Citrix XenApp servers almost obsolete. Show how the Package Builder, Synchronizer, Downloader and Internalize simplify the day to day operation of developers.
Facilitating continuous delivery in a FinTech world with Salt, Jenkins, Nexus...Michel Buczynski
Michel Buczynski is a DevOps coach working at TD Securities to help implement continuous delivery tools and standardize workflows. He discussed his team's journey from no version control or automation to using tools like Jenkins, SaltStack, Nexus, and Chocolatey. His goals are to produce software efficiently using these tools and coach his team on their use. He emphasized standardizing processes, cleaning up repositories, and enforcing new workflows to help with adoption. He also demonstrated some of the tools in a live session.
This document summarizes an open house event about DevOps hosted by Prashant P Beniwal. The event will take place on September 17th from 7-8 pm. The agenda includes introductions, an overview of DevOps, a pipeline demo, and a question period. Prashant P Beniwal has 20 years of IT experience and is a certified DevOps trainer. He will discuss DevOps principles like breaking down silos between teams and enabling rapid feedback. The event will also promote Prashant's Certified Professional DevOps Foundation certification and upcoming training programs.
16370 cics project opening and project update fnick_garrod
This document provides an overview and agenda for the CICS Project Opening and Project Update session. It includes:
- An introduction from Dave Jeffries, the CICS Director, and Andy Bates, the CICS TS Product Manager.
- A forecast of key topics to be covered at the SHARE conference related to CICS, including Cloud & DevOps, Java & Liberty, Mobile & APIs, Cost Optimization, and Generation z & Core Skills.
- An outline of upcoming releases, betas, and skills certifications for CICS Transaction Server.
This document summarizes a Pakistani blogger's experience writing about mobile technologies. It outlines the blogger's history starting blogs in 2006 focusing on mobile topics. It lists over 50 sources the blogger draws information and ideas from. The blogger emphasizes the importance of knowledge, innovation, and time for a successful tech blog.
Theme 2 the fear place vocabulary flash cards mod2013PEDH
The document is a vocabulary exercise that provides sample sentences for key words and asks the reader to determine the definitions of those words based on context clues. It includes 14 vocabulary words - adventure, cautious, concentrate, discomfort, dismayed, excitement, immobile, stamina, terrified, unsure, and their definitions. The purpose is to help readers learn new words and their meanings in different contexts.
The document defines and provides examples of several words related to wildlife and the natural environment. It defines the words abundant, aggressive, caribou, subservience, territory, tundra, wariness, and wilderness. For each word it gives a concise definition and includes a related photo to illustrate the term.
There are approximately 1.5 billion Muslims worldwide who come from a vast range of races, nationalities, cultures, and geographic regions. Muslims are united by their common Islamic faith and beliefs. The world's largest Muslim community is in Indonesia, which has over 87% Muslims. Significant Muslim populations can also be found throughout Asia, Africa, as well as minorities in places like Europe, North America, South America, China, and the former Soviet Union.
Q1 2009 Earning Report of Du Pont E I De Nemoursguestc4fcf72
- DuPont reported first quarter 2009 earnings of $0.54 per share, in line with guidance, with strong performance in agriculture and pharmaceuticals offsetting declines in industrial demand.
- In response to weak global economic conditions, DuPont increased its 2009 cost reduction goal to $1 billion and reduced planned capital expenditures by an additional $200 million to $1.4 billion.
- DuPont revised its full-year 2009 earnings outlook to a range of $1.70 to $2.10 per share, expecting difficult market conditions to continue except in global agriculture markets. The company will focus on aggressively reducing costs and capital expenditures.
This document discusses project management and related topics. It begins with an agenda for the document, then defines what a project is, discusses the history and need for project management. It introduces key project management concepts like the work breakdown structure (WBS), triple constraint/project management triangle of balancing scope, time and cost, and critical path method. The document emphasizes learning project management essentials and provides examples to illustrate core concepts. It concludes by recommending further resources for learning more about project management.
Open Content in Kalimantan: Wikipedia and Open Street Map for Transparency Re...Wikimedia Indonesia
Making All Voices Count Open Content in Kalimantan: Wikipedia & Open Street Map for Transparency
http://www.makingallvoicescount.org/project/open-content-in-kalimantan-wikipedia-openstreetmap-for-transparency/
- Venkat is the DevOps Practice Leader at NewtGlobal with over 16 years of experience delivering enterprise projects.
- The webinar will discuss microservices and include a Q&A session. Questions can be asked in the chat window.
- Moving from monolithic to microservices architecture allows individual components to be independently deployed, scaled, and developed using different technologies. This improves agility but also increases complexity.
Following topics will be addressed into presentation:
Motivation and goals of splitting monolith application
Criteria and markers to start splitting process. Is it necessary at all?
Optimal order of extracting microservices
How organize the whole process in closed iterative steps?
What can be done with common libraries and shared code?
Options for technology and deployment of target microservices
How organize and motivate the teams and convince management?
Speaker Bio
Andrei is a Software Architect in VMWare Tanzu Labs. The areas of his interest are REST API design, Microservices, Cloud, resilient distributed systems, security and agile development. Andrei is PMC and committer of Apache CXF and committer of Syncope projects.
Dev Ops for systems of record - Talk at Agile Australia 2015Mirco Hering
Mirco Hering is a DevOps and Agile lead with over 10 years of experience improving IT delivery through automation, methodology, and innovation. The document discusses applying DevOps principles to systems of record like packaged software, non-custom code, and older custom code. It outlines challenges in automating builds, deployments, testing and integrating these systems. It provides examples of automating merges and traceability for a Siebel system to help systems of record adopt DevOps practices and continuous delivery.
The document discusses different dependency injection styles in Spring, including external configuration via XML files versus internal configuration via annotations. It outlines seven key characteristics to consider when choosing a DI style: external vs internal configuration, explicit vs implicit wiring, type safety, non-invasiveness, portability, configurability of third party components, and available tooling support. The document then analyzes each characteristic in more detail and provides examples to illustrate different styles.
The document discusses continuous deployment for machine learning projects using Bodywork. Bodywork enables CI/CD for ML projects by allowing teams to define workflows in a Git repository that can deploy models, pipelines, and services to Kubernetes. It tackles common deployment challenges for ML like managing container images and infrastructure, and allows teams to focus on their code. The talk includes demos of sample ML projects deployed with Bodywork, like serving a model with a REST API and a train-and-serve pipeline.
This document compares and contrasts microservice architecture (MSA) and service-oriented architecture (SOA). SOA defines application components as loosely coupled services that communicate over a network, while MSA develops applications as suites of small services communicating via lightweight mechanisms like REST. The document also discusses Netflix's transition from a monolithic to a microservices architecture led by Adrian Cockcroft, highlighting benefits like speed, autonomy, and flexibility.
Facilitating continuous delivery in a FinTech world with Salt, Jenkins, Nexus...Chocolatey Software
Michel Buczynski, DevOps Coach at TD Securities: Most of the developments in FinTech are hybrid, they rely of both legacy and modern or more agile technologies. We will show how Chocolatey Business Edition can become the centerpiece of a CD pipeline. We will explain in detail how to integrate Chocolatey with Jenkins, Nexus, SaltStack to deploy micro-services both on legacy and cloud platform. We will show how the Chocolatey Agent (Self-Service Installer) with the help of Nexus repos, permit a secure continuous deployment of custom desktop applications on users' workstations and make the use of Citrix XenApp servers almost obsolete. Show how the Package Builder, Synchronizer, Downloader and Internalize simplify the day to day operation of developers.
Facilitating continuous delivery in a FinTech world with Salt, Jenkins, Nexus...Michel Buczynski
Michel Buczynski is a DevOps coach working at TD Securities to help implement continuous delivery tools and standardize workflows. He discussed his team's journey from no version control or automation to using tools like Jenkins, SaltStack, Nexus, and Chocolatey. His goals are to produce software efficiently using these tools and coach his team on their use. He emphasized standardizing processes, cleaning up repositories, and enforcing new workflows to help with adoption. He also demonstrated some of the tools in a live session.
This document summarizes an open house event about DevOps hosted by Prashant P Beniwal. The event will take place on September 17th from 7-8 pm. The agenda includes introductions, an overview of DevOps, a pipeline demo, and a question period. Prashant P Beniwal has 20 years of IT experience and is a certified DevOps trainer. He will discuss DevOps principles like breaking down silos between teams and enabling rapid feedback. The event will also promote Prashant's Certified Professional DevOps Foundation certification and upcoming training programs.
16370 cics project opening and project update fnick_garrod
This document provides an overview and agenda for the CICS Project Opening and Project Update session. It includes:
- An introduction from Dave Jeffries, the CICS Director, and Andy Bates, the CICS TS Product Manager.
- A forecast of key topics to be covered at the SHARE conference related to CICS, including Cloud & DevOps, Java & Liberty, Mobile & APIs, Cost Optimization, and Generation z & Core Skills.
- An outline of upcoming releases, betas, and skills certifications for CICS Transaction Server.
Migrating to Microservices – It's Easier Than You ThinkDevOps.com
Moving from a monolithic architecture to a service-based architecture may look like a daunting task. The good news is it does not need to be. A maturing cloud native tooling market is making it easier to get the job done.
In this webinar, Steve will cover the steps required to move a standard J2EE application from a monolithic architecture to a service based architecture. He will cover tools such as Ngnix, Docker, Kubernetes and DeployHub to manage and configure this new environment. Anyone with an interest in shifting to microservices will benefit from hearing this "roadmap" presentation.
DSC UTeM DevOps Session#1: Intro to DevOps Presentation SlidesDSC UTeM
DevOps has been such a buzzword in the IT field nowadays. If you look into job postings, you might be surprised to find terms like "work with DevOps team", "work in an agile team" etc.
What is DevOps? What is agile? And why all these? 樂
Join us on 24 May 2021, where we have a short session to explore on the events that led to the trend nowadays
We will be exploring on the current trends, tech stacks and the existence of DevOps itself! 朗
Mark this date on your calendar and we'll see you there!
* Note: This is an introductory "brief overview" session that gives you context on our upcoming events.
Slides by KwongTN.
A presentation to explain the microservices architecture, the pro and the cons, with a view on how to migrate from a monolith to a SOA architecture. Also, we'll show the benefits of the microservices architecture also for the frontend side with the microfrontend architecture.
2022 DOI SKILup Days_Google Uses Monorepo, and I Don't - Here's Why.pptxTurja Narayan Chaudhuri
Repository structure is one of the most important decisions that an engineering team needs to make. This decision is typically made at the start of the project when possible.
In most enterprises, teams tend to follow a similar pattern, as to their choice of monorepo VS multi-repo. Google switched to monorepo, which means all their projects and code is stored in a single, large repository.
But which approach should we take - monorepo or multi-repo?
What are the pros/cons of each? Why did I advocate for multi-repo with all clients that I worked with? Are there criteria to help teams decide?
This session will discuss the context, challenges and advantages of each of the two approaches.
Lublin Startup Festival - Mobile Architecture Design PatternsKarol Szmaj
This document discusses mobile app development architecture and design patterns. It covers the out-of-the-box approach using code behind, the model-view-viewmodel (MVVM) pattern, inversion of control (IOC), and command query responsibility segregation (CQRS). It also discusses tools like Fody, Polly, and Cimbalino Toolkit. Tips are provided on using universal apps, Windows 10 XAML, and developing cross-platform with Xamarin. The presentation ends with an invitation for questions.
The document describes the evolution of software development methodologies over time, from the 1950s to the 2000s. It discusses several models including code and fix, waterfall model, spiral model, V-model, and agile methods. The waterfall model was introduced in the 1970s and emphasized sequential development through requirements, design, implementation, testing, integration, and maintenance phases. The spiral model was developed in the 1980s to address limitations of the waterfall model through an iterative, risk-driven approach. The V-model emerged in the 1990s and depicted the relationships between project phases and testing activities.
By,
Krishna Kumar
This very brief talk gives you an overview of how you can contribute to CNCF (Cloud Native Computing Foundation) not just through the code.
How to contribute to cloud native computing foundation (CNCF)Krishna-Kumar
Contribute to cloud native computing foundation - various ways. This is an introductory presentation given in Container conference in Bangalore April 2017 and may help new comers to get in to the CNCF eco system faster.
Ähnlich wie One Year Later: Reflections on Developing with Extbase and Fluid (20)
Communications Mining Series - Zero to Hero - Session 1DianaGray10
This session provides introduction to UiPath Communication Mining, importance and platform overview. You will acquire a good understand of the phases in Communication Mining as we go over the platform with you. Topics covered:
• Communication Mining Overview
• Why is it important?
• How can it help today’s business and the benefits
• Phases in Communication Mining
• Demo on Platform overview
• Q/A
“An Outlook of the Ongoing and Future Relationship between Blockchain Technologies and Process-aware Information Systems.” Invited talk at the joint workshop on Blockchain for Information Systems (BC4IS) and Blockchain for Trusted Data Sharing (B4TDS), co-located with with the 36th International Conference on Advanced Information Systems Engineering (CAiSE), 3 June 2024, Limassol, Cyprus.
Securing your Kubernetes cluster_ a step-by-step guide to success !KatiaHIMEUR1
Today, after several years of existence, an extremely active community and an ultra-dynamic ecosystem, Kubernetes has established itself as the de facto standard in container orchestration. Thanks to a wide range of managed services, it has never been so easy to set up a ready-to-use Kubernetes cluster.
However, this ease of use means that the subject of security in Kubernetes is often left for later, or even neglected. This exposes companies to significant risks.
In this talk, I'll show you step-by-step how to secure your Kubernetes cluster for greater peace of mind and reliability.
Why You Should Replace Windows 11 with Nitrux Linux 3.5.0 for enhanced perfor...SOFTTECHHUB
The choice of an operating system plays a pivotal role in shaping our computing experience. For decades, Microsoft's Windows has dominated the market, offering a familiar and widely adopted platform for personal and professional use. However, as technological advancements continue to push the boundaries of innovation, alternative operating systems have emerged, challenging the status quo and offering users a fresh perspective on computing.
One such alternative that has garnered significant attention and acclaim is Nitrux Linux 3.5.0, a sleek, powerful, and user-friendly Linux distribution that promises to redefine the way we interact with our devices. With its focus on performance, security, and customization, Nitrux Linux presents a compelling case for those seeking to break free from the constraints of proprietary software and embrace the freedom and flexibility of open-source computing.
Removing Uninteresting Bytes in Software FuzzingAftab Hussain
Imagine a world where software fuzzing, the process of mutating bytes in test seeds to uncover hidden and erroneous program behaviors, becomes faster and more effective. A lot depends on the initial seeds, which can significantly dictate the trajectory of a fuzzing campaign, particularly in terms of how long it takes to uncover interesting behaviour in your code. We introduce DIAR, a technique designed to speedup fuzzing campaigns by pinpointing and eliminating those uninteresting bytes in the seeds. Picture this: instead of wasting valuable resources on meaningless mutations in large, bloated seeds, DIAR removes the unnecessary bytes, streamlining the entire process.
In this work, we equipped AFL, a popular fuzzer, with DIAR and examined two critical Linux libraries -- Libxml's xmllint, a tool for parsing xml documents, and Binutil's readelf, an essential debugging and security analysis command-line tool used to display detailed information about ELF (Executable and Linkable Format). Our preliminary results show that AFL+DIAR does not only discover new paths more quickly but also achieves higher coverage overall. This work thus showcases how starting with lean and optimized seeds can lead to faster, more comprehensive fuzzing campaigns -- and DIAR helps you find such seeds.
- These are slides of the talk given at IEEE International Conference on Software Testing Verification and Validation Workshop, ICSTW 2022.
GraphSummit Singapore | The Future of Agility: Supercharging Digital Transfor...Neo4j
Leonard Jayamohan, Partner & Generative AI Lead, Deloitte
This keynote will reveal how Deloitte leverages Neo4j’s graph power for groundbreaking digital twin solutions, achieving a staggering 100x performance boost. Discover the essential role knowledge graphs play in successful generative AI implementations. Plus, get an exclusive look at an innovative Neo4j + Generative AI solution Deloitte is developing in-house.
Sudheer Mechineni, Head of Application Frameworks, Standard Chartered Bank
Discover how Standard Chartered Bank harnessed the power of Neo4j to transform complex data access challenges into a dynamic, scalable graph database solution. This keynote will cover their journey from initial adoption to deploying a fully automated, enterprise-grade causal cluster, highlighting key strategies for modelling organisational changes and ensuring robust disaster recovery. Learn how these innovations have not only enhanced Standard Chartered Bank’s data infrastructure but also positioned them as pioneers in the banking sector’s adoption of graph technology.
Maruthi Prithivirajan, Head of ASEAN & IN Solution Architecture, Neo4j
Get an inside look at the latest Neo4j innovations that enable relationship-driven intelligence at scale. Learn more about the newest cloud integrations and product enhancements that make Neo4j an essential choice for developers building apps with interconnected data and generative AI.
For the full video of this presentation, please visit: https://www.edge-ai-vision.com/2024/06/building-and-scaling-ai-applications-with-the-nx-ai-manager-a-presentation-from-network-optix/
Robin van Emden, Senior Director of Data Science at Network Optix, presents the “Building and Scaling AI Applications with the Nx AI Manager,” tutorial at the May 2024 Embedded Vision Summit.
In this presentation, van Emden covers the basics of scaling edge AI solutions using the Nx tool kit. He emphasizes the process of developing AI models and deploying them globally. He also showcases the conversion of AI models and the creation of effective edge AI pipelines, with a focus on pre-processing, model conversion, selecting the appropriate inference engine for the target hardware and post-processing.
van Emden shows how Nx can simplify the developer’s life and facilitate a rapid transition from concept to production-ready applications.He provides valuable insights into developing scalable and efficient edge AI solutions, with a strong focus on practical implementation.
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
GraphSummit Singapore | The Art of the Possible with Graph - Q2 2024Neo4j
Neha Bajwa, Vice President of Product Marketing, Neo4j
Join us as we explore breakthrough innovations enabled by interconnected data and AI. Discover firsthand how organizations use relationships in data to uncover contextual insights and solve our most pressing challenges – from optimizing supply chains, detecting fraud, and improving customer experiences to accelerating drug discoveries.
Dr. Sean Tan, Head of Data Science, Changi Airport Group
Discover how Changi Airport Group (CAG) leverages graph technologies and generative AI to revolutionize their search capabilities. This session delves into the unique search needs of CAG’s diverse passengers and customers, showcasing how graph data structures enhance the accuracy and relevance of AI-generated search results, mitigating the risk of “hallucinations” and improving the overall customer journey.
Threats to mobile devices are more prevalent and increasing in scope and complexity. Users of mobile devices desire to take full advantage of the features
available on those devices, but many of the features provide convenience and capability but sacrifice security. This best practices guide outlines steps the users can take to better protect personal devices and information.
Cosa hanno in comune un mattoncino Lego e la backdoor XZ?Speck&Tech
ABSTRACT: A prima vista, un mattoncino Lego e la backdoor XZ potrebbero avere in comune il fatto di essere entrambi blocchi di costruzione, o dipendenze di progetti creativi e software. La realtà è che un mattoncino Lego e il caso della backdoor XZ hanno molto di più di tutto ciò in comune.
Partecipate alla presentazione per immergervi in una storia di interoperabilità, standard e formati aperti, per poi discutere del ruolo importante che i contributori hanno in una comunità open source sostenibile.
BIO: Sostenitrice del software libero e dei formati standard e aperti. È stata un membro attivo dei progetti Fedora e openSUSE e ha co-fondato l'Associazione LibreItalia dove è stata coinvolta in diversi eventi, migrazioni e formazione relativi a LibreOffice. In precedenza ha lavorato a migrazioni e corsi di formazione su LibreOffice per diverse amministrazioni pubbliche e privati. Da gennaio 2020 lavora in SUSE come Software Release Engineer per Uyuni e SUSE Manager e quando non segue la sua passione per i computer e per Geeko coltiva la sua curiosità per l'astronomia (da cui deriva il suo nickname deneb_alpha).
Enchancing adoption of Open Source Libraries. A case study on Albumentations.AIVladimir Iglovikov, Ph.D.
Presented by Vladimir Iglovikov:
- https://www.linkedin.com/in/iglovikov/
- https://x.com/viglovikov
- https://www.instagram.com/ternaus/
This presentation delves into the journey of Albumentations.ai, a highly successful open-source library for data augmentation.
Created out of a necessity for superior performance in Kaggle competitions, Albumentations has grown to become a widely used tool among data scientists and machine learning practitioners.
This case study covers various aspects, including:
People: The contributors and community that have supported Albumentations.
Metrics: The success indicators such as downloads, daily active users, GitHub stars, and financial contributions.
Challenges: The hurdles in monetizing open-source projects and measuring user engagement.
Development Practices: Best practices for creating, maintaining, and scaling open-source libraries, including code hygiene, CI/CD, and fast iteration.
Community Building: Strategies for making adoption easy, iterating quickly, and fostering a vibrant, engaged community.
Marketing: Both online and offline marketing tactics, focusing on real, impactful interactions and collaborations.
Mental Health: Maintaining balance and not feeling pressured by user demands.
Key insights include the importance of automation, making the adoption process seamless, and leveraging offline interactions for marketing. The presentation also emphasizes the need for continuous small improvements and building a friendly, inclusive community that contributes to the project's growth.
Vladimir Iglovikov brings his extensive experience as a Kaggle Grandmaster, ex-Staff ML Engineer at Lyft, sharing valuable lessons and practical advice for anyone looking to enhance the adoption of their open-source projects.
Explore more about Albumentations and join the community at:
GitHub: https://github.com/albumentations-team/albumentations
Website: https://albumentations.ai/
LinkedIn: https://www.linkedin.com/company/100504475
Twitter: https://x.com/albumentations
Presentation of the OECD Artificial Intelligence Review of Germany
One Year Later: Reflections on Developing with Extbase and Fluid
1. A Year Later
Reflections on Developing with ExtBase and Fluid
Date: June 10, 2011
Author: Zach Davis, Cast Iron Coding, Inc.
Slide #1 Zach Davis - June 10, 2011 - San Francisco TYPO3 Conference
Friday, June 10, 2011
2. Background
About CIC, about this talk
Background
About Cast Iron Coding and how we came to TYPO3
• Located in Portland, Oregon
• Founded in 2004 with two employees; now at seven employees (six
developers) plus local sub-contractors
• 95% of all sites we build are built with TYPO3
• While we are a full-service agency, CIC’s core competency is
development; we have developed hundreds of TYPO3 extensions for
our clients.
• Our clients are drawn from a variety of industries but we have some
specialization in non-profit and higher education sites
The goal of today’s talk is to share some of our experiences with ExtBase/Fluid and to discuss
specific uses of ExtBase/Fluid that have been helpful on recent projects.
Slide #2 Zach Davis - June 10, 2011 - San Francisco TYPO3 Conference
Friday, June 10, 2011
3. CICMVC
Our first attempt at MVC in TYPO3
CICMVC: Our first attempt at MVC in TYPO3
In 2008, we needed a way to reduce development time and costs to remain competitive with
other open source systems such as Wordpress (for smaller projects) and Drupal or Joomla (for
larger projects)
There were a number of challenges that we experienced working with TYPO3 in 2008 and
2009:
• Low quality extension—hard to configure, lack of Typoscript abstraction, presentation layer hard-coded into code—
extensions in the extension library meant that for most projects we ended up developing custom extensions for clients.
• Consequently, the cost associated with pretty standard features was often too high for clients, especially for smaller clients
on tight budgets
• This made it increasingly more difficult for us to compete with Wordpress , which has increasingly come to be seen as a
viable CMS, on smallish (under 15k) projects.
• Instead of hoping for better extensions in the TER, we chose to devote time to finding a way to a) reduce the time required to
develop extensions and b) increase the amount of code that was reusable between projects (or make sure we were writing
code that was focused on the domain)
Slide #3 Zach Davis - June 10, 2011 - San Francisco TYPO3 Conference
Friday, June 10, 2011
4. CICMVC
Our first attempt at MVC in TYPO3
CICMVC: Our first attempt at MVC in TYPO3
In response to these challenges, CIC developed CICMVC to replace piBase.
CICMVC is a light-weight, high-performance MVC layer that sits on top of piBase. Some parts of
it worked really well for us:
• Few constraints, which isn’t always a bad thing! Because we can ensure quality control in-house, we didn’t need to include
the sorts of constraints that are present in FLUID and ExtBase.
• Therefore, CICMVC uses PHP views—not so popular these days, perhaps, but not much more syntactically difficult than
FLUID, and quite a bit faster.
• Core classes of CICMVC include: controller, model, helper, view, peer, query, form, requests, request filters, exceptions, email
and partials.
• Built-in models and peers for common objects (Digital asset and digital asset peer, user models, countries and states, etc).
• Separate pi classes (pi1, pi2, etc) and page types are used for different output modes (HTML, JSON, XML, etc).
Slide #4 Zach Davis - June 10, 2011 - San Francisco TYPO3 Conference
Friday, June 10, 2011
5. CICMVC
Our first attempt at MVC in TYPO3
CICMVC: Our first attempt at MVC in TYPO3
Some parts of it worked really well for us:
• Database accessed by way of “peer” classes which relied on query objects. In most cases, records could be received easily
without writing much SQL . The query object used arrays to store the query components. In more complicated cases, the
query object and the peer class offer easy, direct access to the underlying TYPO3 DB class. We _never_ ran into performance
problems in relation to database access.
• Basic security accomplished with basic request filters. Variables coming from GET or POST need to be defined as strings,
integers, etc, and are validated as such before being passed to controllers. For most extensions, this was sufficient.
• CICMVC was not an academic exercise. It was a real-world attempt to dramatically reduce development time in order to
increase company revenue while also reducing client cost
• More lightweight than ExtBase, feels significantly faster and more responsive.
• The year after we started using CICMVC widely across all projects, we saw revenue increase by about 75% while the
company stayed relatively small. Without wanting to mistake correlation for causation, our strong sense is that CICMVC had a
huge effect on CIC’s bottom line.
Slide #5 Zach Davis - June 10, 2011 - San Francisco TYPO3 Conference
Friday, June 10, 2011
6. CICMVC
Our first attempt at MVC in TYPO3
CICMVC: Our first attempt at MVC in TYPO3
Other parts weren’t so great...
• Lack of an ORM meant that persisting objects from the TYPO3 front-end was never as easy as it should have been. Instead of
persisting objects automatically, we built a form class that made error handling, validation, etc easier. (Creating and persisting
objects from a front-end form was the developer’s responsibility—not the framework’s—which made sense because there
often is not a simple 1-1 relationship between form and model.)
• Because it was a custom solution without a community behind it, our clients had to place a great deal of trust in their long-
term relationship with CIC in order to use CICMVC as the foundation for a large project.
• CICMVC was not an academic exercise. If developers weren’t careful, business logic could wind up in a view or presentation
logic could wind up in a model. Lack of constraints required CIC to place a lot of trust in its developers, even with internal QA
processes.
•Limited feature set and lack of configurability
•Lack of modularity: view helpers were stored in one large “helper” class rather than as individual classes
•Magic getters and setters on models were both a blessing and a curse
Slide #6 Zach Davis - June 10, 2011 - San Francisco TYPO3 Conference
Friday, June 10, 2011
7. CICMVC
A few examples
Some CICMVC Examples
Emory Center for the Study of Law and Religion
Slide #7 Zach Davis - June 10, 2011 - San Francisco TYPO3 Conference
Friday, June 10, 2011
8. CICMVC
A few examples
Some CICMVC Examples
Carnegie Corporation of New York
Slide #8 Zach Davis - June 10, 2011 - San Francisco TYPO3 Conference
Friday, June 10, 2011
9. CICMVC
A few examples
Some CICMVC Examples
Carnegie Corporation of New York
Models
and
Peers
Modules
Publication
Views
Slide #9 Zach Davis - June 10, 2011 - San Francisco TYPO3 Conference
Friday, June 10, 2011
10. Goodbye CICMVC, hello ExtBase!
We make the leap
In mid-2010, we drop CICMVC and switch to ExtBase
Custom ExtBase Content Tides: Project Directory and Tides: Impact Stories
Elements SFDC
Oracle Storage Backend Fluid Page Templates Backend Reporting Tools
Slide #10 Zach Davis - June 10, 2011 - San Francisco TYPO3 Conference
Friday, June 10, 2011
11. Goodbye CICMVC, hello ExtBase!
We make the leap
In mid-2010, we drop CICMVC and switch to ExtBase
We had a number of reasons for making the leap
• We wanted clients to have a solutions that other TYPO3 developers could support. It’s already a challenge to sell US
customers on TYPO3 with only a handful of vendors here; further lock-in due to a custom extension framework makes that
pitch even more difficult.
•We wanted to give back to the TYPO3 project, which we didn’t feel was possible with CICMVC. Originally, before ExtBase,
we thought we might be able to share CICMVC eventually. However, once ExtBase took off, it was clear that another MVC
solution wouldn’t be helpful.
•We bought into the thinking behind Domain Driven Design. Staying current in terms of best practices and writing code that
can be changed without extensive refactoring keeps us competitive. DDD pushes us to think more conceptually, which
makes us better developers (and, IMO, better thinkers!)
Slide #11 Zach Davis - June 10, 2011 - San Francisco TYPO3 Conference
Friday, June 10, 2011
12. Goodbye CICMVC, hello ExtBase!
We make the leap
In mid-2010, we drop CICMVC and switch to ExtBase
And some concerns...
•Performance, performance, performance! Would our clients perceive ExtBase extensions as slow and under performing?
•We were concerned about decreased productivity. The kickstarter wasn’t quite there yet, which meant having to do more
work to setup tables. Writing getters and setters on models is a pain. Fluid syntax took some getting used to and writing view
helpers can be time consuming.
•We were concerned that ExtBase wasn’t stable enough, even in late 2010, and that APIs would change after we’d done a
project.
•We worried that the persistence layer was too restrictive, and that some of the approaches expected by DDD were not well
suited for real-world applications.
•We suspected that ExtBase would not play nice with other key TYPO3 features, especially localization and Workspaces.
Slide #12 Zach Davis - June 10, 2011 - San Francisco TYPO3 Conference
Friday, June 10, 2011
13. ExtBase Content Elements
Hard to do with piBase, easy with ExtBase
Our first attempt: ExtBase content elements
We thought we’d take something difficult—creating editor-friendly, custom content elements
—and see if we could make it easier by using ExtBase
Slide #13 Zach Davis - June 10, 2011 - San Francisco TYPO3 Conference
Friday, June 10, 2011
14. ExtBase Content Elements
Hard to do with piBase, easy with ExtBase
Sidebar Callout
Content Element
Slide #14 Zach Davis - June 10, 2011 - San Francisco TYPO3 Conference
Friday, June 10, 2011
15. ExtBase Content Elements
Hard to do with piBase, easy with ExtBase
Custom content elements defined in ext_tables.php
ext_tables.php:
ext_localconf.php:
Slide #15 Zach Davis - June 10, 2011 - San Francisco TYPO3 Conference
Friday, June 10, 2011
16. ExtBase Content Elements
Hard to do with piBase, easy with ExtBase
Define actions in ContentController class
Slide #16 Zach Davis - June 10, 2011 - San Francisco TYPO3 Conference
Friday, June 10, 2011
17. ExtBase Content Elements
Hard to do with piBase, easy with ExtBase
Setup a Fluid view for the content element
Slide #17 Zach Davis - June 10, 2011 - San Francisco TYPO3 Conference
Friday, June 10, 2011
18. ExtBase Content Elements
Hard to do with piBase, easy with ExtBase
Our first attempt: ExtBase content elements
Using the same approach, we created a handful of similar elements.
Slide #18 Zach Davis - June 10, 2011 - San Francisco TYPO3 Conference
Friday, June 10, 2011
19. ExtBase Content Elements
Hard to do with piBase, easy with ExtBase
Our first attempt: ExtBase content elements
We learned a few things from these custom content elements
•Editors LOVE these content elements. Without much work on our part, clients get a library of custom content elements that
force them to be consistent without being overly constrained.
•After you create the first one, additional custom content elements are very cost effective. We include a placeholder
extension called “t3site” in our starter package that contains a controller for custom content elements and a sample custom
content element. The ext_tables config can be easily reproduced and new content elements can be created that use the
same controller.
•Someday, we should create a model for tt_content records that could be shared across these different content element
types.
•We save time (thereby making our work more profitable) because we don’t have to set up classes in the RTE that allow
editors to create similar element with <P> tags and whatnot, and because we don’t have to map and maintain a bunch of
FCEs.
•Editors get a better user interface because instead of flexforms, they get standard TYPO3 tt_content records with the
conventional fields that they’re used to.
Slide #19 Zach Davis - June 10, 2011 - San Francisco TYPO3 Conference
Friday, June 10, 2011
20. ExtBase Front-end Plugins
A typical ExtBase use case
Our second attempt: a standard extBase search/list
plug-in
Structurally similar to the Carnegie publications plug-in, Tides project directory and impact
stories seemed like a good candidate for moving away from CICMVC
•Built around quite a few simple models: Constituents, GeographicScopes, Issues, Programs, Projects, Strategies, Services,
and Stories
•Data for project directory is stored in Salesforce, pulled into TYPO3 every couple hours via Salesforce’s SOAP web service
• Story views include issue list, list of stories, search results (for AJAX requests), single story, and story teaser box
•Project directory views include list of projects, lat/long coordinates (for Google Maps request, output as JSON), search
results (for AJAX requests), and single project.
Slide #20 Zach Davis - June 10, 2011 - San Francisco TYPO3 Conference
Friday, June 10, 2011
21. ExtBase Front-end Plugins
A typical ExtBase use case
Tides Project Directory
Slide #21 Zach Davis - June 10, 2011 - San Francisco TYPO3 Conference
Friday, June 10, 2011
22. ExtBase Front-end Plugins
A typical ExtBase use case
Tides Issues Stories
Slide #22 Zach Davis - June 10, 2011 - San Francisco TYPO3 Conference
Friday, June 10, 2011
23. ExtBase Front-end Plugins
A typical ExtBase use case
Our second attempt: a standard extBase search/list
plug-in
One of ExtBase’s most important (and overlooked) capabilities is that it can unify back-end and
front-end functionality. There’s some hackery involved, but using the same repositories in both
sides of TYPO3 as well as ExtBase’s persistence layer saves considerable time.
Slide #23 Zach Davis - June 10, 2011 - San Francisco TYPO3 Conference
Friday, June 10, 2011
24. ExtBase Front-end Plugins
A typical ExtBase use case
Our second attempt: a standard extBase search/list
plug-in
Nonetheless, ExtBase’s persistence layer wasn’t sufficient for handling the complex queries
(not all that complex, perhaps?) generated by the search interface.
Slide #24 Zach Davis - June 10, 2011 - San Francisco TYPO3 Conference
Friday, June 10, 2011
25. Oracle Storage Backend for ExtBase
It worked!
Our third attempt: Oracle ExtBase Storage Backend
Client needed a searchable white paper/video library. We couldn’t, in good conscience, create
piBase extensions for this, and felt that we had to use ExtBase. One requirement was that
TYPO3 be running on an Oracle DB
Slide #25 Zach Davis - June 10, 2011 - San Francisco TYPO3 Conference
Friday, June 10, 2011
26. Oracle Storage Backend for ExtBase
It worked!
Our third attempt: Oracle ExtBase Persistence Layer
Our approach:
• Out of the box, DBAL pretty much ignores ExtBase because ExtBase pretty much ignores the TYPO3 DB class. Instead of using
methods like exec_SELECTquery, the ExtBase persistence layer uses passes SQL directly to the sql_query method on TYPO3’s
DB class. DBAL, as I understand it, doesn’t really parse these queries.
• So, instead of trying to use these DB methods, we followed ExtBase’s example and made a OracleDBBackend Class that
generates queries that conform to Oracle’s query syntax.
• Because the objects don’t change on the front-end, we didn’t implement addRow, updateRow or other save-related
methods. Those are on our roadmap
• Setting a different storage backend for Extbase in ext_localconf isn’t hard (and while it works, this probably shouldn’t be
considered a public API):
Slide #26 Zach Davis - June 10, 2011 - San Francisco TYPO3 Conference
Friday, June 10, 2011
27. Oracle Storage Backend for ExtBase
It worked!
Our third attempt: Oracle ExtBase Persistence Layer
What we learned:
• Avoiding DBAL as much as possible is definitely the way to go. Instead of making DBAL smarter about parsing ExtBase
queries, it’s easier to just make ExtBase generate syntactically correct Oracle queries.
• We ran into more problems with TYPO3/Oracle/DBAL in general than we did with ExtBase specifically, once we
implemented our storage backend.
• Performance, while not great, is tolerable. Because of the keyword search, the output is essentially uncached
• Work involved with this was really not all that difficult. We probably spent about 2 developer days on this.
• Not ExtBase related, per se, but worth mentioning: if TYPO3 is to truly succeed as an “enterprise” CMS, it needs better
Oracle support. Developers who have worked on DBAL have done a great job, but there’s more to do. Would be nice if
companies using TYPO3 and Oracle could pool resources.
Slide #27 Zach Davis - June 10, 2011 - San Francisco TYPO3 Conference
Friday, June 10, 2011
28. Fluid Page Templates
Lots of possibilities for continued development
Our fourth attempt: Fluid Page Templates
We’ve never been entirely satisfied with TemplaVoila. FCEs mean flexforms, and flexforms
provide an inconsistent UI for editors. TV stores configuration (mapping) in the DB, so we can’t
easily track it in Git. The classic page module and it’s limitations was a non-starter.
We needed a new approach, so we started building the fluid pages extension.
• Uses FLUID for page templates
• Does not require mapping mechanisms like TV, automaketemplate, parts and subparts, and other approaches
• Instead, Typoscript Objects are made available to the Fluid page template, just as objects are made available to fluid
templates in ExtBase
• Editors use backend layouts for the editing interface, which is more consistent with TYPO3’s overall back-end UI than TV
• FCEs are no longer needed because we have custom content elements, which are just as easy to setup, easier to use, and
easier to track in Git
• We’re looking for a column solution (like Bernhard’s nested content elements extension or Snowflake’s columns extension in
the TER).
• Relationship between tt_content and pages is obscured in XML, which makes some tasks difficult
Slide #28 Zach Davis - June 10, 2011 - San Francisco TYPO3 Conference
Friday, June 10, 2011
29. Fluid Page Templates
Lots of possibilities for continued development
Our fourth attempt: Fluid Page Templates
Slide #29 Zach Davis - June 10, 2011 - San Francisco TYPO3 Conference
Friday, June 10, 2011
30. Reports
A little ExtBase, a lot of ExtJs and ExtDirect
Our fifth attempt: Reports
Slide #30 Zach Davis - June 10, 2011 - San Francisco TYPO3 Conference
Friday, June 10, 2011
31. Conclusions
Our first attempt at MVC in TYPO3
Conclusions!
Overall, results are positive. We’ll continue using ExtBase!
• On low to medium traffic sites, with relatively flat data, ExtBase is clearly a better choice than piBase
• Even with more complex data or with larger sets of data, there’s a good chance that you can circumvent ExtBase’s storage
backend in your repositories by writing your own queries, especially if the application is read-only on the front-end.
• We get greater code reusability in ExtBase as we add models, services, and view helpers to our own ExtBase helper
extension.
• We think that Fluid, in particular, should be more widely used throughout TYPO3. It’s silly (and super-confusing for
newcomers) that we have so many templating methods in TYPO3 (TemplaVoila, parts/subparts/markers, and FLUID). TYPO3
should try to standardize on FLUID and continue to develop the FLUID TEMPLATE cObj so that it can be more useful as a tool
for page templates.
Slide #31 Zach Davis - June 10, 2011 - San Francisco TYPO3 Conference
Friday, June 10, 2011
32. Conclusions
Our first attempt at MVC in TYPO3
Conclusions!
Overall, results are positive. We’ll continue using ExtBase!
• Sharing models and repositories between the front-end and the back-end can be a huge time saver, especially when you
have to import data into TYPO3 from an external system for display on the front-end
• As recent discussions have shown, the persistence layer is a real pain point for ExtBase developers. Given TYPO3’s
idiosyncrasies, I have my doubts about the possibilities offered by Doctrine. Instead, I’d like it to be EASIER for developers to
get low-level database access and to create objects out of query results in the repositories (thereby moving away from the
one-to-one model / DB table relationship).
Slide #32 Zach Davis - June 10, 2011 - San Francisco TYPO3 Conference
Friday, June 10, 2011