Jonathan Lalou's Blog

Posts Tagged ‘AWSReInventPartnerSessions2024’

Lecturer

Felipe Cardeneti Mendes acts as Technical Director at ScyllaDB, guiding technical strategies for high-throughput, low-latency databases. Based in São Paulo, Felipe has extensive experience in distributed systems optimized for data-intensive applications. Dean Poulin leads data engineering at Tripadvisor, focusing on scalable solutions for personalization in travel platforms.

Abstract

This thorough assessment explores Tripadvisor’s use of ScyllaDB on AWS for real-time personalization, analyzing challenges in data-intensive apps, methodological optimizations for throughput and latency, and implications for user experience and infrastructure efficiency.

Challenges in Data-Intensive Personalization

Tripadvisor assesses user preferences rapidly to deliver relevant content, requiring systems sustaining one million operations per second with single-digit millisecond latencies. Growth escalates costs, forcing trade-offs between performance and expenses.

ScyllaDB, compatible with Cassandra and DynamoDB, offers five times higher throughput and twenty times lower latencies, reducing infrastructure spend by up to seventy-five percent.

Methodological Deployment and Performance

Migration from on-prem Cassandra to Scylla Cloud, then bring-your-own-account model, achieved zero-downtime at forty thousand operations per second. Partitioning by visitor GUID and fact type, using leveled compaction, supports read-heavy workloads.

Microservices handle over one billion daily requests with 1.2-millisecond average latency. A six-node EC2 cluster processes 340,000 operations per second at twenty-one percent CPU.

Code sample for data partitioning in ScyllaDB:

CREATE TABLE facts (
    visitor_guid UUID,
    fact_type TEXT,
    created_at TIMESTAMP,
    attributes TEXT,
    PRIMARY KEY ((visitor_guid, fact_type), created_at)
) WITH CLUSTERING ORDER BY (created_at DESC);

This structure optimizes queries for user events.

In summary, ScyllaDB enhances personalization, balancing scale and cost effectively.

Links:

• Video Lecture
• Felipe Cardeneti Mendes on LinkedIn
• Dean Poulin on LinkedIn
• ScyllaDB Website
• Tripadvisor Website

Lecturer

Ben Lingwood directs cloud and data engineering initiatives at PwC, leading efforts to modernize enterprise systems through scalable, cost-effective solutions. Based in London, Ben has driven numerous digital transformations, emphasizing native cloud services for enhanced efficiency. Lulu Zhang heads technology and services at KONE, overseeing global operations and digital strategies to support the company’s extensive elevator and escalator networks.

Abstract

This scholarly inquiry assesses KONE’s strategic shift to AWS for data integrations in enterprise applications, facilitated by PwC’s delivery of over two hundred technical integrations amid an SAP transformation. It evaluates the contextual business imperatives, methodological designs for seamless data flows, and implications for cost reduction, customer insights, and innovation in urban mobility solutions.

Business Imperatives and Solution Design

KONE, a Finnish leader in elevators and escalators, transports two billion people daily, necessitating robust data management for maintenance and innovation. Business challenges included cost reduction to benefit the bottom line and clients, alongside gaining insights into product usage for preemptive maintenance and enhancements.

PwC adopted a backward-working approach, starting from ambitions to devise solutions. This led to a scalable, cost-effective data movement layer using native AWS services, replacing expensive middleware. Patterns like event-driven architectures and persistent stores optimized for velocity and cost.

Implementation and Operational Outcomes

Over two hundred integrations supported SAP transformations, capturing payloads for predictive queries. DynamoDB enabled high-velocity lookups, reducing lag and expenses. The layer underpins AI models for maintenance and financial analysis, aligning with data-driven visions.

In conclusion, this collaboration demonstrates how native services streamline operations, fostering innovation and efficiency.

Links:

• Video Lecture
• Ben Lingwood on LinkedIn
• Lulu Zhang on LinkedIn
• PwC Company Website
• KONE Website

Lecturer

Connor McArthur co-founded dbt Labs, where he contributes to developing workflows for data transformations inspired by software engineering principles. With over a decade in engineering leadership, Connor focuses on metadata-driven analytics to enhance governance and development speed. Sri Kamireddy leads data initiatives at Moderna, overseeing the integration of diverse data platforms to support organizational goals in biotechnology.

