Lean and mean MongoDB

Apr 3, 20131 like1,710 views

MongoDB is good for startups because it simplifies schema design, requires no database setup or migrations, and has no ORM overhead. It allows for easier development by optimizing for simplicity over premature optimization. MongoDB provides a web admin interface, can be hosted on services starting from free, and code examples show it can be used to query and return JSON documents.

Lean and mean MongoDB
or why MongoDB is good for start ups

/whois olegp
● doing startups since 2000
– RIOT-E
● tech DD for investors since 2008
● Startup Sauna coach
● new venture: StartHQ

Web apps 101
● REST API centric design
● One primary data store
– Except blobs
● No premature optimization
– e.g. caching

Background Reading
● “How FriendFeed uses MySQL to store
schemaless data”
– “mariadb dynamic columns”

● “PostgreSQL as a schemaless database”

The Pros
● Simpler schema design
– Fewer many to one relationships
– Design is part of development, not separate
● No DB setup step
● No DB migrations *
● No ORMs
● JSON as query language

Hosting
● Amazon RDS: from $18
● Heroku Postgres: from $10
● MongoHQ & MongoLab: from FREE

Database as a Service
● Web admin FTW
– Saves you building your own
● No SSL
– But on AWS you can't sniff traffic
● Expensive backups
– But you can easily roll your own

Some Code

return db.getCollection("apps").find({
nameLowerCase:{
$regex:utils.prettify(request.queryParams.term)
},
verified:true
}, {
name:true, url:true
}).sort({'extractors.social.score':-1})
.limit(10).toArray().map(function(app) {
return {
label:app.name,
value:app.url
};
});

Getting Started
● try.mongodb.org
● “dailyjs lmaw”
● olegp/notes & olegp/tokenize

Summary
● Optimize for ease of development
● Do design your schema
● Do not prematurely optimize
● Have fun!

Thanks!
@olegpodsechin
starthq.com/apps/?q=mongodb

This document discusses various techniques for optimizing website performance in order to improve search engine optimization (SEO) rankings. It outlines strategies for reducing page load time such as compressing files, lazy loading images, minimizing requests, caching content, and using modules like Apache's mod_pagespeed. The document stresses that the primary goal should be improving the user experience rather than solely focusing on achieving full scores on Google's Pagespeed Insights tool.

RESTful with Drupal - in-s and out-sKalin Chernev

The document discusses building and using RESTful APIs with Drupal. It provides an overview of REST and its benefits, how data can be managed by Drupal as a REST server or client, considerations for building REST APIs, and modules and tools for working with REST in Drupal. The presentation agenda includes explaining REST, reasons to use RESTful APIs, data management paradigms in Drupal, and a demo of managing data both inside and outside of Drupal via REST.

Getting Started with MongoDB using Node.jsNic Raboy

Cloud talkUTD Computer Security Group

This document provides an introduction to cloud computing, including what cloud is, its benefits and drawbacks, common cloud service models (SaaS, PaaS, IaaS), major cloud providers, and common cloud computing services. Key cloud computing services discussed include compute services (like AWS EC2 and Google Compute Engine), databases, storage, and additional AI/ML and serverless services. The document also highlights some free cloud credits and resources available for students.

The Next Generation Software Stack: MeteorMongoDB

Meteor is the next take on agile development on the full JavaScript stack. Based on established JavaScript tools like Node, JQuery and Underscore, it still brings a fresh and integrated approach. And MongoDB is very much its heart: Minimongo implements a client side MongoDB API for manipulating your data model; Transparent replication of data between client and server; Using WebSockets, MongoDB oplog events replicate immediately to all clients, making it simple to do distributed applications "Google Docs style."

How we build VideomeKane Zhu

This document discusses how to build scalable and stable web applications using VME. It focuses on measures for scalability including using distributed databases like MongoDB, message queues for logic decoupling, and stateless microservices for frontends and backends. It also covers high availability through techniques like MongoDB replication, RabbitMQ HA, and web server clusters. Additionally, it outlines the importance of automation through testing, DevOps, and containers, as well as comprehensive monitoring of availability, performance, errors, and alerts.

Part One: Building Web Apps with the MERN StackMongoDB

