Apex vs MySQL

Overview

MySQL

Stacks129.6K

Followers108.6K

Votes3.8K

GitHub Stars11.8K

Forks4.1K

Apex

Stacks503

Followers117

Votes0

GitHub Stars33

Forks56

Apex vs MySQL: What are the differences?

Introduction

This Markdown code provides a comparison between Apex and MySQL. Apex is a programming language used for the Salesforce platform, while MySQL is a relational database management system. The following points highlight the key differences between Apex and MySQL.

Data Manipulation Language (DML) vs. Structured Query Language (SQL): Apex uses DML statements to perform CRUD operations on records in the Salesforce database. On the other hand, MySQL uses SQL queries, such as SELECT, INSERT, UPDATE, and DELETE, to interact with the database. The main difference is that Apex's DML is specific to the Salesforce platform, while MySQL's SQL can be used with other database systems as well.
Object-Oriented vs. Relational Database Model: Apex is an object-oriented programming language, which means it supports features like inheritance, encapsulation, and polymorphism. It allows developers to define custom objects, classes, and relationships between them. In contrast, MySQL follows a relational database model, where data is organized into tables with rows and columns. It focuses on maintaining relationships between tables through foreign keys.
Execution Context: Server-side vs. Client-side: Apex runs on the Salesforce servers, making it a server-side language. The code is executed on the server, and the results are sent back to the client. This architecture provides the advantage of server performance and security. On the other hand, MySQL is a client-side database management system. Queries and manipulations are sent from the client to the MySQL server, and the results are returned to the client for processing.
Integration with Salesforce Platform vs. Standalone Database: Apex is tightly integrated with the Salesforce platform, allowing developers to access and manipulate data within the Salesforce ecosystem. It provides native support for Salesforce-specific features like record triggers, workflow rules, and custom objects. In contrast, MySQL is a standalone database system that can be used with various programming languages and platforms. It is commonly used for web development, e-commerce, and other applications.
Hosting and Infrastructure: Cloud vs. On-premises: Salesforce, including the Apex code, is hosted on the cloud infrastructure provided by Salesforce.com. This eliminates the need for developers to manage the underlying hardware and infrastructure. MySQL is a database management system that can be hosted either on the cloud or on-premises. It allows developers to choose the hosting option that best suits their requirements and preferences.
Scalability and Performance: Platform as a Service vs. Traditional Database: Salesforce's platform-as-a-service (PaaS) model provides built-in scalability, performance optimization, and automatic upgrades. Apex code can take advantage of these features to ensure optimal performance. MySQL, being a traditional database system, requires manual scaling and optimization to handle increasing workloads. This adds an extra layer of responsibility for developers and administrators.

In summary, Apex is a server-side language tightly integrated with the Salesforce platform, running on a cloud infrastructure, and focused on object-oriented development. MySQL, on the other hand, is a client-side database management system, offering broader compatibility, standalone hosting options, and adherence to the relational database model.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs

CLI (Node.js)

Manual

Advice on MySQL, Apex

Kyle

Web Application Developer at Redacted DevWorks

Dec 3, 2019

Decidedon

PostGIS

While there's been some very clever techniques that has allowed non-natively supported geo querying to be performed, it is incredibly slow in the long game and error prone at best.

MySQL finally introduced it's own GEO functions and special indexing operations for GIS type data. I prototyped with this, as MySQL is the most familiar database to me. But no matter what I did with it, how much tuning i'd give it, how much I played with it, the results would come back inconsistent.

It was very disappointing.

I figured, at this point, that SQL Server, being an enterprise solution authored by one of the biggest worldwide software developers in the world, Microsoft, might contain some decent GIS in it.

I was very disappointed.

Postgres is a Database solution i'm still getting familiar with, but I noticed it had no built in support for GIS. So I hilariously didn't pay it too much attention. That was until I stumbled upon PostGIS and my world changed forever.

449k views449k

Comments

Ido

Mar 6, 2020

Decided

My data was inherently hierarchical, but there was not enough content in each level of the hierarchy to justify a relational DB (SQL) with a one-to-many approach. It was also far easier to share data between the frontend (Angular), backend (Node.js) and DB (MongoDB) as they all pass around JSON natively. This allowed me to skip the translation layer from relational to hierarchical. You do need to think about correct indexes in MongoDB, and make sure the objects have finite size. For instance, an object in your DB shouldn't have a property which is an array that grows over time, without limit. In addition, I did use MySQL for other types of data, such as a catalog of products which (a) has a lot of data, (b) flat and not hierarchical, (c) needed very fast queries.

575k views575k

Comments

Navraj

CEO at SuPragma

Apr 16, 2020

Needs adviceon

MySQL

PostgreSQL

I asked my last question incorrectly. Rephrasing it here.

I am looking for the most secure open source database for my project I'm starting: https://github.com/SuPragma/SuPragma/wiki

Which database is more secure? MySQL or PostgreSQL? Are there others I should be considering? Is it possible to change the encryption keys dynamically?

Thanks,

Raj

401k views401k

Comments

Detailed Comparison