Abstract

This detailed review investigates Moderna’s adoption of dbt Cloud to construct a unified data mesh architecture, integrating disparate data systems for enhanced coherence and efficiency. It scrutinizes the contextual demands of multi-platform environments, methodological use of cross-platform dbt mesh, and implications for data governance, engineering workflows, and business outcomes in a high-stakes industry.

Contextual Demands in Multi-Platform Data Environments

Organizations like Moderna operate in complex data landscapes, often employing multiple warehouses due to acquisitions, team preferences, or specialized needs. This diversity, while beneficial for tailored solutions, introduces fragmentation, complicating integration and governance. Moderna’s setup includes Amazon EMR, Spark, Redshift, Athena, and Glue, reflecting a hybrid approach to handle vast datasets from supply chain, manufacturing, and shipments.

The challenge lies in unifying these without duplicating data or losing lineage, which could delay insights critical for operations like vaccine distribution. dbt addresses this by providing an opinionated workflow based on software development cycles, generating active metadata that informs a data control plane. This plane centralizes building, deploying, orchestrating, observing, and cataloging analytics stacks.

Methodological Application of Cross-Platform dbt Mesh

dbt mesh enables seamless connectivity across platforms using Iceberg for interoperability. At Moderna, this methodology streamlined combining supply chain data from a data lake (Athena) with manufacturing data (Redshift). By setting project statuses to public within the dbt environment, models from one platform reference others, preserving end-to-end lineage.

A custom SDK wrapper enforces data quality checks and metadata inclusion during model development, ensuring governance without stifling domain-driven engineering. Lake Formation tags maintain access controls, preventing silos.

Code sample for referencing models across projects in dbt:

sources:
  - name: athena_project
    schema: athena_schema
    tables:
      - name: supply_chain_data

models:
  - name: unified_product
    config:
      materialized: table
    sql: |
      SELECT *
      FROM {{ ref('athena_project', 'supply_chain_data') }}
      JOIN redshift_manufacturing ON ...

This demonstrates methodological simplicity in unifying data flows.

Implications for Governance and Operational Efficiency

The approach reduces engineering workloads by eliminating custom scripts, allowing focus on value-added tasks. Enhanced lineage aids business users in tracing metrics origins, fostering trust and faster decision-making.

In biotechnology, where timely insights impact global health, this efficiency is crucial. Scalable infrastructure with controlled costs supports Moderna’s data-driven culture, emphasizing strong platforms, governance, and security.

In summary, dbt mesh at Moderna exemplifies how unified tools bridge platform divides, promoting cohesive data estates that drive innovation and reliability.

Links:

• Video Lecture
• Connor McArthur on LinkedIn
• Sri Kamireddy on LinkedIn
• dbt Labs Website
• Moderna Website

