You’d be surprised how much trust people place in legal departments, balance sheet strength and talent capacity. All things for which I had to turn down superior technical proposals in the past. The old saying „Nobody gets fired for buying IBM“ still runs strong.
Free e-signatures are a great idea, have you considered getting a foundation to back the project and maybe taking out some indemnity insurance, perhaps raising a dispute fund?
Because when you send a document for a $75MM contract to be signed you want to send it via a well known and trusted document signing platform like Docusign where you know everything is legit and legally defensible.
Basically before CDK, this type of offering made sense but the truth is that AWS correctly identified this need to quickly scaffold infrastructures AND edit it without requiring YAML, Cloudformation or other declarative syntax like Terraform.
CDK is literally writing Python code. You can organize your files and write out logic in all the ways you could possibly. CDK offers tremendous value in this regard but the downside being you won't be able to generate the same layout on Azure or Google but that's a given.
On one end of the spectrum you could have a hybrid of Azure/Google cloud products but with AWS as your main base, vice versa. However, usually in my personal experience, you rarely end up deploying a complete stack on both clouds. It's like take that product from Google or Azure and make it work with AWS, in such scenario you could simply do most of the stuff in CDK and then wire up separate products (but to each their own).
The only use case where I think might require Terraform to a large degree is if you make heavy use of VPC'd, full stack across multiple clouds (ex. agency or consulting firm) but for majority of cases I don't really leave AWS and neither is there an expectation to from clients and employers (they rather just stick to AWS for everything if possible)
tldr: Terraform and tools like what OP is offering, were used to scaffold infra on AWS but CDK came along and really made it unecessary—just learn Python or a backend developer to scaffold infra on AWS in Python.
Stacktape is a whole "cloud development framework". It's not only about infrastructure management, but also about all the other DevOps-related tasks you come across when developing/running an application on AWS.
- In my opinion, it's even easier to use than a CDK L3 construct.
- It supports local/remote development, source-code packaging, deployment artifact management, secret management, domain management and much more.
- Besides AWS resources, it supports other 3rd party services (like MongoDB Atlas clusters and Upstash Kafka/Redis).
- It has a local development studio - GUI (currently in private beta).
I believe AWS CDK is actually written in JS, natively, and ported to other languages, inc. Python, using sort of a transpiler they created for that purpose.
I would love to support Scylla, I ** love that database, those guys are magicians. And I assume in supporting that we'd also offer de-facto support for Cassandra.
I don't think either Scylla or dynamo are on the roadmap now, but if you want them feel free to create an issue asking for them: https://github.com/mindsdb/mindsdb
It should be noted that there's two level of support:
1. As a source of data (easy to implement)
2. Being able to publish models into the database (a bit harder)
If you work with those and are interested in doing ML from the database please get in touch, ideally via github, but you can also use the contact form (https://mindsdb.com/contact-us/) or email one of us directly. The best case scenario for us is that when we do one of these integrations we have an actual user in mind, and we're open to "first users" for any database where we can find a reasonable way of integrating.
Thanks for asking! We develop based on community requests, if you want we can setup a call, and we can see if we can help you with your data on DynamoDB/SCylia, its becoming pretty fast now to support new databases. send us an email to adam jorge at mindsdb.com
If you do have a Scylla use case, please also feel free to let us Scylla monsters know: peter at scylladb dot com. Very encouraged to see such a great convergence occurring between NoSQL + ML. The camps between data scientists and data engineers have been pitched too far apart to date. My best wishes to all those who helped bring this to fruition.
