By Richard Seroter, Director of Product Management
One of the most important trends in cloud development is the emergence of the “12-factor app” style where complex systems are deconstructed into simple, scalable apps and services. An extension of this trend is the innovation and evolution we see in the database space.
Key/value stores, caching services, and all manner of NoSQL database capabilities have, in no small part, led to the explosion of innovation we commonly refer to as the “Internet of Things.” Applications and systems are collecting, storing and analyzing more data than ever, and developers increasingly embrace NoSQL options as their data store.
However, there are so many types of NoSQL databases that developers need to keep track of, and it seems like a new one emerges every day. There are dozens of database packages in the market that didn’t even exist five years ago. Each one has important tradeoffs. Is it easy to use? How does it scale? What does it take to get resilience? Developers are faced with the choice of either weaving together multiple technologies in order to get the backend services they need, or settling on a single-purpose platform that meets SOME of their requirements. There's got to be a better way, right? Orchestrate tackled...