spec = “Sort a list of numbers”
code = generate_code(spec)
tests = [([3, 1, 2], [1, 2, 3]), ([5, 4], [4, 5])]
if test_code(code, tests):
print(“Code passes tests”)
“`

This exemplifies the iterative process of generation and validation central to the platform.

Analytical Implications for Efficiency and Innovation

The deployment of GenWizard reveals profound implications for operational efficiency. By automating repetitive tasks, it allows teams to focus on high-value activities, reducing project timelines by up to seventy percent in some cases. This efficiency stems from the platform’s ability to handle complex correlations and predictions, as seen in incident management where noise reduction leads to faster resolutions.

Innovation is fostered through enhanced decision-making. The system’s knowledge base, enriched with historical data and AI insights, supports proactive strategies like predictive maintenance and application rationalization. For instance, analyzing application portfolios identifies redundancies, enabling cost savings and streamlined operations.

Collaboration with technology partners like AWS amplifies these benefits. Amazon Q’s integration ensures seamless natural language interactions, democratizing access to advanced tools and promoting a culture of continuous improvement.

Consequences for Enterprise Adoption and Future Directions

Enterprise adoption of such platforms mitigates risks associated with legacy systems, facilitating smoother migrations and modernizations. However, challenges include ensuring data privacy and model accuracy, addressed through robust governance frameworks.

Future directions involve expanding agentic capabilities to encompass more lifecycle stages, potentially incorporating multimodal AI for broader applications. This could revolutionize industries by enabling autonomous operations, where systems self-optimize based on real-time data.

In conclusion, the fusion of generative AI with service delivery platforms like GenWizard, powered by AWS, represents a paradigm shift toward intelligent, efficient technology management, promising sustained competitive advantages.

Links:

• Video Lecture
• Luke Higgins on LinkedIn
• Accenture Company Website

generated_code = f"def process_data(data):\n    return sorted(data)\n"
return generated_code

def test_code(code, test_cases):
exec(code)
for case in test_cases:
input_data, expected = case
result = process_data(input_data)
if result != expected:
return False
return True

Lecturer

Luke Higgins serves as the Chief Architect for global asset and automation deployment at Accenture, where he focuses on integrating artificial intelligence and automation into service delivery frameworks. With over twenty years at Accenture, Luke has contributed to numerous innovations, including award-winning projects in generative AI applications. Kishor Panth leads global asset engineering at Accenture, overseeing the development of software assets, tools, and automations for client solutions. With more than twenty years in the firm, Kishor specializes in applying AI and automation to software development and platform management.

Abstract

This comprehensive analysis delves into the integration of generative artificial intelligence within service delivery platforms, drawing from Accenture’s experiences with its proprietary GenWizard system. It explores the contextual evolution from traditional automation to AI-driven workflows, methodological approaches to embedding Amazon Q and foundation models, and the broader implications for operational efficiency, decision-making, and innovation across technology lifecycles. By examining real-world applications in software engineering, application management, and platform optimization, the article highlights how these technologies foster accelerated project timelines and customized client outcomes.

Evolution from Automation to Generative AI in Service Delivery

The journey toward incorporating generative AI in technology services reflects a shift from rule-based automation to intelligent, adaptive systems. Initially, efforts focused on streamlining processes through predefined scripts and AI models for tasks like anomaly detection and predictive maintenance. However, the advent of large language models introduced capabilities for natural language processing and code generation, transforming how organizations approach software development and operations.

At Accenture, this evolution culminated in the GenWizard platform, designed to enhance service areas by leveraging AWS services such as Amazon Q. The platform addresses challenges in managing complex technology lifecycles, where traditional methods often led to inefficiencies in code migration, application rationalization, and incident resolution. By infusing generative AI, GenWizard enables forward and reverse engineering, allowing for rapid analysis of legacy systems and generation of modern equivalents.

This transition was driven by the need to handle vast codebases—often millions of lines—across diverse languages like COBOL, Java, and .NET. Reverse engineering, for instance, involves creating visual representations of code structures to identify dependencies and inefficiencies, while forward engineering automates the creation of new code based on specifications. The integration of Amazon Q facilitates natural language queries, making these processes accessible to non-experts and accelerating timelines from months to days.

Methodological Integration of AWS Services in GenWizard

GenWizard’s architecture employs a multi-agent framework powered by AWS foundation models, where agents specialize in tasks such as code analysis, generation, and testing. This methodology draws from software development best practices, incorporating continuous integration and deployment loops to ensure reliability.

A key component is the use of Amazon Q for contextual understanding and response generation. For example, in code migration, agents analyze source code, infer intent, and produce target language equivalents, followed by automated testing against predefined criteria. This reduces human error and enhances consistency, as demonstrated in projects converting legacy mainframe applications to cloud-native formats.

In application management, the platform’s event operations module rationalizes incident tickets by identifying duplicates and correlating issues with configuration management databases. This involves clustering related events and suggesting resolutions from a knowledge base, significantly cutting resolution times.

Platform engineering benefits from predictive analytics, where AI models forecast resource needs and optimize configurations. The methodology emphasizes data-driven insights, using metadata from development workflows to inform decisions.

Code sample illustrating a basic agentic workflow in Python, simulating code generation and testing:

“`
def generate_code(specification):

class Account:
def init(self, balance):
self.balance = balance

def transaction(self, amount):
    if amount > 0:
        self.balance += amount
    else:
        if abs(amount) <= self.balance:
            self.balance += amount
        else:
            raise ValueError("Insufficient funds")

Lecturer

