Apache Cassandra
Connection and object support require review
Record types to review with Stacksync
| Record types | Coverage and requirements |
|---|---|
| Confirm support for this record type and the direction you need. |
Database / ERP · Two-way sync platform
Apache Cassandra and Plex ERP integration
Plan how Apache Cassandra and Plex ERP should share data across your business. Work with Stacksync engineers on record mapping, system access, and the requirements for running the integration.
- Scope your workflow with an integration engineer
- Review the systems, records, and updates you need
Built for teams where self-serve, reliability and scale matter
Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Proposed workflow
Customer reporting workflow
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting eventA change involving the proposed customer table in Apache Cassandra or Plex ERP Customers needs a defined result in the other system.
Start with the proposed customer table in Apache Cassandra and Plex ERP Customers. Use the record-matching and field-ownership rules from your mapping worksheet.
Resolve person or company type, legal entity, business role, and any billing account before transactions.
Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
What to verifyTest an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
Review records and field ownershipProposed record relationships
Records to connect
Use these examples to define record matching and field ownership for your technical review.
Download the mapping worksheetCSV · No email required
| Apache Cassandra record | Plex ERP record | Record matching | Field ownership |
|---|---|---|---|
| Proposed customer tableProposed table; choose its name and schema.Reporting dataset | CustomersProposed record; confirm Stacksync object support. | Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient. | Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company. |
| Proposed sales order tableProposed table; choose its name and schema.Reporting dataset | Sales ordersProposed record; confirm Stacksync object support. | Preserve both the order ID and stable line IDs. Allow one order to relate to several shipments or invoices. | Decide which system approves the order and which can cancel or amend it after fulfillment begins. |
| Proposed supplier or vendor tableProposed table; choose its name and schema.Reporting dataset | SuppliersProposed record; confirm Stacksync object support. | Use the supplier ID within its business entity; a supplier name may occur in several subsidiaries. | Assign responsibility for approved supplier details; restrict changes to payment instructions to the business approval process. |
These relationships do not establish connector availability. Review the required connection and record operations with Stacksync.
Record coverage to review
Use documented coverage where available. Catalog record types are starting points for review and do not confirm Stacksync support.
Plex ERP
Connection and object support require review
Record types to review with Stacksync
| Record types | Coverage and requirements |
|---|---|
| Confirm support for this record type and the direction you need. |
Connection essentials
Confirm Stacksync support and account requirements for undocumented connections. Interface information alone does not establish connector availability.
View setup requirements and limits| Connection requirement | Apache Cassandra | Plex ERP |
|---|---|---|
| Integration interface | CQL over the Cassandra native binary protocol | REST APIs plus legacy SOAP web services |
| Authentication | Confirm the credentials, API plan, and permissions required for Apache Cassandra. | Confirm the credentials, API plan, and permissions required for Plex ERP. |
| Change detection | Confirm how Stacksync detects changes for this connector and the objects you need. | Confirm how Stacksync detects changes for this connector and the objects you need. |
| Read access | Confirm with Stacksync | Confirm with Stacksync |
| Write access | Confirm with Stacksync | Confirm with Stacksync |
Enterprise controls
Security and control for your integrations
Explore security controlsCompliance and data transfers
As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.
- SOC 2 Type II
- ISO 27001
- HIPAA BAA
- GDPR
- CCPA
- DPF US-EU-UK-CH
SSO & SCIM
Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.
Alerts
Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.
Secure connection options
Securely connects to your systems with:
Record-level recovery
Inspect sync errors and use retry and revert controls to resolve failed updates.
Read the recovery guideImplementation
Technical reference
Review setup, record relationships, testing, and recovery for your implementation.
Authentication, permissions and API limits
Connection requirements and limits
Apache Cassandra
- Integration interface
- CQL over the Cassandra native binary protocol
- Authentication
- Confirm the credentials, API plan, and permissions required for Apache Cassandra.
- Change detection
- Confirm how Stacksync detects changes for this connector and the objects you need.
- Read access
- Confirm with Stacksync
- Write access
- Confirm with Stacksync
Setup requirements
- Identify the Apache Cassandra account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for Apache Cassandra, including read/write support, authentication, and initial-load limits.
Limitations to check
- Confirm Stacksync support for Apache Cassandra and the record types your workflow needs.
- Review write-back, deletion handling, update timing, and account limits with the integration team.
Plex ERP
- Integration interface
- REST APIs plus legacy SOAP web services
- Authentication
- Confirm the credentials, API plan, and permissions required for Plex ERP.
- Change detection
- Confirm how Stacksync detects changes for this connector and the objects you need.
- Read access
- Confirm with Stacksync
- Write access
- Confirm with Stacksync
Setup requirements
- Identify the Plex ERP account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for Plex ERP, including read/write support, authentication, and initial-load limits.
Limitations to check
- Confirm Stacksync support for Plex ERP and the record types your workflow needs.
- Review write-back, deletion handling, update timing, and account limits with the integration team.
Prepare Apache Cassandra and Plex ERP access
Set up both accounts before testing the mapping. Use test records where available, and identify the account administrator who can approve access and help resolve setup errors.
Apache Cassandra setup checklist
- Identify the Apache Cassandra account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for Apache Cassandra, including read/write support, authentication, and initial-load limits.
Plex ERP setup checklist
- Identify the Plex ERP account, edition, environment, and business objects the integration must access.
- Confirm a Stacksync connector or implementation path for Plex ERP, including read/write support, authentication, and initial-load limits.
Prepare to go live
Record the fields each system can update, the first-load cutoff, both record IDs, the expected update delay, and who handles errors. Complete the tests before production before expanding to more records.
Use the Apache Cassandra and Plex ERP planning worksheet to capture these decisions. Record the access owner in the worksheet and enter credentials only in the connection setup.
Record identity and field ownership
Use these data-model references to describe the records your connection needs. They are planning examples; connector availability and supported operations must be established before implementation.
Download the mapping worksheet · CSV, no email required
Reporting dataset
Proposed customer table in Apache Cassandra (choose its name) / Customers
Plan a customer dataset while preserving its source meaning.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Apache Cassandra
- Your database schema
- Plex ERP
- Object support to establish
- Record identity
- Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient.
- Field ownership
- Separate the customer relationship from contact details, billing authority, and consent. Choose an owner for each field after identifying whether the customer is a person or company.
Fields to include
- Source customer ID
- Person/company classification
- Legal entity or business unit
- Destination identity reference
- Record dependencies
- Resolve person or company type, legal entity, business role, and any billing account before transactions.
- Validation
- Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
- Recovery
- Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.
Reporting dataset
Proposed sales order table in Apache Cassandra (choose its name) / Sales orders
Plan a sales order dataset while preserving its source meaning.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Apache Cassandra
- Your database schema
- Plex ERP
- Object support to establish
- Record identity
- Preserve both the order ID and stable line IDs. Allow one order to relate to several shipments or invoices.
- Field ownership
- Decide which system approves the order and which can cancel or amend it after fulfillment begins.
Fields to include
- Source order ID
- Customer reference
- Line references and quantities
- Order status
- Currency
- Record dependencies
- Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
- Validation
- Test a multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.
- Recovery
- Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.
Reporting dataset
Proposed supplier or vendor table in Apache Cassandra (choose its name) / Suppliers
Plan a supplier or vendor dataset while preserving its source meaning.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Apache Cassandra
- Your database schema
- Plex ERP
- Object support to establish
- Record identity
- Use the supplier ID within its business entity; a supplier name may occur in several subsidiaries.
- Field ownership
- Assign responsibility for approved supplier details; restrict changes to payment instructions to the business approval process.
Fields to include
- Source supplier ID
- Legal name
- Entity reference
- Payment terms
- Active status
- Record dependencies
- Resolve business-unit and payment-term references before purchasing transactions.
- Validation
- Test a supplier shared across subsidiaries and an inactive supplier referenced by an open bill.
- Recovery
- Review rejected supplier changes before retrying dependent bills; do not reactivate a supplier merely to make a write pass.
Reporting dataset
Proposed product or catalog item table in Apache Cassandra (choose its name) / Production jobs
Plan a product or catalog item dataset while preserving its source meaning.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Apache Cassandra
- Your database schema
- Plex ERP
- Object support to establish
- Record identity
- Distinguish the product ID, variant ID, SKU, and price-list entry; they are not interchangeable keys.
- Field ownership
- Assign ownership for catalog content, price, and stock separately.
Fields to include
- Source product ID
- SKU or variant reference
- Description
- Unit of measure
- Price-list reference
- Record dependencies
- Resolve units, variants, categories, and applicable price lists before order lines.
- Validation
- Test two variants of one product, a changed SKU, and a price that applies to only one market or currency.
- Recovery
- Repair the variant or price-list reference before retrying affected order lines; preserve existing transaction prices.
Reporting dataset
Proposed inventory or stock position table in Apache Cassandra (choose its name) / Inventory
Plan a inventory or stock position dataset while preserving its source meaning.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Apache Cassandra
- Your database schema
- Plex ERP
- Object support to establish
- Record identity
- Identify stock by product/variant, location, and any lot or serial dimension; a product ID alone is insufficient.
- Field ownership
- Choose the stock authority and distinguish available, reserved, and physical quantities.
Fields to include
- Product reference
- Location reference
- Quantity type
- Quantity
- As-of time
- Record dependencies
- Resolve product, unit, warehouse/location, and lot/serial references.
- Validation
- Test the same SKU in two locations, a reservation, and an older snapshot arriving late.
- Recovery
- Reconcile the latest stock position before retrying; do not apply an old absolute quantity after new movements.
Reporting dataset
Proposed shipment or fulfillment table in Apache Cassandra (choose its name) / Shipments
Plan a shipment or fulfillment dataset while preserving its source meaning.
Planning example. Stacksync support for the required connection and record operations needs a technical review.
- Apache Cassandra
- Your database schema
- Plex ERP
- Object support to establish
- Record identity
- Retain shipment/fulfillment and line IDs, order reference, and carrier context.
- Field ownership
- The fulfillment owner controls shipped quantities and cancellation eligibility.
Fields to include
- Source shipment ID
- Order/line references
- Carrier
- Tracking reference
- Fulfillment status
- Record dependencies
- Resolve order lines, delivery address, carrier, and any partial-fulfillment references.
- Validation
- Test split shipments, multiple tracking references, partial returns, and a carrier status arriving out of order.
- Recovery
- Verify existing fulfillment before retrying creation; reconcile quantities against order lines.
Compare integration approaches
Choose a method around one example record and the update your business needs. Use Proposed customer table in Apache Cassandra (choose its name) / Customers to review record matching and confirm Stacksync support for the required operations. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.
Stacksync managed sync
- Best fit
- Review compatibility with a Stacksync engineer using an example of the records and updates you need.
- Operating responsibility
- Fits ongoing record synchronization when the required operations are supported. Add workflow steps for approvals or business actions that go beyond copying fields.
- Before you choose
- Check record matching: Determine whether each customer represents an individual, a company, or a business-unit relationship before matching it to a contact or organization. Retain the source customer ID and destination ID; names and email alone are insufficient. Verify field coverage, deletion handling, and how changes are detected.
Native vendor integration
- Best fit
- A vendor-built integration may fit if it supports your Apache Cassandra and Plex ERP record types.
- Operating responsibility
- Can reduce setup for a supported workflow. You may need another method for records or business steps it does not cover.
- Before you choose
- First check whether either vendor offers this integration. If available, verify Proposed customer table in Apache Cassandra (choose its name) / Customers, update direction, account tier, and related-record handling.
Custom API or workflow
- Best fit
- Consider when Apache Cassandra and Plex ERP need a transformation, approval, or action outside a direct record sync.
- Operating responsibility
- Provides control over business steps; the team owns credentials, version changes, error queues, and reconciliation.
- Before you choose
- Verify endpoint permissions, pagination, quotas, duplicate detection, and failure recovery. Separate reading history from actions that send messages, grant access, or post transactions.
File or scheduled snapshot
- Best fit
- Consider for a one-time Apache Cassandra / Plex ERP migration or a reporting need with an explicit freshness window.
- Operating responsibility
- Can simplify a bounded transfer; later changes and deletion history require another extraction or a separately designed incremental process.
- Before you choose
- Record the extraction cutoff, source IDs, encoding, date/number formats, and reconciliation totals.
Workflow scenarios and expected results
Customer reporting workflow
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting event: A change to the selected Proposed customer table in Apache Cassandra (choose its name) or Customers record needs a defined result in the other system.
- Start with Apache Cassandra Proposed customer table in Apache Cassandra (choose its name) and Plex ERP Customers. Use the record-matching and field-ownership rules from your mapping worksheet.
- Resolve person or company type, legal entity, business role, and any billing account before transactions.
- Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
Expected result: Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
If it fails: Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.
Sales order reporting workflow
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting event: A change to the selected Proposed sales order table in Apache Cassandra (choose its name) or Sales orders record needs a defined result in the other system.
- Start with Apache Cassandra Proposed sales order table in Apache Cassandra (choose its name) and Plex ERP Sales orders. Use the record-matching and field-ownership rules from your mapping worksheet.
- Create or locate the customer and products first; resolve taxes, currency, and fulfillment references.
- Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
Expected result: Test a multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.
If it fails: Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.
Supplier or vendor reporting workflow
Planning example. Stacksync support for the required connection and record operations needs a technical review.
Starting event: A change to the selected Proposed supplier or vendor table in Apache Cassandra (choose its name) or Suppliers record needs a defined result in the other system.
- Start with Apache Cassandra Proposed supplier or vendor table in Apache Cassandra (choose its name) and Plex ERP Suppliers. Use the record-matching and field-ownership rules from your mapping worksheet.
- Resolve business-unit and payment-term references before purchasing transactions.
- Test a normal update and one failed or repeated update in the supported direction. Keep both record IDs with the test results.
Expected result: Test a supplier shared across subsidiaries and an inactive supplier referenced by an open bill.
If it fails: Review rejected supplier changes before retrying dependent bills; do not reactivate a supplier merely to make a write pass.
Reconcile Plex ERP business records with Apache Cassandra
This is an evaluation scenario; connector and operation support require confirmation.
Starting event: A finance-owned record in Plex ERP needs operational visibility through a selected destination dataset.
- Select Inventory or Production jobs with the correct legal entity, period, and currency.
- Define a reporting relationship in Apache Cassandra; do not equate customer records, ledger accounts, and posted transactions.
- Decide whether the process only reports a financial state or requests an approved accounting action, and maintain a separate transaction ID for each action.
Expected result: Totals reconcile within the same entity/currency/window; a repeated handoff creates no duplicate financial transaction.
If it fails: Verify posting and settlement state before retrying. Use the approved adjustment path for already-posted transactions.
Initial load and acceptance testing
Keep both record IDs with the expected and actual result. Reconcile the same filters and time window in each system.
Proposed customer table in Apache Cassandra (choose its name) / Customers
Test case
Test an individual buyer, a company buyer, and one company with multiple billing relationships. Do not merge these into a single generic contact.
Expected result
The expected customer relationship is preserved with no duplicate action or unintended write.
Proposed sales order table in Apache Cassandra (choose its name) / Sales orders
Test case
Test a multi-line order, a partial cancellation, and two partial shipments. Compare line totals as well as the header.
Expected result
The expected sales order relationship is preserved with no duplicate action or unintended write.
Proposed supplier or vendor table in Apache Cassandra (choose its name) / Suppliers
Test case
Test a supplier shared across subsidiaries and an inactive supplier referenced by an open bill.
Expected result
The expected supplier or vendor relationship is preserved with no duplicate action or unintended write.
Proposed product or catalog item table in Apache Cassandra (choose its name) / Production jobs
Test case
Test two variants of one product, a changed SKU, and a price that applies to only one market or currency.
Expected result
The expected product or catalog item relationship is preserved with no duplicate action or unintended write.
Direction and permissions
Test case
Bring an example source record and the intended destination operation to the compatibility review. Confirm the supported route before granting write access.
Expected result
Only an approved, supported direction and permitted fields are written.
Freshness and reconciliation
Test case
Measure source and destination times for the selected records under normal load and a burst. Reconcile IDs and values using the same filters and cutoff.
Expected result
The process meets its agreed freshness target and reconciliation has no unexplained differences.
Failed updates, retries and recovery
Start with the failed record and the destination error, then inspect the source value, field requirements, and access.
Rejected or repeated customer change
Investigate
Inspect Apache Cassandra Proposed customer table in Apache Cassandra (choose its name) and Plex ERP Customers, their IDs, and the destination error.
Next action
Hold ambiguous customer matches for review and resolve customer type before retrying dependent records.
Rejected or repeated sales order change
Investigate
Inspect Apache Cassandra Proposed sales order table in Apache Cassandra (choose its name) and Plex ERP Sales orders, their IDs, and the destination error.
Next action
Check for an existing destination order before retrying a timed-out create; reconcile line IDs to avoid duplicate fulfillment.
Rejected or repeated supplier or vendor change
Investigate
Inspect Apache Cassandra Proposed supplier or vendor table in Apache Cassandra (choose its name) and Plex ERP Suppliers, their IDs, and the destination error.
Next action
Review rejected supplier changes before retrying dependent bills; do not reactivate a supplier merely to make a write pass.
A record type or update is unavailable
Investigate
Check the Apache Cassandra and Plex ERP connector guides, account permissions, and any operations marked On Request.
Next action
Ask the integration team to confirm a supported way to handle that record. Verify whether it needs connector configuration or a separate workflow step.
Source and destination disagree after a retry
Investigate
Compare current source values, destination validation, identity mappings, and any side effects already completed.
Next action
Stacksync issue retry reads the current source state. Decide the intended state before retrying or reverting; reconcile downstream effects separately.
Read the Stacksync issues dashboard guide for retry and revert behavior.
Change detection and update delivery
How updates move between Apache Cassandra and Plex ERP
See how each system detects changes and which updates the other system can receive. Each direction has its own permissions and record requirements.
Apache Cassandra Plex ERP Direction requires confirmation
Detect changesConfirm how Stacksync detects changes for this connector and the objects you need.
Apply updatesConfirm that Stacksync can create or update the records you need in Plex ERP.
Plex ERP Apache Cassandra Direction requires confirmation
Detect changesConfirm how Stacksync detects changes for this connector and the objects you need.
Apply updatesConfirm that Stacksync can create or update the records you need in Apache Cassandra.
Update timing and record limits
- Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
- Review write-back, deletion handling, update timing, and account limits with the integration team.
- Review write-back, deletion handling, update timing, and account limits with the integration team.
FAQ
Apache Cassandra and Plex ERP integration FAQ
-
Explore a Apache Cassandra and Plex ERP integration with a Stacksync engineer. Stacksync support for Apache Cassandra and Plex ERP is not established by the connector documentation reviewed for this page. Start with one record and the update your business needs to identify an implementation path.
-
Confirm two-way support with Stacksync for the records and fields you need in both systems. Access to a vendor API does not confirm that its Stacksync connector supports write-back.
-
Prepare both accounts, the selected object schemas, stable source and destination IDs, and the expected outcome. Identify the Apache Cassandra account, edition, environment, and business objects the integration must access. Identify the Plex ERP account, edition, environment, and business objects the integration must access. Use the pair worksheet to record ownership and acceptance criteria.
-
Measure initial-load and ongoing-change latency separately. Source detection, selected objects, account limits, and destination validation determine the observed delay.
-
No. Stacksync documents that pre-existing duplicates are not merged automatically when two-way sync begins. Review the initial dataset and matching plan before enabling it; an empty destination can simplify the first load.
-
Start with one business entity and a stable record ID. Map a small set of editable fields with compatible types, test required values and relationships, then expand after the pilot passes.
-
Check the destination error, field constraints, permissions, and current source value. The Stacksync issues dashboard supports retry and revert; retry reads current source values, so verify the intended record state before acting.
-
Use the current Stacksync pricing page and confirm the supported implementation with the team. Scope the required objects, record volume, update frequency, initial load, and support needs when comparing a managed connector with native or custom development.
-
Start by reviewing Proposed customer table in Apache Cassandra (choose its name) in Apache Cassandra and Customers in Plex ERP. Check how these records relate in your workflow, then confirm the actual fields and supported operations. Test record matching and one failed or repeated update before adding more records.
-
Choose a method around one example record and the update your business needs. Use Proposed customer table in Apache Cassandra (choose its name) / Customers to review record matching and confirm Stacksync support for the required operations. Compare ongoing sync, a custom workflow, and a scheduled export against that requirement.
Integration directory
Related integrations
Review documented support, sync direction, and setup requirements on each pair page. Search all 429 integrations listed for Apache Cassandra and Plex ERP.
Popular · 6 of 429
-
Apache Cassandra and NetSuite -
Apache Cassandra and Dynamics 365 Business Central -
Plex ERP and Couchbase -
Plex ERP and DuckDB -
Plex ERP and Elasticsearch -
Plex ERP and Google Cloud Spanner
No integrations match .
Next step
Plan your integration with an engineer
Walk through your Apache Cassandra and Plex ERP records, field mappings, and requirements with an integration engineer.
