Optimizing Erlang applications: emysql
Here at ProcessOne we are in the business of building and managing huge scale robust platforms. Be it APNS or GCM, the timely deliver of
6 min readThe Blog
Where we write about what we build.
Deep dives on real-time messaging, open protocols, distributed systems, and the engineering decisions behind software that runs at scale.
Boxcar Push: iOS and Android push for all mobile developers
ProcessOne is in the business of building and running huge real-time projects for our customers. It is often a cause of frustration when comes
2 min readGoogle Cloud Messaging Update Boosted by XMPP
As you know, ProcessOne is about realtime messaging. Our core component is XMPP ejabberd scalable and ubiquitous server. We recently acquired Boxcar to use a
5 min readGoogle I/O 2013: Services, services, services
Today was the keynote of Google I/O developer conference. The keynote is usually the place where major announcements are made regarding the Google ecosystem.
4 min readBeam Community is a mentoring organisation for Google Summer of Code
If you are a student excited by XMPP, high-performance and Erlang, this should be great news. It means that you will get the opportunity
1 min read
ejabberd Community Server 13.03 is launched in beta
We are announcing two major changes in ejabberd development today: * a new version of ejabberd, called ejabberd Community Server (eCS), as opposed to ejabberd Business
3 min readPress Release – Kwaga sells Boxcar technologies and intellectual property to ProcessOne
ProcessOne is entering in an agreement with Kwaga to acquire Boxcar world-class push notification service as well as all technologies, intellectual property and trademark from Kwaga, the editor of WriteThatName.
2 min readWhy did ProcessOne acquire Boxcar ?
As founder of ProcessOne, I’ve promoted since 10 years a vision made of real-time messages exchanged at an Internet scale. Together with ProcessOne
3 min readejabberd 2.1 vs 3.0 PubSub processor usage
ejabberd’s PubSub implementation covers most of XEP-0060 specification. This involve some complexity server side, sometimes at cost of performances. So PubSub’s optimizations
1 min readejabberd 2.1 vs 3.0 memory consumption
ejabberd is memory bound as session data is kept in RAM for each connected user. This means that available memory is the factor that limits
1 min readBrowse by topic
What would you like to read about?
Written by
Meet the authors.