MySQL	Apex
The MySQL software delivers a very fast, multi-threaded, multi-user, and robust SQL (Structured Query Language) database server. MySQL Server is intended for mission-critical, heavy-load production systems as well as for embedding into mass-deployed software.	Apex is a small tool for deploying and managing AWS Lambda functions. With shims for languages not yet supported by Lambda, you can use Golang out of the box.
-	Supports languages Lambda does not natively support via shim, such as Go;Binary install (useful for continuous deployment in CI etc);Project level function and resource management;Configuration inheritance and overrides;Command-line function invocation with JSON streams;Transparently generates a zip for your deploy;Function rollback support;Tail function CloudWatchLogs;Concurrency for quick deploys;Dry-run to preview changes
Statistics
GitHub Stars 11.8K	GitHub Stars 33
GitHub Forks 4.1K	GitHub Forks 56
Stacks 129.6K	Stacks 503
Followers 108.6K	Followers 117
Votes 3.8K	Votes 0
Pros & Cons
Pros 800 Sql 679 Free 562 Easy 528 Widely used 490 Open source Cons 16 Owned by a company with their own agenda 3 Can't roll back schema changes	No community feedback yet
Integrations
No integrations available	AWS Lambda Golang

What are some alternatives to MySQL, Apex?

MongoDB

MongoDB stores data in JSON-like documents that can vary in structure, offering a dynamic, flexible schema. MongoDB was also designed for high availability and scalability, with built-in replication and auto-sharding.

PostgreSQL

PostgreSQL is an advanced object-relational database management system that supports an extended subset of the SQL standard, including transactions, foreign keys, subqueries, triggers, user-defined types and functions.

Microsoft SQL Server

Microsoft® SQL Server is a database management and analysis system for e-commerce, line-of-business, and data warehousing solutions.

SQLite

SQLite is an embedded SQL database engine. Unlike most other SQL databases, SQLite does not have a separate server process. SQLite reads and writes directly to ordinary disk files. A complete SQL database with multiple tables, indices, triggers, and views, is contained in a single disk file.

Cassandra

Partitioning means that Cassandra can distribute your data across multiple machines in an application-transparent matter. Cassandra will automatically repartition as machines are added and removed from the cluster. Row store means that like relational databases, Cassandra organizes data by rows and columns. The Cassandra Query Language (CQL) is a close relative of SQL.

Memcached

Memcached is an in-memory key-value store for small chunks of arbitrary data (strings, objects) from results of database calls, API calls, or page rendering.

MariaDB

Started by core members of the original MySQL team, MariaDB actively works with outside developers to deliver the most featureful, stable, and sanely licensed open SQL server in the industry. MariaDB is designed as a drop-in replacement of MySQL(R) with more features, new storage engines, fewer bugs, and better performance.

AWS Lambda

AWS Lambda is a compute service that runs your code in response to events and automatically manages the underlying compute resources for you. You can use AWS Lambda to extend other AWS services with custom logic, or create your own back-end services that operate at AWS scale, performance, and security.

RethinkDB

RethinkDB is built to store JSON documents, and scale to multiple machines with very little effort. It has a pleasant query language that supports really useful queries like table joins and group by, and is easy to setup and learn.

ArangoDB

A distributed free and open-source database with a flexible data model for documents, graphs, and key-values. Build high performance applications using a convenient SQL-like query language or JavaScript extensions.

Related Comparisons

Apex vs MySQL: What are the differences?

Introduction

Data Manipulation Language (DML) vs. Structured Query Language (SQL): Apex uses DML statements to perform CRUD operations on records in the Salesforce database. On the other hand, MySQL uses SQL queries, such as SELECT, INSERT, UPDATE, and DELETE, to interact with the database. The main difference is that Apex's DML is specific to the Salesforce platform, while MySQL's SQL can be used with other database systems as well.
Object-Oriented vs. Relational Database Model: Apex is an object-oriented programming language, which means it supports features like inheritance, encapsulation, and polymorphism. It allows developers to define custom objects, classes, and relationships between them. In contrast, MySQL follows a relational database model, where data is organized into tables with rows and columns. It focuses on maintaining relationships between tables through foreign keys.
Execution Context: Server-side vs. Client-side: Apex runs on the Salesforce servers, making it a server-side language. The code is executed on the server, and the results are sent back to the client. This architecture provides the advantage of server performance and security. On the other hand, MySQL is a client-side database management system. Queries and manipulations are sent from the client to the MySQL server, and the results are returned to the client for processing.
Integration with Salesforce Platform vs. Standalone Database: Apex is tightly integrated with the Salesforce platform, allowing developers to access and manipulate data within the Salesforce ecosystem. It provides native support for Salesforce-specific features like record triggers, workflow rules, and custom objects. In contrast, MySQL is a standalone database system that can be used with various programming languages and platforms. It is commonly used for web development, e-commerce, and other applications.
Hosting and Infrastructure: Cloud vs. On-premises: Salesforce, including the Apex code, is hosted on the cloud infrastructure provided by Salesforce.com. This eliminates the need for developers to manage the underlying hardware and infrastructure. MySQL is a database management system that can be hosted either on the cloud or on-premises. It allows developers to choose the hosting option that best suits their requirements and preferences.
Scalability and Performance: Platform as a Service vs. Traditional Database: Salesforce's platform-as-a-service (PaaS) model provides built-in scalability, performance optimization, and automatic upgrades. Apex code can take advantage of these features to ensure optimal performance. MySQL, being a traditional database system, requires manual scaling and optimization to handle increasing workloads. This adds an extra layer of responsibility for developers and administrators.

Apex vs MySQL

Overview

Apex vs MySQL: What are the differences?