mongodb atlas

This article was originally published on MongoDB. Thank you for supporting the partners who make SitePoint possible.

本文最初在MongoDB上发布。 感谢您支持使SitePoint成为可能的合作伙伴。

Not unlike other startups, Blinkist grew its roots in a college dorm. Only, its creators didn’t know it at the time. It took years before the founders decided to build a business on their college study tricks. Blinkist condenses nonfiction books into pithy, but accessible 15-minute summaries which you can read or listen to via its app.

与其他初创公司不同,Blinkist扎根于大学宿舍。 只是,它的创造者当时还不知道。 创始人花了好几年的时间才决定利用他们的大学学习技巧来开展业务。 Blinkist将非小说类书籍浓缩为精妙的 15分钟摘要,您可以通过其应用阅读或收听。

“It all started with four friends,” says Sebastian Schleicher, Director of Engineering at Blinkist. “After leaving university, they found jobs and built lifestyles that kept them fully occupied—but they were pretty frustrated because their packed schedules left them no time for reading and learning new things.”

“这一切始于四个朋友,” Blinkist的工程总监Sebastian Schleicher说。 “离开大学后,他们找到了工作并建立了自己的生活,使他们完全忙着工作,但他们感到非常沮丧,因为他们的日程安排使他们没有时间阅读和学习新事物。”

Rather than resign themselves to a life without learning, they racked their brains as to how they could find a way to satisfy their craving for knowledge. They decided to revive their old study habits from university where they would write up key ideas from material that they’d read and then share it with each other. It didn’t take long for them to realise that they could build a business on this model of creating valuable easily accessible content to inspire people to keep learning. In 2012, Blinkist was born.

他们没有沉迷于没有学习的生活,而是绞尽脑汁地思考如何找到一种方法来满足对知识的渴望。 他们决定从大学中恢复过去的学习习惯,在大学中,他们将从阅读的材料中写下关键思想,然后彼此分享。 他们很快就意识到,他们可以在这种模式下建立业务,以创建有价值的易于访问的内容来激励人们继续学习。 2012年,Blinkist诞生了。

Six years later, the Berlin-based outfit has nearly 100 employees, but instead of writers and editors, they have Tea Masters and Content Ninjas. Blinkist has no formal hierarchical management structure, having replaced bosses with BOS, the Blinkist Operating System. The app has over five million users and, at its foundation, it has MongoDB Atlas, the fully managed service for MongoDB, running on AWS. But it didn’t always.

六年后,这家位于柏林的公司拥有近100名员工,但他们没有茶作家和编者,而是茶大师和内容忍者。 Blinkist没有正式的分层管理结构,已经用BOS( Blinkist操作系统)代替了老板。 该应用程序拥有超过500万用户,其基础是运行在AWS上的MongoDB完全托管服务MongoDB Atlas 。 但这并不总是如此。

“In four years, we had a million users and 2,500 books,” says Schleicher. “We’d introduced audiobooks and seen them become the most important delivery channel. We tripled our revenue, doubled our team, moved into a larger, open-plan office, and even got a dog. Things were good.”

“在四年内,我们拥有100万用户和2500本书,” Schleicher说。 “我们介绍了有声读物,并看到它们成为最重要的交付渠道。 我们的收入增加了两倍,团队增加了一倍,搬进了一个更大的开放式办公室,甚至还养了一条狗。 一切都很好。”

第三方MongoDB即服务遇到麻烦 (Running into trouble with 3rd party MongoDB as a Service)

Then came an unwelcome plot twist. Blinkist had built its service on Compose, a third-party database as a service, based on MongoDB. MongoDB had been an obvious choice as the document model provided Blinkist with the flexibility needed to iterate quickly, but the team was too lean to spend time on infrastructure management

然后出现了不受欢迎的情节转折。 Blinkist已在基于MongoDB的第三方数据库即服务Compose上构建了服务。 MongoDB是一个显而易见的选择,因为文档模型为Blinkist提供了快速迭代所需的灵活性,但是该团队过于精简,无法花时间在基础架构管理上

In 2016, Compose unexpectedly decided to change the architecture of its database, creating major obstacles for Blinkist as they would become locked in to an old version of MongoDB. “They left us alone,” says Schleicher. “They said, ‘Here’s a tool, migrate your data.’ I asked if they’d help. No dice. I offered them money. Not interested, no support. After being a customer for all those years? I said goodbye.”

在2016年,Compose意外地决定更改其数据库架构,给Blinkist造成了重大障碍,因为它们将被锁定在旧版本的MongoDB中。 “他们让我们一个人呆着,” Schleicher说。 “他们说,'这是一个工具,可以迁移您的数据。' 我问他们是否有帮助。 没有骰子。 我给他们钱。 不感兴趣,不支持。 这些年来都是客户吗? 我说再见。”

After years of issues, it became clear last year that Blinkist would need to leave Compose, which meant choosing a new database provider. “We looked at migrating to MySQL, we were that desperate. That would have meant freezing development and concentrating on the move ourselves. On a live service. It was bleak.”