Cameron Jenkins acts as a Managing Director in the Mainframe Modernization group at Accenture, overseeing sales, marketing, and technology products with decades of experience in legacy system transformations. Shri Kai occupies a senior role at T. Rowe Price, serving as the executive sponsor for modernization initiatives, with prior successes at Experian and CoreLogic. Joel Rosenberger functions as the AWS Mainframe Modernization Lead and Chief Architect at Accenture, strengthening partnerships and architecting programs like Go Big for large-scale migrations.

Abstract

This in-depth analysis scrutinizes the strategic value of mainframe modernization in financial services, focusing on T. Rowe Price’s migration to Amazon Web Services facilitated by Accenture’s refactoring and generative artificial intelligence tools. It dissects the methodologies for automating legacy code analysis, generating artifacts, and enhancing decision-making, while considering contextual drivers like agility and cost savings. The article evaluates implications for business users, risk mitigation, and future patterns, advocating a hybrid approach combining deterministic tools with emerging AI capabilities.

Strategic Drivers and Organizational Support

Mainframe modernization in finance yields enhanced flexibility, superior client interactions, and reduced expenses. At T. Rowe Price, the decision to decommission the mainframe and relocate core applications stems from these benefits, supported by executive buy-in from the CEO, CTO, COO, and CDO. This high-level endorsement mitigates risks associated with legacy systems, aligning technology with business objectives.

The initiative transcends cost reduction, positioning technology as a competitive advantage. Historical projects lacking such support often faltered, emphasizing the need for strategic alignment. AWS was selected due to its leadership in cloud services and proximity advantages, facilitating seamless integration.

Methodological Approaches to Code Transformation

Accenture’s tools automate analysis of legacy languages like COBOL, Assembler, and PL/1, producing technical and business documentation. Generative AI augments this by creating artifacts valuable to IT architects and business stakeholders, fostering collaboration and informed decisions.

Patterns include refactoring for twelve applications, with some sunsetting pre-migration. Post-migration flexibility allows microservices development, end-of-life planning, or incremental enhancements, tailored to business needs.

Testing remains pivotal for confidence-building, with AI generating test suites to address outdated data, reducing risks.

Code sample for basic COBOL to Java refactoring simulation in Python:

