Hosted Cloud SQL instance in Google Cloud

relational database

Persistent data store.

Backing data store.

MySQL is the primary datastore, this is setup in a Master/Slave configuration, with offsite replicas.

Our choice for data storage.

Banco de dados principal da aplicação

Database

To have a database.

MySQL is our database of choice for storage of relational user data.

High performance RDBMS

Database

We support MySQL databases so that developers can interact with their data.

Common database store for basic admin to advanced databases, high performance, highly maintainable.

Relational content, such as user data, posts, logs and other relevant but not so heavy data. Consumed by web servers.

As the baseline database in which to:

• install Drupal core
• store any data created by the user during a session

Accounts/Payments database

Where the data lives.

Website data storage

I am not using this DB for blog posts or data stored on the site. I am using to track IP addresses and fully qualified domain names of attacker machines that either posted spam on my website, pig flooded me, or had more that a certain number of failed SSH attempts.

The RDS type.

Simple and Fast

One of the RDBMS that can be used for this CRUD module.

A MySQL database stores the instructions and messages sent and received respectively.

For Laravel projects

Most of the data in ZATEMAS is stored in MySQL.

Ordinary database

MySQL is used as Database Server, is default option for Wordpress environment.

MySQL with InnoDB is a good all-purpose storage software.

I initially used MySQL as the database backend for the service. Thanks to JDBC (and some discipline), it was easy to swap in Oracle during deployment.

Store all the blog data

MySQL is where most of our data lies, it's old but it's easier for us from BigData background to use and build on top of. If the data is properly indexed and the servers properly sharded, MySQL is quite performant.

We can pull real potential out of MySQL expressions, sub-selects with our relational models.

Wordpress & Laravel

Server-side data store.

Our Ghost blog relies on MySQL.

Local OS X test server runs on this.

Main Database

mammoths ?:D

Like that first girlfriend you had. It makes us feel alive, in a fun way.

My database of choice. Nothing like it. Except maybe other databases..

Setup web server as service and user/database management for developer team.

Used MySQL as ORM managed database in application development. (Hibernate/Sequalize)

Data warehouse for storing anonymized/de-identified student data for analysis and reporting purposes.

Used lightly. Part of Wordpress stack

We formerly used MySQL instead of MariaDB but shifted exclusively to the latter. MySQL is a part of our Stack anyways, as we still use the MySQL-Syntax/Architecture.

I am using mysql as my relational database engine

expert

mysql 에는 엔진이 있는데 요즘은 다 innodb를 사용 한다. 하지만 오래된 버전의 경우 myisam을 사용하는데.....트랜젝션이 안된다. 트랜젝션이 필요하다면 반드시 innodb를 쓰자 꼭!!

Google Cloud Platform - our Data Library is in Cloud SQL (MySql)

Used as main storage for user settings, account settings, etc. (Our social data itself resides in ElasticSearch.)

MySQL stores permanent data such as user logins.

Easy to use, basic relationship DB without any sharp corners, where examples "just work".

Oracle을 통해 RDB를 학습했지만, MySQL과 mariaDB도 차이를 분석하며 학습하고 있습니다.

Transactional database for the application

Used it at almost every job I've had.

라이센스가 오락가락 하는 MySQL을 대체하기 위해 파생된 DBMS. 기존 MySQL과 거의 완벽하게 명령어/구조가 같아 누구나 쉽게 넘어올 수 있는 오픈소스 소프트웨어.

One of our datasources for Ataccama ONE platform.

Long-lived data is stored in MySQL, period. Everything from users, to scores, to beatmaps, anything.

Prime DB for all our customers website and web apps.

Database

Used to store Relational data for services

Our main database.

widely used

Basic mysql

The existing WordPress database had been built on MySQL, a large portion of the API is built around configuring the endpoints for the data that already exists in this database.

Store orders from the rapid order widget located on the modafinil online page.

DD Configurations

Database

MySQL is the database system we use.

타 팀의 요청에 의해 sql 쿼리를 실행시키지만

보통은 spring의 orm을 사용해 mysql을 실행합니다

We use MySQL (or MariaDB) as our main database.