经过多年的讨论,去年很明显Blinkist需要离开Compose,这意味着选择新的数据库提供商。 “我们曾考虑过迁移到MySQL,这真是令人绝望。 那将意味着冻结发展并自己专注于行动。 上线服务。 太暗了。”

发现MongoDB地图集 (Discovering MongoDB Atlas)

By this time, MongoDB’s managed cloud Atlas service was well established and seemed to be the logical solution. “We downloaded MongoDB’s free mongomirror service to make the transition,” says Schleicher, “but we hit a brick wall. Compose had locked us into a very old version of the database and who knows what else, and we couldn’t work it out.”

到这个时候,MongoDB的托管云Atlas服务已经很好地建立了,并且似乎是合理的解决方案。 Schleicher表示:“我们下载了MongoDB的免费mongomirror服务以进行过渡,但我们遇到了mongomirror 。 Compose已将我们锁定在一个非常旧的数据库版本中,谁知道其他内容,我们就无法解决。”

At that point, Schleicher made a call to MongoDB. MongoDB didn’t say, ‘Do it yourself.’ Instead, they sent their own data ninja—or, in more conventional, business-card wording, a principal consulting engineer. “It was the easiest thing in the world,” Schleicher remembers. “In one day, he implemented four feature requests, got the migration done and our databases were in live sync. Such a great experience.”

那时,Schleicher致电MongoDB。 MongoDB没有说“自己动手”。 相反,他们发送了自己的数据忍者-或更传统的名片文字是首席咨询工程师。 “这是世界上最容易的事情,”施莱希尔回忆道。 “有一天,他实现了四个功能请求,完成了迁移,并且我们的数据库处于实时同步状态。 很棒的经历。”

Now that Blinkist is on Atlas, Schleicher feels like they have a very solid base for the future. “Performance is terrific. Our mobile app developers accidentally coded in a distributed denial of service attack on our own systems. Every day at midnight, in each time zone, our mobile apps all simultaneously sync. This pushes the requests load up from a normal peak of 7,500 requests a minute to 40,000 continuous. That would have slaughtered the old system, with real business impacts—killing sign-ups and user interactions. This time, nobody noticed anything was wrong.”

现在Blinkist在Atlas上,Schleicher感到他们为未来奠定了坚实的基础。 “性能很棒。 我们的移动应用程序开发人员不小心在我们自己的系统上进行了分布式拒绝服务攻击的编码。 每天午夜,每个时区,我们的移动应用程序都同时同步。 这将请求负载从正常的高峰(每分钟7500个请求)提高到连续的40,000个。 那会破坏旧的系统,并产生实际的业务影响—杀死注册和用户交互。 这次,没有人注意到有什么问题。”

Right now it feels like we have a big tech advantage. With MongoDB Atlas and AWS, we’re on the shoulders of people who can scale the world. I know for the foreseeable future I have partners I can really rely on.

目前看来,我们拥有巨大的技术优势。 借助MongoDB Atlas和AWS,我们站在了可以扩展世界的人们的肩膀上。 我知道在可预见的将来,我有可以依靠的伙伴。

Sebastian Schleicher, Director of Engineering, Blinkist

Blinkist工程总监Sebastian Schleicher

Schleicher adds: “We’re building our future through microarchitecture with all the frills. Developers know they don’t have to worry about what’s going on behind the API in MongoDB. It just works. We’re free to look at data analytics and AI—whatever techniques and tools we believe will help us grow—and not spend all our time maintaining a monolithic slab of code.”

Schleicher补充说:“我们正在通过微架构与所有的装饰来构建我们的未来。 开发人员知道,他们不必担心MongoDB中API背后的功能。 它只是工作。 我们可以自由地研究数据分析和AI,无论我们相信哪种技术和工具都能帮助我们发展,而不必花费所有时间来维护完整的代码段。”

With Blinkist’s global ambitions, scaling isn’t just a technical challenge; it tests company culture—no matter how modern—to the limits. MongoDB’s own customer focused culture, it turns out, is proving as compatible as MongoDB’s data platform.

借助Blinkist的全球野心,扩展不仅仅是技术上的挑战。 它可以测试公司文化(无论多么现代)达到极限。 事实证明,MongoDB自己的以客户为中心的文化被证明与MongoDB的数据平台一样兼容。

“Talking to MongoDB isn’t like being exposed to relentless sales pressure. It’s cooperative, it’s reassuring. There are lots of good technical people on tap. It’s holistic, no silos, whatever it takes to help us.”

“与MongoDB交流并不像面临无休止的销售压力。 合作,令人放心。 有很多优秀的技术人员可供使用。 这是整体的,没有孤岛,无论需要什么帮助我们。”

This partnership is helping make Blinkist a great place to be a developer.

这种伙伴关系使Blinkist成为开发人员的理想之地。

“A new colleague we hired last year told me we’ve created an island of happiness for engineers. Once you have an understanding of the business needs and vision, you get to drive your own projects. We believe in super transparency. Everyone is empowered.”

“我们去年聘用的一位新同事告诉我,我们为工程师们创造了一个幸福的小岛。 一旦了解了业务需求和愿景,就可以推动自己的项目。 我们相信超级透明。 每个人都有能力。”