“`

Lecturer

Jason Tan represents Intel within automotive technology partnerships, emphasizing edge-to-cloud computational synergies. Anas Jaber contributes AWS expertise in industry-specific cloud maturity acceleration.

Abstract

This extensive analytical treatment examines the automotive sector’s transition toward sustainable, connected, and personalized mobility paradigms, projecting electric vehicle penetration at thirty-five percent by 2030 and 863 million connected vehicles by 2035. It details Intel-AWS collaboration with a prominent Asian original equipment manufacturer to establish a robust Cloud Center of Excellence, overcoming initial resistance through structured governance, phased migration, and comprehensive data fabric implementation. Architectural patterns for IoT ingestion, serverless processing, and machine learning integration illustrate scalable innovation pathways.

Macro-Trends and Operational Challenges in Automotive Digital Transformation

The automotive industry undergoes profound restructuring driven by sustainability imperatives, connectivity proliferation, and personalization expectations. Electric vehicles emerge as dominant choice factors, bolstered by governmental incentives and expanding charging infrastructure. Connected vehicle projections anticipate near-universal network integration within fifteen years.

Transformation imperatives encompass solution scalability to accommodate exponential data growth, data-to-action translation interconnecting providers, consumers, and service entities, and security assurance given pervasive connectivity risks.

Intel and AWS maintain eighteen-year strategic alignment: seventy percent of AWS instances operate on Intel processors, joint optimizations deliver superior total-cost-of-ownership, and marketplace extensions enhance service accessibility.

Cloud Center of Excellence Establishment and Phased Implementation

The Asian OEM partnership constructs a comprehensive Cloud Center of Excellence integrating centralized policy enforcement with decentralized execution autonomy.

Governance foundations include landing zone standardization, guardrail automation, and cost allocation transparency. Migration orchestration progresses through repatriation waves for optimization followed by native redesign embracing serverless and microservices paradigms.

Data fabric architecture unifies ingestion via Kinesis, storage within S3, processing through EMR, analytics using Athena and QuickSight, and machine learning via SageMaker. Smart mobility manifests through IoT Core telemetry collection, Lambda orchestration, DynamoDB persistence, and Cognito authentication.

{
  "telemetryIngestion": "AWS IoT Core",
  "eventProcessing": "Lambda + Kinesis",
  "stateManagement": "DynamoDB",
  "authentication": "Cognito"
}

Edge computing via Greengrass processes locally critical functions, synchronizing periodically through Snowball Edge. FinOps dashboards visualize expenditure patterns while anomaly detection flags deviations.

Organizational Change Management and Standardization Imperatives

Executive commitment to industry consortia accelerates interoperability standards development, addressing architectural fragmentation and application portability constraints. Change management emphasizes education, training, and cultural alignment to mitigate resistance.

Outcomes include accelerated cloud adoption, elevated customer satisfaction, and foundational infrastructure for continuous mobility innovation. The paradigm extends beyond automotive to any sector pursuing connectivity-driven differentiation.

Links:

• Video: Discover how automotive industry drives user adoption in smart mobility

Lecturer

Beth Torres heads strategic accounts for Eviden within the Atos Group, facilitating client alignment with artificial intelligence transformation initiatives. Kevin Davis serves as CTO of the AWS business group at Eviden, architecting machine learning operations and generative operations platforms. Eric Trell functions as AWS Cloud lead for Atos, optimizing hybrid and multi-cloud infrastructures.

Abstract

This scholarly examination articulates the distinction between conventional artificial intelligence adoption and genuine AI-first organizational identity, wherein intelligence permeates decision-making, customer engagement, and product architecture. It contrasts startup-native implementations with enterprise retrofitting, delineates MLOps/GenOps operational frameworks, and establishes ethical governance across model construction, deployment guardrails, and continuous monitoring. Cloud-enabled legacy data accessibility emerges as a pivotal enabler, alongside considerations for responsible artificial intelligence stewardship.

Conceptual Differentiation: AI Adoption versus AI-First Organizational Paradigm

The progression from cloud-first to AI-first organizational models necessitates embedding artificial intelligence as foundational infrastructure rather than peripheral augmentation. Whereas startups construct products with intelligence intrinsically woven throughout, established enterprises frequently append capabilities—exemplified by chatbot overlays—onto legacy systems.

AI-first identity manifests through operational preparedness: strategic platforms enabling accelerated use-case development by abstracting foundational complexities including data acquisition, quality assurance, and infrastructure provisioning. Artificial Intelligence Centers of Excellence institutionalize this preparedness, directing resources toward rapid return-on-investment validation through structured experimentation.

MLOps and GenOps frameworks streamline model lifecycle management at enterprise scale, addressing data integrity, ethical transparency, and governance requirements. Cloud-first positioning substantially facilitates this transition; mainframe-resident operational data, previously inaccessible for generative applications, becomes replicable to AWS environments without comprehensive modernization.

Ethical Governance and Technical Enablement Mechanisms

Responsible artificial intelligence necessitates multilayered ethical consideration. A tripartite framework structures this responsibility:

During model construction, training corpora undergo scrutiny for bias, provenance, and representativeness. Deployment guardrails leverage AWS-native capabilities to enforce content policies and contextual grounding. Continuous monitoring implements anomaly detection with predefined response protocols, calibrated according to interface interactivity levels.

\# Conceptual Bedrock guardrail implementation
import boto3

bedrock = boto3.client('bedrock-runtime')
guardrail = {
    'contentPolicy': [{'blockedTopics': ['prohibited-content']}],
    'contextualGrounding': True
}
response = bedrock.invoke_model(
    modelId='anthropic.claude-3',
    body=prompt,
    guardrailConfig=guardrail
)

Security compartmentalization within Bedrock preserves data isolation for sensitive domains such as healthcare. Production readiness extends beyond prompt efficacy to encompass data validation, accuracy verification, and misinformation mitigation within innovation toolchains.

Strategic Ramifications and Transformation Imperatives

AI-first positioning defends against startup disruption by enabling comparable innovation velocity. Ethical frameworks safeguard reputational integrity while ensuring output reliability. Cloud-mediated legacy data accessibility democratizes generative capabilities across historical systems.

Organizational consequences include systematic competitive advantage through intelligence-permeated operations, regulatory alignment via auditable governance, and cultural evolution toward experimentation-driven development. The paradigm compels reevaluation of educational curricula to incorporate technology ethics as core competency.

Links:

• Video: What is an AI-first company?