用于加载 component registry 中注册的组件
A word cloud component using d3-cloud
Cloud component
Tag/word cloud component for react
A Vue.js Word Cloud component
AdaptJS cloud component library
D3 word cloud component for Angular built upon d3-cloud
MemberJunction: Reusable SVG-based word cloud component for Angular.
Cloud component utils
A word cloud component using d3-cloud
a word cloud component using d3-cloud
A cloud component for shuidi
Vue3+ cloud component loader
Word cloud component library for Svelte with accessibility support.
D3-based word cloud component for React >= 18
A Vue.js Word Cloud component
Cloud component for elroy.
A cloud component for pensees
D3 word cloud component for Angular built upon d3-cloud
React word cloud component based on jQCloud layout algorithm
A customizable React word cloud component
a word cloud component using d3-cloud
The Cloud Firestore component of the Firebase JS SDK.
The Cloud Firestore component of the Firebase JS SDK.
wasmCloud component library giving access to interfaces provided by wasmCloud host runtime
wasmCloud component adapters
See https://www.cloud66.com for more info
Miscellaneous EY server utilities
Pluggable cloud management framework that provides a simple foundation for deploying and destroying enterprise ready cloud environments and components that integrate; cloud provider components and services, cloud orchestration and configuration management tools, and continuous integration and delivery pipelines.
Simulator for IT Services in Federated Clouds
A set of components and classes for quickly building cloud applications and infrastructure.
Coming soon: FreeStorage provides comprehensive file storage capabilities for the FreeRuby web framework. Features include local storage, cloud storage integration (AWS S3, Google Cloud, etc.), file uploads, and storage management for enterprise Ruby applications.
Dataproc Metastore is a fully managed, highly available within a region, autohealing serverless Apache Hive metastore (HMS) on Google Cloud for data analytics products. It supports HMS and serves as a critical component for managing the metadata of relational entities and provides interoperability between data processing applications in the open source data ecosystem. Note that google-cloud-metastore-v1 is a version-specific client library. For most uses, we recommend installing the main client library google-cloud-metastore instead. See the readme for more details.
Dataproc Metastore is a fully managed, highly available within a region, autohealing serverless Apache Hive metastore (HMS) on Google Cloud for data analytics products. It supports HMS and serves as a critical component for managing the metadata of relational entities and provides interoperability between data processing applications in the open source data ecosystem. Note that google-cloud-metastore-v1beta is a version-specific client library. For most uses, we recommend installing the main client library google-cloud-metastore instead. See the readme for more details.
Dataproc Metastore is a fully managed, highly available within a region, autohealing serverless Apache Hive metastore (HMS) on Google Cloud for data analytics products. It supports HMS and serves as a critical component for managing the metadata of relational entities and provides interoperability between data processing applications in the open source data ecosystem.
License your Ruby and Rails applications using evoleap's cloud licensing system ELM. Supports server instance registration, per-user session licensing, component checkout/checkin, and feature flags.
It's your entire technical stack, from cloud architecture to databases, from server-side services to client interfaces, all unified into one cohesive system. Think of it as your development blueprint that ensures consistency, accelerates learning, and eliminates the guesswork from building modern applications. Whether you're starting a new project or scaling an existing one, Rapid Stack gives you the confidence to build faster and smarter, with every component perfectly orchestrated.
== OceanDynamo As one important use case for OceanDynamo is to facilitate the conversion of SQL databases to no-SQL DynamoDB databases, it is important that the syntax and semantics of OceanDynamo are as close as possible to those of ActiveRecord. This includes callbacks, exceptions and method chaining semantics. OceanDynamo follows this pattern closely and is of course based on ActiveModel. The attribute and persistence layer of OceanDynamo is modeled on that of ActiveRecord: there's +save+, +save!+, +create+, +update+, +update!+, +update_attributes+, +find_each+, +destroy_all+, +delete_all+, +read_attribute+, +write_attribute+ and all the other methods you're used to. The design goal is always to implement as much of the ActiveRecord interface as possible, without compromising scalability. This makes the task of switching from SQL to no-SQL much easier. OceanDynamo uses only primary indices to retrieve related table items and collections, which means it will scale without limits. OceanDynamo is fully usable as an ActiveModel and can be used by Rails controllers. Thanks to its structural similarity to ActiveRecord, OceanDynamo works with FactoryBot. See also Ocean, a Rails framework for creating highly scalable SOAs in the cloud, in which ocean-dynamo is used as a central component: http://wiki.oceanframework.net
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.
No description provided.