“Oh, and did I mention we have a dog?”

“哦,我提过我们有狗吗?”

Atlas is the easiest and fastest way to get started with MongoDB. Deploy a free cluster in minutes.

Atlas是MongoDB入门的最简单,最快的方法。 数分钟内即可部署一个免费集群。

翻译自: https://www.sitepoint.com/how-blinkist-powers-millions-of-users-on-mongodb-atlas/

mongodb atlas

mongodb atlas_Blinkist如何在MongoDB Atlas上为数百万用户提供支持相关推荐

  1. 如何在 Windows 10 上为单个用户安装应用程序

    Windows 10 上的应用程序通常都安装到同一个文件夹,即 C 驱动器中的 Program Files 或 Program Files (86) 文件夹.当您完成应用程序的初始安装步骤时,它将提供 ...

  2. MongoDb进阶实践之一 如何在Linux系统上安装和配置MongoDB

    一.NoSQL数据简介 1.NoSQL概念 NoSQL(NoSQL = Not Only SQL ),意即"不仅仅是SQL",是一项全新的数据库革命性运动,早期就有人提出,发展至2 ...

  3. MongoDB年终大会转移至线上进行 | 周五参会指南

                                                             会议调整通知 社区的朋友.各位mongoer,大家好! 前阵子我们一直准备着能够跟大家 ...

  4. mongodb 字段检索_如何在MongoDB中创建,检索,更新和删除记录

    mongodb 字段检索 介绍 (Introduction) MongoDB is a free and open-source NoSQL document database used common ...

  5. 【大咖有约】MongoDB 大中华区首席技术顾问唐建法:如何在MongoDB中实现强事务...

    MongoDB 大中华区首席技术顾问唐建法先生将作为DTCC 2016中国数据库技术大会特邀嘉宾出席.并将于5月12日大会分会场2分享题为<如何在MongoDB中实现强事务>的演讲,敬请期 ...

  6. Adhesive框架系列文章--Mongodb数据服务模块使用(上)

    之前介绍的应用程序信息中心模块中所有日志.异常.性能和状态数据都依赖Mongodb数据服务,Mongodb数据服务的接口也简单的可以: public interface IMongodbInsertS ...

  7. mongodb android,如何在Android中连接到MongoDB数据库?

    compile 'org.mongodb:mongo-java-driver:2.13.2' 我跑我的Android应用摇篮粉碎后. 如果我直接添加罐子,我的应用程序无论如何都会粉碎. 连接下面的代码 ...

  8. (翻译) MongoDB(13) 在 Ubuntu 上安装MongoDB社区版

    概述 使用这个教程在 LTS Ubuntu Linux 使用 .deb 软件包安装 MongoDB 社区版. Ubuntu 包含自己的 MongoDB 软件包, 但官方的 MongoDB 社区版包通常 ...

  9. mongodb @aggregation 返回字段映射不上_Spring Boot 操作 MongoDB

    MongoDB 测试数据,导入 MongoDB https://gitee.com/shizidada/moose-resource/raw/master/shici_item.json Spring ...

最新文章

  1. git pull 默认拉取远端其他分支 问题解决
  2. group by具有去重的功能
  3. mysql常用的视图_MySQL视图
  4. Android Studio打开DDMS : An error has occurred URIUtil
  5. 10个最常见的数据库缺陷
  6. python 重载的实现(single-dispatch generic function)
  7. 再一次站在捆绑销售风口的携程该何去何从?
  8. Eclipse中最有用的快捷键组合
  9. Java中System.getProperty()的作用及使用
  10. Oracle 数据库基本知识概念
  11. 如何计算虚拟化vcpu_【虚拟化实战】VM设计之一vCPU
  12. 现货黄金的点差费用是怎么收的
  13. 通达信日线数据转换为feather格式,提高后续数据处理速度
  14. 实战演练 | Navicat Premium 轻松连接阿里云云数据库
  15. 多对多关系需要建立中间表_【数据库基础】为什么需要三张表之多对多表结构设计...
  16. 丢手帕问题 java_丢手帕问题java 实现
  17. 如何区分研究背景与研究意义
  18. MATLAB台大郭彦甫老师课程笔记:第四课:基础绘图
  19. Flink菜鸟教程(二)——时间概念
  20. 关于RoboMaster2019新型能量机关的一些感想(大风车)

热门文章

  1. 捷联式惯性导航基础知识(一)
  2. 新闻稿写作的具体要求是什么?
  3. 8月1日云栖精选夜读:独家:阿里巴巴DevOps落地实践玩法及思路解析
  4. 会计人必知的会计实务知识及操作流程bbs.canet
  5. C语言连接MySQL(Windows)
  6. oracle中fm990.9,国内主要FM电台频率数据.doc
  7. java酒店的点评功能实现,基于JAVA的酒店管理系统
  8. 中国养老产业投资趋势与发展动态分析报告2022-2028年版
  9. 2018专业就业率排行出炉,就业率最高的专业是它!
  10. IDEA创建mybatis框架web项目