1.It's very popular. Heared about it in Database class 2. The most comprehensive set of advanced features, management tools and technical support to achieve the highest levels of MySQL scalability, security, reliability, and uptime. 3. MySQL is an open-source relational database management system. Its name is a combination of "My", the name of co-founder Michael Widenius's daughter, and "SQL", the abbreviation for Structured Query Language.

Transaction Database

Best db storage.

Used MySQL for storing statistics.

Very easy to use, design and deploy innoDB servers. Open migration path to Amazon Aurora RDS.

I use MySQL because it's fast and reliable. I use it to store all of the info I get from my users and Roblox.

Our relational database to store all information, users, products, etc.

We use MySQL and variants thereof to store the data for our projects such as the community. MySQL being a well established product means that support is available whenever it is required along with an extensive list of support articles all over the web for diagnosing issues. Variants are also used where needed when, for example, better performance is needed.

I SQL sometimes.

Pretty simple - it's our chosen database system. Widely used, proven and stable.

MySQL is a freely available open source Relational Database Management System (RDBMS) that uses Structured Query Language (SQL). SQL is the most popular language for adding, accessing and managing content in a database. It is most noted for its quick processing, proven reliability, ease and flexibility of use.

MySQL boasts rigorous I/O allowing Hndhld to serve content to thousands of users in the blink of an eye.

Developing programming skills. managing relational database management systems, database analytics, and for data processing.

Database

For support reason

Main database for the application

database sql

Base de datos master.

We use MySQL as our main database.

We strongly prefer Postgres over mysql. We don't use MySQL.

MySQL is used in Shiro, Kuro and Shirogane.

The data used to run the whole stack is saved as SQL in databases like MySQL.

convenient Database for Cordova.

• We are used MySQL database to build the Online Food Ordering System

  • Its best support normalization and all joins ( Restaurant details & Ordering, customer management, food menu, order transaction & food delivery).
  • Best for performance and structured the data.
  • Its help to stored the instant updates received from food delivery app ( update the real-time driver GPS location).

Database purposes

Database

MongoDB fills our more traditional database needs. We knew we wanted Trello to be blisteringly fast. One of the coolest and most performance-obsessed teams we know is our next-door neighbor and sister company StackExchange. Talking to their dev lead David at lunch one day, I learned that even though they use SQL Server for data storage, they actually primarily store a lot of their data in a denormalized format for performance, and normalize only when they need to.

The everything store.

Mongo powers our data

Used to be MySQL, but once moved to MongoDB, everything just speed up dramatically, data became pretty and easy to work with. Sophisticated aggregations allow us to run complicated analytics anytime as easy as possible.

Store image metadata.

Nearly all of our backend storage is on MongoDB. This has also worked out pretty well. It's enabled us to scale up faster/easier than if we had rolled our own solution on top of PostgreSQL (which we were using previously). There have been a few roadbumps along the way, but the team at 10gen has been a big help with thing.

Our NoSql data storage. Provided to us through Modulus.

Main storage

We use MongoDB as the database server for all infra configuration/settings.

Used MongoDB as primary database. It holds trip data of NYC taxis for the year 2013. It is a huge dataset and it's primary feature is geo coordinates with pickup and drop off locations. Also used MongoDB's map reduce to process this large dataset for aggregation. This aggregated result was then used to show visualizations.

MongoDB is only used as session storage since storing session in Firebase is not feasible.

로그성 데이터는 mongodb 에 기록됩니다. 뛰어난 성능이 강점입니다만 NOSQL 의 특성을 이해하지 못하고 사용할 경우에는 오히려 독이 될 수 있습니다.

Big datasets not likely to need joins with another dataset go in Mongo to offload Postgresql

As primary database

in conjunction with Meteor, database alternative

This is our DB.

So much more flexible than SQL …

Primary product data store

Primary app data store.

We use Mongo for persistent storage and retrieval. We also use a nifty Mongo ODM, Mongoose (available from NPM), to model our schemas and connect to Mongo on our private VLAN.

We support Mongo databases so that developers can interact with their data.

Main database

Our main datastore

Our data storage, for the most part is handled by a set of MongoDB storage clusters handling all the persistent information needed for our apps.

