NewApp Digest
search bot

scaling

GTA 6's Lack of a PC Port Isn't Out of Greed, According to a Former Rockstar Producer
AppWizard
July 15, 2026

GTA 6’s Lack of a PC Port Isn’t Out of Greed, According to a Former Rockstar Producer

Former Rockstar Games producer John Ricchio discussed the development timeline for PC versions of games in relation to console releases. He explained that starting with console development is advantageous due to their limited hardware capabilities, making it easier to create a game within specific constraints. Ricchio noted that while a PC build of Red Dead Redemption existed during its development, the decision to delay its release was influenced by prioritizing resources for Grand Theft Auto 5. He emphasized the need for a strong business rationale for porting games to different platforms, as the complexity of development often requires significant resource allocation. As Rockstar prepares for the launch of Grand Theft Auto 6 on November 19th for Xbox Series X|S and PS5, the focus is on delivering a polished product.
Ascend to ZERO: A Time-Bending Roguelike Sharpened to the Last Second
AppWizard
July 14, 2026

Ascend to ZERO: A Time-Bending Roguelike Sharpened to the Last Second

Ascend to ZERO has launched on XBOX Series X|S, XBOX on PC, and XBOX Cloud, and is part of the XBOX Play Anywhere initiative, accessible through XBOX Game Pass. The game features a 30-second countdown timer for each run, with damage taken reducing the time. A unique Time-Stop feature allows players to freeze everything while they move, enabling strategic positioning and action planning. Combat mechanics focus on autonomous targeting, allowing players to concentrate on strategy. The leveling system enables rapid progression from level 1 to hundreds of thousands. The game includes a new difficulty system for tailored challenges and an in-game play guide for player support. The late-game experience is designed to maintain excitement with strategic decision-making and culminates in a boss battle.
silver Android smartphone
AppWizard
July 13, 2026

GTA 6 isn’t coming to PC at launch, but not because Rockstar doesn’t “care about PC,” says GTA 5 producer: “If you’re working on that, you’re not working on something else”

Many fans are concerned about the absence of a PC port for the upcoming release of GTA 6. Former Rockstar producer John Ricchio explained that while the studio is not against any platform, they evaluate the investment of resources for PC versions based on practical considerations. He noted that developing for console hardware first can be more efficient than scaling down from PC. Advancements in console technology have alleviated some challenges, but focusing on a PC port can divert resources from other projects. Additionally, Rockstar faces a potential million-dollar fine in Australia if it does not comply with new online safety laws requiring player identification to access the game.
What Is Serverless PostgreSQL?
Tech Optimizer
July 12, 2026

What Is Serverless PostgreSQL?

Serverless PostgreSQL is a fully managed cloud database model that separates compute and storage, allowing them to scale independently and automatically based on demand. It eliminates the need for manual infrastructure provisioning and capacity planning, charging only for active usage. Unlike traditional PostgreSQL setups, which require continuous resource allocation and manual scaling, serverless PostgreSQL provisions resources on demand and can scale down to zero during idle periods. Serverless PostgreSQL integrates with serverless compute platforms, enabling analytical queries to access the same data within a unified architecture. Key differences between traditional and serverless PostgreSQL include manual versus automatic provisioning and scaling, fixed versus usage-based billing, and high versus reduced operational overhead. Lakebase architecture is an emerging model that combines transactional databases with lakehouse foundations, allowing operational and analytical workloads to coexist on a single platform. This architecture minimizes data duplication and simplifies access, enhancing data management and analysis. Serverless PostgreSQL operates on a cloud-native architecture that enhances efficiency by allowing compute and storage to scale autonomously. It features scale-to-zero behavior, where compute resources are suspended when inactive and reactivated upon new queries. Major providers include Databricks Lakebase, Amazon Aurora Serverless v2, and Neon, each offering varying capabilities and integrations. Pricing for serverless PostgreSQL typically includes charges for compute resources, storage, and data transfer, with costs fluctuating based on workload activity. Cold start latency is a performance consideration, as reactivating compute resources can introduce delays. Strategies to mitigate this include keeping resources partially active or selecting providers with minimal cold start impacts. Serverless PostgreSQL is well-suited for OLTP workloads, while lakebase architecture is better for AI development, variable workloads, and environments requiring rapid iteration. Setting up serverless PostgreSQL involves choosing a provider, creating a database instance, and configuring access settings. It can also be used alongside serverless compute platforms for analytics, further extending its capabilities.
Running pgvector in production on Amazon Aurora PostgreSQL
Tech Optimizer
July 12, 2026

Running pgvector in production on Amazon Aurora PostgreSQL

