Single-purpose databases were designed to address specific problems and use cases. Given this narrow focus, there are inherent tradeoffs required when trying to accommodate multiple datatypes or workloads in your enterprise environment. The result is data fragmentation that spills over into application development, IT operations, data security, system scalability, and availability.

In this report, author Alice LaPlante explains why developing modern, data-driven applications may be easier and more synergistic when using a converged database. Senior developers, architects, and technical decision-makers will learn cloud-native application development techniques for working with both structured and unstructured data. You'll discover ways to run transactional and analytical workloads on a single, unified data platform.

This report covers:

  • Benefits and challenges of using a converged database to develop data-driven applications
  • How to use one platform to work with both structured and unstructured data that includes JSON, XML, text and files, spatial and graph, Blockchain, IoT, time series, and relational data
  • Modern development practices on a converged database, including API-driven development, containers, microservices, and event streaming
  • Use case examples including online food delivery, real-time fraud detection, and marketing based on real-time analytics and geospatial targeting

Table of Contents

  1. Developing Modern Applications with a Converged Database
    1. Data-Driven Applications: The New Gold Standard of Enterprise Software
    2. Barriers to Building Data-Driven Applications
    3. Single-Purpose Specialty Databases
    4. Converged Databases
    5. Know SQL? You’re Set with a Converged Database
    6. Converged Databases Address Common Data-Driven App Challenges
    7. Some Potential Use Cases for Converged Databases
    8. Moving to Modern Development Paradigms
    9. Development Paradigm #1: Microservices
    10. Development Paradigm #2: Event Streaming
    11. Development Paradigm #3: API-Driven
    12. Developer Paradigm #4: SaaS
    13. Developer Paradigm #5: Low Code
    14. Developer Paradigm #6: Distributed Data
    15. Developer Paradigm #7: Continuous Integration/Continuous Delivery
    16. Converged or Single-Purpose Database: Which is Right for Your Use Case?
    17. Conclusion: Avoiding the Innovator’s Dilemma