Hosts the unstructured data for each event that comes into the system. Also maps the event to each individual job or pipeline that gets spun off. All relevant persistent data is currently stored here.

Data layer

Backend account data storage.

In conjunction with Mongoose.js as a Node.js interface for MongoDB, I utilize this service to store user/feedback information.

Data storage of ITFrame

Notifications and analytics.

Great data store for JSON objects, which is mostly what I need.

Document oriented distriubted storage

Because you don't know what data you will be querying for. Perfectly suited for rapid prototyping. Altering tables in traditional, relational DBMS is painfully expensive and slow.

Performance is not great though. Ah who cares!

MongoDB is used as a datastore for accounts and users and underlying storage engine for databases.

Models in Agile Toolkit support NoSQL databases including MongoDB.

Main data storage, Has a secondary cache and stores our time series reports.

MongoDB is our prefered document store for pretty much all non-relational-heavy development. MongoDB scales beautifully and provides us with very polished api's and drivers. Easy to use, flexible and scalable.

some logger with it's own isolated collection

backend data store container

Replicated high-availability and high-performance database.

Backend of the app

Used Mongodb for web application development.

Saving Application data

Yes, we use Mongo

Backend server

MySQL was yesterday... MongoDB rocks. Check out s for smartdata on npm for MongoDB with TypeScript support.

Primary document store backend for the API

Unstructured No-SQL DB was important as deal with several different devices.

The backend for Parse Server.

System's main database

While the huge majority of BI data comes from 3rd-party sources, some pieces require ad-hoc sources - this is largely where Mongo comes into play. Views such as "Activity Log" need on-the-fly recordkeeping that's best manually entered; considering that fetching from a task manager API will paint an overwhelming or inaccurate picture of the month's activity.

Auxiliary storage for service data and settings. GridFS as storage for binary data

We are testing out MongoDB at the moment. Currently we are only using a small EC2 setup for a delayed job queue backed by agenda. If it works out well we might look to see where it could become a primary document storage engine for us.

Schema-less, JS in the console, flexible, fast, and pairs well with node/Mongoose.

타임라인 반응 데이터 및 로그 데이터 저장

OpenStack 내부의 메터링 서비스 데이터 기록을 위한 DB로 잠깐 사용했었다.

다이어리 앱의 사용자 및 다이어리 데이터는 MongoDB로 관리합니다.

Data storage.

The Geospatial features are the easiest to get up and running and easiest to scale beyond single servers. On top of that NoSQL allows us to iterate features at the speed of light.

We use Mongo for storage

Backend and analytics database.

Easy to develop with, can make changes to schemas easily.

Persistence database to store any data

Native integration with meteor

We used MongoDB to implement a filesystem abstraction for the application (i.e. each user has his/her own home directory and can share them, etc.)

Primary DB

For document (attachments) storage and associated metadata

Easy to use for small projects

Persistence Database

NoSQL of choice

MongoDB is used to store most of our data, both user-related (e.g. documents, contacts etc.) and global.

Leading document (JSON) database

We use MongoDB as our main NoSQL repository for data.

Out main storage.

Stores database items in document format. Doesn't require a schema declaration.

Mandatory database in meteor.js, stores user profiles

If we encounter multi-level or complex objects, we usually go with mongo/document/cosmos DBs. Getting better in detecting such objects and moving them here.

Base de données

PrometheanTV uses MongoDB as the primary transactional database that powers the platform. MongoDBs are hosted on both EC2 instances as well as via the MLab MongoDB cloud.

Database purposes

Our database are with MongoDB data store.

Store all of our unstructured data in a fast and efficient way.

By being built on, of, in and around CouchDB, Smileupps offers to its customers secure and reliable CouchDB hosting and a CouchDB-based app store to build and sell serious business-enabled web applications

Storage for unstructured, linked and timeseries data.

We use CouchDB in an internal analysis tool for usage data.

json store + geo + _changes

Document (JSON) DB.

• - queries must be pre-defined as views (not as flexible as query formulation on the fly)
• - community and ecosystem not as large as mongodb
• + PouchDB is an excellent JS library to interact with CouchDB or even work in offline-then-sync moce