:)
* Meteor is a solution for both frontend and backend development, while Telepat focuses on backend functionality.
- You can use it for just the backend if you want. This statement is true, but just noting that you don't have to use both sides.
* When using Meteor in the backend, you also need to use it in your frontend app. Telepat lets you use any frontend framework.
- You don't have to use it with just Meteor's front end (which is I think what you meant). It has integrations with other front end frameworks and you could use it with just about any front end framework as long as you add some boilerplate to communicate with the client-side store and DDP.
* Meteor is a solution for creating webapps, and running on mobile devices works only via webviews. Telepat enables native clients and native functionality for mobile or embedded.
- Not true actually. They make it the easiest to get mobile apps out with Cordova and webviews, but there are various libraries out there like the ObjectiveC-DDP or meteor-ios library that integrates natively with iOS applications.
* Telepat allows using adapters for 3rd party databases, messaging queues and push transports.
- You can do this with Meteor as well and integrate NPM packages.
I hope that helps shed some light on the comparison.
The platform looks great though. I'll definitely have to take a look at it sometime soon.
I was wondering though, looking at the stack, if some parts couldn't be substituted with "lighter" alternatives? I'm assuming couchbase is being used for the changes feed and since you can't do adhoc querying you need "elastic search" for that, however wouldn't it be possible to replace both with just rehinkdb? Anyway I'm just speculating here, I should probably dig into the code.
Thanks for sharing this and keep up the good work!
Update: seems you'll still need elastic search for rethinkdb full text search [0]
I was searching for a good framework for an online booking system, and though one link and other stumbled upon this. I have't heard about it before, so I thought it would be nice to share it with HN; github repo seems to have a low involvement from anyone outside the creators https://github.com/telepat-io .
EDIT: looks like the comparison is Derby only - racer is a bit more flexible IMO
2) Hosted version (SAAS)
3) Book deal
4) Paid client/server plugins for additional functionality
5) Get "aqui-hired"
6) Enterprise version that's more stable and battle tested
7) etc...
We'll share updates along the road, meanwhile - we're eager to talk to developers that are tackling real-time and refine the product together.
Should be http://kernel.org as linux.com has a spammy feeling..
mainly ability to sync changes made offline on clients back to server and handle conflicts?