This document provides an overview and agenda for a workshop on building web applications with the MERN stack using MongoDB Atlas and Google Cloud Platform. It introduces MERN stack technologies like MongoDB, Express, React, and Node.js. It discusses database concepts and shows how to get started with MongoDB Atlas, including creating a free account and building a cluster. It also outlines plans to code an exercise tracker application using MongoDB and Mongoose to explore and work with data in the MongoDB Atlas database.

Java driver for mongo dbAbhay Pai

The document discusses the Java driver for MongoDB, presenting information on why MongoDB is preferable to MySQL for large datasets from cloud computing. It then provides details on the languages supported by MongoDB, its basic storage structure of databases and collections, information on the Java driver including code repositories and APIs, key classes needed to use the driver like MongoClient and DBCollection, and plans for a demonstration using Windows 8, Java, and MongoDB driver version 2.12.3.

Pump up the JAM with Gatsby (2019)Stefan Adolf

It's lean, it's crazily fast and it's packed with features: Gatsby is a game changing static PWA generator. This talk starts with a short intro into the consolidated GraphQL content interface and how Gatsby builds pages. We’re then digging into custom content plugins that allow you to connect nearly any data source, explain Gatsby's page generation process and how editors can use MDX to embed dynamic components into their content. We conclude with a build time performance demo that renders and updates a huge amount of pages at once.

Part Two: Building Web Apps with the MERN StackMongoDB

MongoDB for Oracle Experts - OUGF Harmony 2014 Henrik Ingo

CouchDB: replicated data store for distributed proxy servertkramar

CouchDB is a document database that uses JSON documents and handles replication of data across a distributed system. It supports views generated with JavaScript MapReduce that allow querying like SQL SELECT statements. CouchDB provides pagination of view results both slowly using skip and limit parameters, and faster using startdoc and limit. The document discusses using CouchDB alongside a distributed proxy server to store and query access logs.

Ruby On RailsSawood Alam