Running pgvector on Amazon Aurora PostgreSQL-Compatible Edition offers a vector store with operational capabilities, high availability, and scalability. It is favored for Retrieval Augmented Generation (RAG) workloads transitioning to production, but increased traffic introduces challenges like query latency and memory management. Key operational practices for pgvector workloads include selecting the appropriate index type (HNSW or IVFFlat), establishing a baseline schema, choosing a suitable distance operator, scaling the index through quantization and partitioning, and preparing for churn and observability. The prerequisites for using pgvector include an Aurora PostgreSQL-Compatible cluster with specific PostgreSQL versions and the vector extension enabled. The embedding model used in examples is Amazon Titan Text Embeddings V2, which produces 1024-dimensional embeddings. pgvector supports two Approximate Nearest Neighbor (ANN) index types: HNSW, which is efficient for querying and allows for incremental insertions, and IVFFlat, which is less resource-intensive but requires rebuilding if data changes. There are scenarios where forgoing an index is beneficial, such as small datasets or partitioned datasets requiring 100% recall. A baseline schema for a multi-tenant document store includes creating a table for documents with an embedding vector and establishing indexes for tenant IDs and embeddings using HNSW. The recommended parameters for HNSW include m = 16 and ef_construction = 128. Scaling to millions of vectors involves quantization, tuning HNSW parameters, and partitioning. Aurora Optimized Reads can extend effective cache capacity, and managing index churn is crucial for maintaining performance. Observability metrics include query-level statistics, instance-level metrics, and custom application-defined metrics. To clean up after testing, it is advisable to drop the created indexes and tables, and delete the Aurora PostgreSQL-Compatible cluster and any manual snapshots taken during testing.
Why most AI projects fail: It’s infrastructure and people
Tech Optimizer
July 6, 2026

Why most AI projects fail: It’s infrastructure and people

AI technology faces significant criticism for its low success rates in delivering business results, with studies indicating a 95% failure rate for enterprise AI solutions and only 9% of organizations in Europe, the Middle East, and Africa achieving measurable outcomes from AI initiatives. Four main shortcomings hinder the transition of AI prototypes to production: 1. Deployment Flexibility: Prototyping environments often lack the necessary flexibility for large-scale production deployment, particularly in regulated sectors. 2. Data Sovereignty: Production transitions can complicate data sovereignty at enterprise and regional levels. 3. Reliability: High availability is crucial for production environments, but vendor-managed platforms may not guarantee seamless upgrades or hardware swaps without downtime. 4. Disconnect in Tool Selection: Developers often choose tools for prototyping without considering production implications, leading to difficulties in scaling. The shortage of database administrators (DBAs) is exacerbated by the increasing use of AI tools, with 84% of developers utilizing them according to a 2025 survey. To address these challenges, Merrick suggests leveraging AI DBA agents to support human DBAs and improve database management efficiency. He emphasizes the need for both robust data infrastructure and enhanced operational support to improve the success rates of AI prototypes.
From monolith to Lakebase to LTAP: rethinking the database from storage up
Tech Optimizer
July 2, 2026

From monolith to Lakebase to LTAP: rethinking the database from storage up

Sixteen years ago, the author began their PhD at UC Berkeley and was advised to focus on analytics rather than OLTP databases, which were considered solved. This led to the creation of Apache Spark and Databricks. However, during the development of Databricks, it was found that OLTP databases were not solved problems; they were difficult to scale and fragile. This realization led to the development of Lakebase, a serverless Postgres database designed with modern technology. Lakebase architecture separates the write-ahead log (WAL) and data files into independent, scalable services. The WAL is externalized to a service called SafeKeeper, which uses Paxos-based replication for durability, while data files are managed by PageServer, which stores them in cloud object storage. This design addresses challenges such as data loss, scaling, and performance interference between transactional and analytical workloads. Lakebase maintains compatibility with Postgres, offers unlimited storage, serverless compute, durable writes, and simpler high availability. It also introduces LTAP (Lake Transactional/Analytical Processing), which allows both transactional and analytical processing to operate on a single data copy in real time, eliminating the need for separate data copies and reducing costs. LTAP utilizes a unified storage layer that allows data to be materialized in both row and columnar formats, optimizing it for both transactional and analytical workloads. The system ensures that analytics can access the most current data without affecting transactional performance by using a log sequence number (LSN) to retrieve the latest changes. Unlike traditional CDC approaches, LTAP requires no explicit table replication, as all data is stored in a single governed copy. This architecture circumvents common issues faced by hybrid transactional/analytical processing (HTAP) systems, such as incomplete feature sets, lack of ecosystem support, and performance contention. The Lakebase architecture has unlocked capabilities like unlimited storage, elastic compute, durable writes, and instant branching, with ongoing developments anticipated in the future.
silver Android smartphone
Tech Optimizer
July 2, 2026

From monolith to Lakebase to LTAP: rethinking the database from storage up

Sixteen years ago, the author began their PhD at UC Berkeley, where they were advised to focus on analytics rather than OLTP databases, which were considered a solved problem. However, upon developing Databricks, they found that OLTP databases were cumbersome, challenging to scale, and fragile. This led to the creation of Lakebase, a serverless Postgres database designed to address these issues by externalizing the write-ahead log (WAL) and data files into independent services. Lakebase architecture separates the WAL into a distributed service called SafeKeeper and data files into another service called PageServer, allowing for improved durability, scalability, and performance. This architecture eliminates data loss risks associated with disk failures and misconfigurations, simplifies high availability, and allows for elastic compute resources. Lakebase also introduces LTAP (Lake Transactional/Analytical Processing), which enables transactions and analytics to operate on a single data copy in real-time, avoiding the need for separate data copies and reducing costs. The system retains Postgres's ACID semantics while storing data in open columnar formats, making it accessible to both transactional and analytical engines without the delays and complexities of traditional replication methods. The architecture allows for unlimited storage, serverless compute, and instant branching, while ensuring that analytics can read the most current transactional data without affecting transactional workloads. LTAP aims to unify transactional and analytical processing by leveraging distinct compute engines for each workload while integrating at the storage layer.
Search