Hello to everyone in the community, and an extra big thank-you to everyone that has been mailing us lately to ask questions or show their support!
We’ve had a busy September here, and we want to share what we’ve been up to, and what we’re planning for the next month.
So here’s what’s new with Telepat:
- We’ve released version 0.2 (currently at patch 0.2.4). This is awesome, because:
- The built-in Couchbase instance (for storing system data) has been replaced with Redis;
- Database adapters are now ready for action! We provide a default adapter for Elasticsearch, but you can now write your own;
- We’ve pumped up password encryption security using bcrypt;
- Adapters are available for the messaging layer as well, so you can replace Kafka if needed;
- Users can now register and login using an email/password combination, on top of the already supported Facebook login;
- A lot of issues have been fixed, and performance was significantly improved.
- We released the first iterations of our CLI, that basically acts like a bash client and can help you handle management and debugging tasks easily;
- We’ve revamped the Getting started guide to reflect the latest changes;
- Check out Telepat’s CI on Travis – we’re at 78% test coverage for the API right now;
- Also, check out our code climate rating.
Now that we have a pretty stable version functionality-wise, we’re putting Telepat to the test. In the next couple of weeks, we plan to:
- Bump code coverage to 90%+;
- Continue improving and documenting the Telepat CLI;
- Run a large-scale cloud deployment and benchmark for Telepat. We’re hunting for issues and tweaks that are only revealed when under load, so hopefully, by the end of this process, we’ll make sure that we have a core that scales out beautifully and efficiently. But more on that later;
- Of course, work on documentation, tutorials and examples.
But one of the most important things that we can be doing right now is listening to the community. If you have any questions, issues, ideas or you’d like to join the effort to create the missing open-source data synchronization engine, you can get in touch in multiple ways:
- Ask your questions on Stack Overflow;
- Open an issue directly on any Telepat component GitHub page;
- Email us directly: firstname.lastname@example.org;
- Let us know this matters by starring Telepat on GitHub:
Thanks for tuning in, and we’ll be back soon with more news. Meanwhile, how about giving Telepat a test run? We would really love your feedback!