Ruby on Rails is an open-source web framework that favors convention over configuration for rapid development and sustainable productivity. It utilizes several key principles like convention over configuration, DRY (Don't Repeat Yourself), MVC (Model-View-Controller) architecture, RESTful design, and a well-defined directory structure to make code more predictable, understandable, and maintainable. The document also briefly discusses that Rails is database agnostic and can be hosted on various platforms like Heroku.

Intro Couchdbselvamanisampath

This document introduces CouchDB, an open-source document-oriented NoSQL database that uses a RESTful API. It is schema-less and stores data in JSON format. Documents can be queried using user-defined JavaScript map/reduce functions. CouchDB supports multi-master replication and MVCC concurrency control. Examples are provided on installing CouchDB, creating databases and documents via REST calls, updating documents, and creating views. Major companies that use CouchDB are also listed.

Decoupled (Headless) DrupalDaniel Stout

The document discusses headless Drupal, which separates the front-end interface built with JavaScript frameworks from the Drupal backend which acts as an API. It outlines the benefits of this approach, popular JavaScript frameworks that can be used including Backbone.js and AngularJS, and how to implement headless Drupal using services and REST modules in Drupal 7 and the built-in capabilities in Drupal 8. Examples are provided and it's noted that Drupal is well positioned for the growing need for APIs and data-driven approaches to websites.

Wwc london-perf-appsClaire Tran

This document provides tips for improving app performance. It discusses monitoring performance to identify problems, caching to improve load times by storing frequently accessed data, scaling to handle more traffic by adding servers or services, and optimizing databases. Specific caching, scaling, and database techniques are outlined. Other miscellaneous techniques like queuing jobs, asset optimization, and edge caching are also mentioned. Links to further reading on performance topics are provided at the end.

web optimizationsGeorgi Tachev

This document provides tips for optimizing website performance, including optimizing the loading sequence, HTML, CSS, images, JavaScript, headers, fonts, and other resources. It emphasizes measuring performance before and after optimizations to identify bottlenecks and areas for further improvement. Key recommendations include minifying files, reducing file sizes, caching resources, optimizing the critical rendering path, and using a content delivery network.

Charla ro 2GeneXus

This document discusses the new Smooth responsive web design (RWD) features in GeneXus Evolution 3. The key points covered are: - The Smooth event model optimizes event execution and navigation between pages for improved performance. - Features like grid and web component refreshing, optimized Ajax navigation between pages, and transitions improve the user experience. - Web notifications are now supported to notify users of new data availability. - The event model is compatible with previous Evolution versions for a smooth migration. - The abstract editor in GeneXus now supports responsive design with features like responsive sizes, themes, rules, and conditional class properties to adapt forms across devices.

Progressive web applicationsTom Martin

Vlad zelinschi optimizing the critical rendering pathCodecamp Romania

The document discusses optimizing the critical rendering path (CRP) of a web page. The CRP refers to the steps between receiving HTML, CSS, and JavaScript and rendering pixels on the screen. These steps include parsing HTML to build the DOM tree, parsing CSS to build the CSSOM tree, combining them into a render tree, running layout to compute geometry, and painting to the screen. Optimizing the CRP means minimizing the time spent in these steps. Some tips include getting CSS to the client fast, eliminating blocking JavaScript from the CRP, and focusing on above-the-fold content. Tools like critical CSS extraction can help optimize the CRP.

Analyzing and processing FInancial Market Data on AWS with Kinesis - AWS Pop ...Florian Benz

Processing real-time market data is an essential part of financial services companies operating on the stock market. This data comes in “big and fast” - thousands of ticks per second - requiring transformation for fast and efficient access by our apps and services as well as storage for compliance and research purposes. In this session, you will learn about Scalable Capital’s evaluation journey. How we ended up with a solution around Amazon Kinesis, and how we are processing and analyzing market data now. A combination of AWS services allowed us to build a solution that is scalable, efficient and tailored to our needs. A Fargate service receives market data and puts it into Kinesis. Lambda functions transform and store data in ElastiCache. From there, the data can either be accessed in an aggregated form or streamed to other services for further processing. Amazon Kinesis Data Firehose is used to store all data on Amazon S3. Presented at the AWS Pop Up Loft Munich on November 14, 2019

Gatsby (Code.Talks) 2019Stefan Adolf

A socially Geo-localized WebNuno Khan

A faster webBakani Pilime

Service workers can improve network resilience by caching content to reduce trips to the server. Workbox is a set of libraries and tools that help generate service workers using best practices. It can integrate with build tools like Webpack. Caching layers like Redis can also be used in front of databases to provide redundancy and faster requests while protecting databases. Redis is an open source in-memory data store that can be used as a cache. The demos showed how to implement these caching strategies to improve performance.

GR8Conf 2011: Building Progressive UIs with GrailsGR8Conf

This document discusses progressive enhancement and how to build progressive user interfaces with Grails. It provides examples of using Grails features like request.xhr and withFormat to vary output for AJAX requests. It also covers techniques like separating markup and behavior, reading and enhancing markup with JavaScript, form enhancements, and test-driven progressive enhancement using Modernizr and yepnope.

Rapid Application Development with MEAN StackAvinash Kaza

This document proposes a new RAD (Rapid Application Development) approach using the MEAN stack (MongoDB, ExpressJS, AngularJS, NodeJS) to quickly build full-stack web applications. It describes how the authors built a basic TODO application over a weekend using this approach. The key advantages highlighted are the ability to build and test applications quickly at low cost, with high flexibility to change requirements later.

Introduction to JavascriptfoOfys Solutions

kranonit S06E01 Игорь Цинько: High loadKrivoy Rog IT Community

This document summarizes a presentation about designing systems to handle high loads when Chuck Norris is your customer. It discusses scaling architectures vertically and horizontally, RESTful principles, using NoSQL databases like MongoDB, caching with Memcached, search engines like Sphinx, video/image storage, and bandwidth management. It emphasizes that the right technology depends on business needs, and high-load systems require robust architectures, qualified developers, and avoiding single points of failure.

Building RESTtful services in MEANMadhukara Phatak

The document discusses the MEAN stack, which is used to build RESTful services and web applications. It consists of MongoDB for data storage, Express for building the web application, AngularJS for the front-end, and Node.js as the runtime environment. The document compares MEAN to LAMP and explains why MEAN is better suited for building RESTful APIs and web applications with its use of a single programming language and ability to directly work with JSON data without translation.

Mean stackRavikantGautam8

The document provides an overview of the MEAN stack, which is a full-stack JavaScript framework that simplifies and accelerates web application development using MongoDB, Express, AngularJS, and Node.js. It discusses each component of the MEAN stack in detail, including their features and advantages. The key advantages are that MEAN allows for fast development of robust and maintainable web applications using a single programming language across both front-end and back-end. However, MongoDB is not as robust as an SQL database and JavaScript lacks coding guidelines.

More Related Content

What's hot (19)

Pump up the JAM with Gatsby (2019)Stefan Adolf

Part Two: Building Web Apps with the MERN StackMongoDB

MongoDB for Oracle Experts - OUGF Harmony 2014 Henrik Ingo

CouchDB: replicated data store for distributed proxy servertkramar

Ruby On RailsSawood Alam

Intro Couchdbselvamanisampath

Decoupled (Headless) DrupalDaniel Stout

Wwc london-perf-appsClaire Tran

web optimizationsGeorgi Tachev

Charla ro 2GeneXus

Progressive web applicationsTom Martin

Vlad zelinschi optimizing the critical rendering pathCodecamp Romania

Analyzing and processing FInancial Market Data on AWS with Kinesis - AWS Pop ...Florian Benz

Gatsby (Code.Talks) 2019Stefan Adolf

A socially Geo-localized WebNuno Khan

A faster webBakani Pilime

GR8Conf 2011: Building Progressive UIs with GrailsGR8Conf

Rapid Application Development with MEAN StackAvinash Kaza

Introduction to JavascriptfoOfys Solutions

Pump up the JAM with Gatsby (2019)Stefan Adolf

Part Two: Building Web Apps with the MERN StackMongoDB

MongoDB for Oracle Experts - OUGF Harmony 2014 Henrik Ingo

CouchDB: replicated data store for distributed proxy servertkramar

Ruby On RailsSawood Alam

Intro Couchdbselvamanisampath

Decoupled (Headless) DrupalDaniel Stout

Wwc london-perf-appsClaire Tran

web optimizationsGeorgi Tachev

Charla ro 2GeneXus

Progressive web applicationsTom Martin

Vlad zelinschi optimizing the critical rendering pathCodecamp Romania

Analyzing and processing FInancial Market Data on AWS with Kinesis - AWS Pop ...Florian Benz

Gatsby (Code.Talks) 2019Stefan Adolf

A socially Geo-localized WebNuno Khan

A faster webBakani Pilime

GR8Conf 2011: Building Progressive UIs with GrailsGR8Conf

Rapid Application Development with MEAN StackAvinash Kaza

Introduction to JavascriptfoOfys Solutions

Similar to Lean and mean MongoDB (20)

kranonit S06E01 Игорь Цинько: High loadKrivoy Rog IT Community

Building RESTtful services in MEANMadhukara Phatak

Mean stackRavikantGautam8

Deploying Perl apps on dotClouddaoswald

Write less (code) and build more with serverlessDhaval Nagar

Creating a custom API for a headless DrupalExove

Creating a custom API for a headless Drupal involves using the Services module to define endpoints and resources. The Services module introduces endpoints, which define authentication and attach resources. Resources define CRUD operations and custom actions that can target specific resources. To create an API, endpoints and resources are configured through the Services module to expose the desired data and functionality through the custom API.

Not Your Father’s Web App: The Cloud-Native Architecture of images.nasa.govChris Shenton

Presentation to the NASA Cloud Community of Interest. Shows the evolution of simple webapps lacking resilience and scalability up to cloud-native apps that tolerate server faults and availability zone outages. Describes how images.nasa.gov leverages S3, EC2, ELB, DynamoDB, CloudSearch, ElasticTranscoder and more to provide a modern, scalable, mobile-friendly site showcasing the best of NASA's images, video and audio.

Spark Workflow ManagementRomi Kuntsman

Cloud arch patternsCorey Huinker

This document discusses PostgreSQL database architecture patterns for running PostgreSQL at scale when a relational database as a service like Amazon RDS won't meet needs. It describes challenges faced with MySQL, Redshift and Vertica and how PostgreSQL was better suited through techniques like partitioning by date, TOAST compression, foreign data wrappers, and poor man's parallel processing. Key takeaways are that PostgreSQL supported scaling to petabytes of data, sub-second queries across large date ranges, and custom extensions needed while avoiding limitations and expenses of other database options.

Jumpstart your idea with AWS Serverless [Oct 2020]Dhaval Nagar

Traveloka's journey to no ops streaming analyticsRendy Bambang Junior

Traveloka transitioned from a custom data architecture to using Google Cloud services for streaming analytics to improve scalability and reduce operational overhead. They moved from Kafka and custom Java consumers to using Cloud Pub/Sub and Cloud Dataflow for ingesting and processing streaming data. This delivered lower latency, auto-scaling, and reduced the engineering team size needed from 8 people to just 2. Traveloka's use of fully managed services like BigQuery, Cloud Storage, and Dataflow allowed them to focus on business problems rather than infrastructure.

Serverless Big Data Architecture on Google Cloud Platform at Credit OKKriangkrai Chaonithi

Serverless Big Data Architecture on Google Cloud Platform was presented by Kriangkrai Chaonithi. The presentation covered Credit OK's use of serverless architecture on GCP for their big data analytics platform. Credit OK processes large amounts of customer data from over 400 sites to perform credit scoring. They use Google Cloud Functions to ingest data from sites, as well as Compute Engine and Google Cloud Storage. This serverless architecture allows them to automatically scale infrastructure as needed, reducing costs since they only pay for resources used. While serverless architectures don't require managing servers, there are still resource limits that must be considered to avoid issues like exhausted worker pools during peak loads.

Laskar: High-Velocity GraphQL & Lambda-based Software Development ModelGarindra Prahandono

Seo for single page applicationsJustinGillespie12

This document discusses SEO challenges for single page applications (SPAs) and strategies to improve their rankings. While SPAs provide good user experiences, server-side rendered websites often rank higher in search results. The document recommends a two-pronged approach: using performance optimization techniques like pre-rendering to help crawlers index SPAs, and selectively server-side rendering high-value content to increase page rank. Tools like Lighthouse and services like Netlify and Prerender.io can help with implementation.

Evolution of DBA in the Cloud EraMydbops

Web App Prototypes with Google App EngineVlad Filippov

This document discusses using Google App Engine and its Python SDK for quickly prototyping web applications. Some key points covered include: - App Engine allows developers to build and host web apps and supports Python runtimes. It offers scalable hosting and APIs for common tasks like user auth and data storage. - The Python SDK makes it easy to quickly create prototypes by providing a local development server, a scalable datastore, and APIs that handle common tasks so developers can focus on unique features. - Examples of prototyping tasks demonstrated include adding entities to the datastore, building basic views and filters, and testing the prototype. Frameworks like webapp2 and appengine-rest-server can further accelerate the prototyping process

Postgres-XC as a Key Value Store Compared To MongoDBMason Sharp

Going Serverless with AWS Lambda at ReportGardenJay Gandhi

This document discusses using AWS Lambda for serverless web scraping. It provides an example use case of scraping business directory websites to check for incorrect or missing business listings. Traditionally this would require writing separate code for each directory, but with serverless it can be done more flexibly. The benefits of the serverless approach include increased scalability, reduced costs since functions only run when needed, and easier integration with other AWS services. The document demonstrates setting up a serverless framework for asynchronous web scraping using AWS Lambda, SNS, and API Gateway.

The great migration embracing serverless first AngelaTimofte1

Serverless architectures can reduce operational cost and development time but it does come with an architectural overhead and complexity. In this talk you'll get an insight on how Trustpilot adopted a serverless mindset. The benefits and challenges of migrating and refactoring our systems having a serverless first approach. Learn how we mitigated the complexity of our services and cut down the cost on our infrastructure.

Dust.jsYevgeniy Brikman

The document discusses LinkedIn's adoption of the Dust templating language in 2011. Some key points: - LinkedIn needed a unified view layer as different teams were using different templating technologies like JSP, GSP, ERB. - They evaluated 26 templating options and selected Dust as it best met their criteria like performance, i18n support, and being logic-less. - Dust templates are compiled to JavaScript for client-side rendering and to Java for server-side rendering (SSR) through Google's V8 engine, allowing templates to work on both client and server. - SSR addresses challenges like SEO, supporting clients without JavaScript, and i18n by rendering

kranonit S06E01 Игорь Цинько: High loadKrivoy Rog IT Community

Building RESTtful services in MEANMadhukara Phatak

Mean stackRavikantGautam8

Deploying Perl apps on dotClouddaoswald

Write less (code) and build more with serverlessDhaval Nagar

Creating a custom API for a headless DrupalExove

Not Your Father’s Web App: The Cloud-Native Architecture of images.nasa.govChris Shenton

Spark Workflow ManagementRomi Kuntsman

Cloud arch patternsCorey Huinker

Jumpstart your idea with AWS Serverless [Oct 2020]Dhaval Nagar

Traveloka's journey to no ops streaming analyticsRendy Bambang Junior

Serverless Big Data Architecture on Google Cloud Platform at Credit OKKriangkrai Chaonithi

Laskar: High-Velocity GraphQL & Lambda-based Software Development ModelGarindra Prahandono

Seo for single page applicationsJustinGillespie12

Evolution of DBA in the Cloud EraMydbops

Web App Prototypes with Google App EngineVlad Filippov

Postgres-XC as a Key Value Store Compared To MongoDBMason Sharp

Going Serverless with AWS Lambda at ReportGardenJay Gandhi

The great migration embracing serverless first AngelaTimofte1

Dust.jsYevgeniy Brikman

More from Oleg Podsechin (14)

Why SaaS (in Helsinki)?Oleg Podsechin

This document discusses SaaS (software as a service) trends in Europe and Finland. It notes that there are many small SaaS companies in Europe but few experienced early stage investors. In Finland, established software companies are starting to offer SaaS but focused on the domestic market. The author proposes a Helsinki SaaS Meetup to help companies understand how to build successful SaaS businesses by focusing on customers rather than just technology. Characteristics of both "bad SaaS" and "badass SaaS" are outlined.

Staying safe in the cloudOleg Podsechin

This document discusses various ways to stay safe in the cloud, including ensuring availability, reliability, and privacy. It outlines potential attack vectors like social engineering, packet sniffing, and zero-day exploits. Some recommended countermeasures include encrypted drives, strong passwords, two-factor authentication, and security audits. The document also discusses trade-offs between self-reliance and reliability as well as security and convenience. It notes that while security is important, users often don't care if a service gets hacked and every service will likely experience a breach at some point.

Tips from angular js users anonymousOleg Podsechin

AngularJS - the folly of choiceOleg Podsechin

Toolkits provide libraries that require assembly, while frameworks call the developer. AngularJS was designed to remove DOM manipulation code, using declarative templates and two-way binding instead of imperative code. It features scopes, modules, dependency injection, routing, directives, services, events, filters and promises to build web apps. Testing is important with AngularJS's inversion of control and removal of global state.

RingoJSOleg Podsechin

RingoJS is a JavaScript platform that runs on the JVM. It was started by Hannes Wallnöfer and is the successor to Helma and HelmaNG. RingoJS conforms to CommonJS standards and supports features like hot reloading, profiling, debugging, and sandboxing. It can run as a standalone process or within a web application container since it runs on the JVM. Examples are provided of using RingoJS for multithreaded JavaScript and web applications using libraries like Stick. Community support is available on IRC and Twitter. RingoJS can be used for standalone applications, extending existing Java web apps, and code reuse between server and client-side JavaScript.

JS everywhere 2011Oleg Podsechin

The document discusses the future of server-side JavaScript. It covers various Node.js frameworks and libraries that support both synchronous and asynchronous programming styles. CommonJS aims to provide interoperability across platforms by implementing synchronous proposals using fibers. Examples demonstrate how CommonJS allows for synchronous-like code while maintaining asynchronous behavior under the hood. Benchmarks show it has comparable performance to Node.js. The author advocates for toolkits over frameworks and continuing development of common standards and packages.

What every developer can learn from startupsOleg Podsechin

Server side JavaScript: going all the wayOleg Podsechin

Node has captured the attention of early adopters by clearly differentiating itself as being asynchronous from the ground up while remaining accessible. Now that server side JavaScript is at the cutting edge of the asynchronous, real time web, it is in a much better position to establish itself as the go to language for also making synchronous, CRUD webapps and gain a stronger foothold on the server. This talk covers the current state of server side JavaScript beyond Node. It introduces Common Node, a synchronous CommonJS compatibility layer using node-fibers which bridges the gap between the different platforms. We look into Common Node's internals, compare its performance to that of other implementations such as RingoJS and go through some ideal use cases.

Current State of Server Side JavaScriptOleg Podsechin

On PlatformsOleg Podsechin

Common NodeOleg Podsechin

The future of server side JavaScriptOleg Podsechin

The document discusses the future of server-side JavaScript. It provides reasons for using JavaScript on the server, including that it is the lingua franca of the web, allows for code reuse between server and client, and supports asynchronous programming well. It also discusses JavaScript engines, CommonJS modules and packages, environments like Node.js and RingoJS, and trends like wider adoption and cloud-based IDEs.

RingoJSOleg Podsechin

This document summarizes RingoJS, an open source JavaScript platform that runs on the Java Virtual Machine. It can install and run with a few commands, supports CommonJS modules and features like a REPL, debugger, profiling, and running synchronous and asynchronous code. The document provides code examples for a simple "Hello World" app, a JSONP proxy, parallel processing using threads, and links to RingoJS libraries and community resources.

Grid and Cloud Computing IntroOleg Podsechin

The document discusses how distributed computing using grids and cloud computing will change the media world. It outlines how virtualization of resources, open source components, billing systems, service level agreements, and infrastructure as a service allows for commercial grids. This enables increased efficiency, flexibility to deal with demand surges, and opportunities for applications to rapidly develop and deploy using scalable processing, bandwidth, and storage resources. However, there are also cons such as high provider lock-in and reliability issues. The document questions what other new resource types like mobile devices could enable when added to grids.

Why SaaS (in Helsinki)?Oleg Podsechin

Staying safe in the cloudOleg Podsechin

Tips from angular js users anonymousOleg Podsechin

AngularJS - the folly of choiceOleg Podsechin

RingoJSOleg Podsechin

JS everywhere 2011Oleg Podsechin

What every developer can learn from startupsOleg Podsechin

Server side JavaScript: going all the wayOleg Podsechin

Current State of Server Side JavaScriptOleg Podsechin

On PlatformsOleg Podsechin

Common NodeOleg Podsechin

The future of server side JavaScriptOleg Podsechin

RingoJSOleg Podsechin

Grid and Cloud Computing IntroOleg Podsechin

Lean and mean MongoDB

1. Lean and mean MongoDB or why MongoDB is good for start ups

2. /whois olegp

4. /whois olegp ● doing startups since 2000 – RIOT-E ● tech DD for investors since 2008 ● Startup Sauna coach ● new venture: StartHQ

5. Web apps 101

7. Web apps 101 ● REST API centric design ● One primary data store – Except blobs ● No premature optimization – e.g. caching

8. The Contenders

10. Background Reading ● “How FriendFeed uses MySQL to store schemaless data” – “mariadb dynamic columns” ● “PostgreSQL as a schemaless database”

11. The Pros

13. The Pros ● Simpler schema design – Fewer many to one relationships – Design is part of development, not separate ● No DB setup step ● No DB migrations * ● No ORMs ● JSON as query language

15. Hosting ● Amazon RDS: from $18 ● Heroku Postgres: from $10 ● MongoHQ & MongoLab: from FREE

16. Database as a Service

18. Database as a Service ● Web admin FTW – Saves you building your own ● No SSL – But on AWS you can't sniff traffic ● Expensive backups – But you can easily roll your own

19. Some Code return db.getCollection("apps").find({ nameLowerCase:{ $regex:utils.prettify(request.queryParams.term) }, verified:true }, { name:true, url:true }).sort({'extractors.social.score':-1}) .limit(10).toArray().map(function(app) { return { label:app.name, value:app.url }; });

20. Tools ● 10gen MMS ● Metrica ● Nodetime

21. Getting Started

23. Getting Started ● try.mongodb.org ● “dailyjs lmaw” ● olegp/notes & olegp/tokenize

24. Summary ● Optimize for ease of development ● Do design your schema ● Do not prematurely optimize ● Have fun!

25. Thanks! @olegpodsechin starthq.com/apps/?q=mongodb

Lean and mean MongoDB

Recommended

More Related Content

What's hot (19)

Similar to Lean and mean MongoDB (20)

More from Oleg Podsechin (14)

Lean and mean MongoDB