Plastic Laravel Package

Product Decisions This Supports

• Accelerate Search Functionality: Enable rapid development of Elasticsearch-powered search features (e.g., e-commerce product search, content discovery, or advanced filtering) without deep Elasticsearch expertise.
• Unify Data Layer: Bridge Eloquent models with Elasticsearch seamlessly, reducing duplication in data management (e.g., syncing database records to Elasticsearch automatically).
• Roadmap for Scalability: Justify investment in Elasticsearch as a core feature (e.g., for a SaaS platform prioritizing search relevance or a marketplace needing faceted navigation).
• Build vs. Buy: Avoid reinventing Elasticsearch integration wheels; leverage a mature, Laravel-native solution to reduce dev time and technical debt.
• Use Cases:
  • Full-text search for blogs, documentation, or customer support.
  • Autocomplete/suggest-as-you-type features.
  • Analytics dashboards with real-time filtering.
  • Hybrid search (combining SQL and Elasticsearch for complex queries).

When to Consider This Package

• Adopt if:

  • Your Laravel app requires Elasticsearch for search/filtering but lacks dedicated backend resources.
  • You need to sync Eloquent models to Elasticsearch with minimal boilerplate (e.g., Model::search() instead of raw queries).
  • Your team values developer experience (e.g., fluent syntax over raw Elasticsearch DSL).
  • You’re building a feature where search relevance is critical (e.g., recommendations, semantic search).

• Look Elsewhere if:

  • You need advanced Elasticsearch features (e.g., custom aggregations, scripting) beyond what the package supports out-of-the-box.
  • Your data model is highly denormalized or requires complex mappings not aligned with Eloquent.
  • You’re already using a dedicated search service (e.g., Algolia, Meilisearch) with deep Laravel integrations.
  • Your team prefers low-level control over Elasticsearch (e.g., for performance tuning or custom analyzers).

How to Pitch It (Stakeholders)

For Executives: "Plastic lets us ship Elasticsearch-powered search features 10x faster by abstracting the complexity behind Laravel’s Eloquent models. This means we can launch advanced search (e.g., for [Product X]) without hiring Elasticsearch experts or delaying the roadmap. The MIT license and active community (500+ stars) ensure low risk, while the fluent API reduces dev time by ~30% compared to raw Elasticsearch. It’s a strategic lever for [competitive differentiator, e.g., ‘discoverability’ or ‘user engagement’]."

For Engineering: *"Plastic gives us a Laravel-native way to map, query, and sync Eloquent models to Elasticsearch with minimal setup. Key benefits:

• Zero duplication: Automatically syncs model changes to Elasticsearch (e.g., Model::save() updates both DB and ES).
• Fluent queries: Replace verbose Elasticsearch DSL with Laravel-like syntax (e.g., Model::search('query')->filter(['price' => '>100'])).
• Extensible: Hook into events for custom logic (e.g., async indexing).
• Battle-tested: Used in production by [hypothetical companies] for [use cases]. Tradeoff: Limited to Eloquent models and basic mappings—ideal for 80% of use cases, but not for niche Elasticsearch features. Worth evaluating if we’re prioritizing [specific feature]."*