Over the last several years, we have responded to these customer needs by introducing new services such as Amazon Neptune for graph databases, Amazon Aurora for fully managed, commercial-grade relational databases, as well as an ever-improving feature set such as Amazon Aurora Serverless. We also walk through a detailed example of these databases powering different experiences in an application, and provide the tools you need to spin up the app for yourself in minutes.ĪWS customers tell us they want to build scalable, high-performing, and functional applications that have specific performance and business needs. In this blog post, we discuss AWS purpose-built databases and how to use them to create rich experiences for your customers. In a sense, developers are doing what they do best – dividing complex applications into smaller pieces – which allows them to choose the right tool for the right job. Indeed, developers today build highly distributed applications using a multitude of purpose-built databases. In contrast, today’s web applications from customers such as Expedia, Airbnb, and Capital One do not use a single database – they use several different types of databases. As Werner Vogels, CTO and VP of, said: “Seldom can one database fit the needs of multiple distinct use cases.” In the past, web applications were constructed by using the LAMP stack (Linux, Apache, MySQL, and PHP), where a single database was used for many different experiences. The days of one-size-fits-all, monolithic databases are behind us. September 8, 2021: Amazon Elasticsearch Service has been renamed to Amazon OpenSearch Service.
0 kommentar(er)
