Case-study on how Industries are using MongoDB.
What is MongoDB ?
MongoDB is a general purpose, document-based, distributed database built for modern application developers and for the cloud era . It is a document database with the scalability and flexibility that we want with the querying and indexing that you need.
MongoDB stores data in JSON-like documents with dynamic schema. This means we can store our records without worrying about the data structure such as the number of fields or types of fields to store values .
Case-Study on “How Toyota Using MongoDB”
Toyota Material Handling and Industry 4.0 — Creating a Smart Factory By Moving from Monolith to Microservices, Microsoft Azure and MongoDB Atlas
Plan.
Toyota Material Handling Europe is building both the machines and the data platforms, that will make this historic shift in manufacturing a success. Toyota is famous for the quality of its vehicles. Now that same standard is being applied to how its development teams create Internet of Things software that will enable the move to smart, autonomous and safer factories of the future. In a recent presentation in Stockholm, Filip described how Toyota Material Handling Europe have already connected over 100000 warehouse trucks with integrated telematics. The trucks are put to use in virtually every business from manufacturing and warehousing to transport.
Challenge and Solutions.
The background on Industry 4.0, developer manifesto , team sign, and the core principles that guide the work. The shift from a monolithic codebase towards a microservices approach, which was undertaken so the development teams could be more productive and the platform more user-friendly. Underpinning this change is MongoDB Atlas , MongoDB’s fully-managed, global cloud database service, which Toyota Material Handling runs on Microsoft Azure.
Toyota Team explained what it was they liked about MongoDB: “The most beautiful part was the data model. Everything is a natural JSON document.
But it wasn’t just the data model. Toyota Material Handling had eight evaluation criteria that were used to decide on which database platform they would use to make the switch:
- Performance — latency, scalable reads and writes to meet customer SLAs and accommodate significant growth in the future
- Automatic scalability, operations, and maintenance that enable developers to focus on applications, rather than backend database administration
- Security and compliance to safeguard highly sensitive business and personal data
- Data locality — able to host in Northwest Europe or West Europe in Microsoft Azure, therefore, ensuring close geographic proximity to factories for latency-sensitive operations
- Automatic backups and restore to provide fully-managed data protection and disaster recovery
- Cloud agnostic, giving customers the freedom to run anywhere, on any platform
- Developer friendly database with a flexible data model so that developers can continuously integrate new application functionality and stay ahead of market demands
- Ecosystem for developer productivity, using proven best practices and widely available skills
Result.
For the developers, it is easy, really easy for them to work with quickly. Spending time on building business value, rather than data modeling.
