----
Five Ways the CumuLogic DBaaS Platform Helps Shorten Development Cycles
// Build AWS-compatible Private Clouds with CumuLogic
By now, everyone should know that "cloud services" have brought about a new era of software development productivity. This is especially true with Database-as-a-Service (DBaaS), since databases are considered to be both the most critical aspect of an application's architecture and it's most complex to deploy and manage. Today's applications are being developed to be effectively "stateless" at most layers, but state (and more importantly, data persistence) can't be eliminated. State has been pushed downward, into the data persistence layer of our architectures. This has increased the importance of our data layer immensely, and is driving many teams to adopt DBaaS as the foundation of their data services.
The CumuLogic DBaaS Platform is unique in it's scope, being software specifically designed to allow the enterprise to have their own multi-engine, multi-infrastructure DBaaS platform available in house. It's usefulness comes from the fact that you won't be tied to a specific infrastructure (be it a public cloud, private cloud or bare metal server farm) or database engine. Your application teams will get the speed and efficiency of on-demand database instances, without the operational overhead of having to manage these environments in traditional ways.
Below are five specific ways that the CumuLogic DBaaS Platform can help shorten your development cycles, reducing risk and effort along the way:
1. Parallelization of Development and Testing Efforts
In the same way that giving a team self service access to create and destroy their own VMs, used to deploy in-progress software for development or testing, DBaaS can let those same teams work with databases just as easily. With DBaaS, they get to think about the database system as a unit of deployment, skipping all of the work required to install, configure and coordinate multi-node clusters. Teams are free to deploy as many copies of their database environment as they need, and destroy them just as easily when they are done.
Given the complexity of managing a database engine, and given that "proper deployment" of that engine isn't a core focus of your application developers, they will appreciate the simplicity of being able to "click, name and launch" anything from a single-node MySQL server to a multi-node sharded MongoDB cluster. Simply said, using DBaaS to handle your data layer will let your teams parallelize their efforts much more effeciently.
2. Ease the Stress of Rolling to Production
To an operations team, hearing "Works on my machine!" from a developer can be one of the most frustrating and time consuming responses to a deployment problem. Doubly so when you are attempting to roll into production. Since the database is usually the heart of the system, it can be a common cause for deployment confusion and frustration.
Using a DBaaS can solve a huge part of the deployment challenges facing your teams. Used correctly, DBaaS can ensure that there is a clear blueprint of the data persistence layer's configuration that can be consistently and repeatably deployed. You also get the operational confidence that the new systems will be correctly deployed as managed assets, including monitoring and backup services. Just as importantly, a good DBaaS can allow you to clone entire database service instances, making it trivial to test a new version of the application against a copy of production data (as well as test the rollout process).
3. Start Public, Move Private, Eliminate Delays
Each time a new project is kicked off, there's a natural friction between the desire to get going and the desire to delay capital investment. Infrastructure can be a significant cost, yet running your more successful apps on your own infrastructure is often the right choice for an organization (for cost reasons or otherwise). Pubic clouds offer part of the solution by making it easy to skip the capital investment in new infrastructure. As for the databases, most major public clouds offer DBaaS, in one form or another, as part of their portfolio of services. But what happens when you want to change providers or bring the application on-prem?
A DBaaS platform like CumuLogic can give you the flexibility to get the benefits of DBaaS across multiple public and private cloud environments. By abstracting away the infrastructure specific details from the deployment, your teams will be able to make use of infrastructure wherever it comes from. You get consistency in the service experience for the users, and the flexibility to pick the infrastructure that's right for you at each point in time.
4. Developers Get to Select Database Technologies Based on Need, Not Mandate
When developers have figure out how to code around a particular mandated database technology's downsides, when another choice would be a better fit, you're increasing risks to the project dramatically (and we all know that with risk comes delays… it's inevitable). Often these mandated technologies are selected due to operational considerations: support skills, provisioning scripts might be in place, the DBAs know how to back-up that particular database technology, etc… It's fair to want some level of consistency in your environment, but a multi-engine DBaaS offers you the option of getting that consistency at a higher level of abstraction.
With a multi-engine DBaaS, developers get to pick the database technology that's right for their project, while operations teams get the assurance that the platform itself will handle the overwhelming majority of mundane operational tasks (from provisioning to self-healing). That's the perfect blend of consistency and plurality.
5. Enables Rapid Prototyping and Experimentation
Software engineering is a discipline that thrives on "experimentation", and projects that have the opportunity to test architectural theories, before committing to them long term, are much more likely to succeed. In fact, early prototyping is an amazing way to decrease the risk of a selected architecture. Many project teams find that without this step, they reach the tail end of the project with significant problems that they are unable to get themselves out of.
Multi-engine DBaaS makes it possible to quickly and easily experiment with a number of different database technologies, including testing various scaling and performance characteristics.
Start Moving Faster without the Risks
The CumuLogic DBaaS Platform is designed with both developers and operations in mind, linking their database needs together into a solution that makes data services as agile as web servers. By deploying CumuLogic's DBaaS solution, enterprises can save valuable engineering time, get projects out to market faster and reduce architectural & deployment risk that is dragging down their projects.
If this sounds useful, feel free get in touch to find out how CumuLogic can help your organization. You can also download our software to see it work for yourself.
----
Shared via my feedly reader
Sent from my iPhone
No comments:
Post a Comment