Idea Validation: Restlr - Faster & Better Rest API for Wordpress as a Service
Hi, I am looking for idea validation here whether my idea is good. For now I already started to build the API but I haven't finished it so I can't show here. And before I continue i hope i can get feedback about my idea.
My Idea:
Provides hosted wordpress rest api as a service that promise to deliver very fast API access with very low latency and bring many features that are important for serving and maintaining REST API as headless CMS. Some features are custom type and custom fields, integrated SSL, CDN Integration, caching, and integrated logging and statistics.
My question for feedback:
Is my idea "good enough" to pursue ?
How far along are you with this? I wanted to do something like this to get the best of both worlds. Long cache times for WordPress proper while all the active / dynamic stuff is done via a Go REST API. Currently I don't think I'd be interested in more than just an API replacement for the WP REST API (and possibly Advanced Custom Fields). I'd be willing to help.
Hi akor, I already implemented nearly all "read" part for the existing WP API. And at first MVP this may provide read API only. Do you need post and update part?
So do you plan to use my service for complementer of your existing WP site?
I am planning to provide this as SAAS that may have option for user to use hosted wp tables or just connect to the existing db, will that fill your need?
Isak - Yes, I'd want the ability to add / edit objects (posts, comments, users, etc).
I'm not sure what you're asking with your second question. My idea was to cache 100% of WordPress and just use your API for the dynamic parts (logging in, adding a user, and comments primarily) but I was actually thinking I could help from a code standpoint.
How are you thinking of dealing with custom WP REST endpoints? I'm assuming I'd have to write that myself and tie it together via JWT (or something like it)?
I'm not sure how I feel about handing over the database (whether via a connection string or an import into your service). The reason I'd want something like this is to simplify the existing WP caching strategy but handing over the data would be hard sell. I'm not saying this is a route you should go but I'd be more likely to trust an on premise service.
What would pricing look like?
Have you looked at what the performance improvements look like (especially for "larger" sites 250K+ users, 500K+ posts) for the parts of the API you've done so far?
Have you seen this?
http://v2.wp-api.org/
Hi Idan, I know Wordpress has integrated rest api already, and now doesn't need to install plugin because it is built in.
But I plan to offer "BETTER & FASTER" rest api. Maybe you can see I am offering service similar like "algolia.com" or "search plugin" that provide better search capability and features compare to built in search feature that is offered by wordpress cms itself.