I'm super excited to announce the launch of IDlight, my very first SaaS. I'll
promote it further after the week-end, but I wanted my blog readers to be the
first to know :)
IDlight is an API that allows applications to retrieve public profile
information. Among other things, it uses established and emerging standards
like Webfinger , XRD and hCard to retrieve and parse public profiles.
It unifies all the retrieved data under a unique schema, which makes it easy
for applications to consume in a consistent manner.
Please give it a try and share your feedback directly on idlight.net.
... (more)
I've just released the very first version of loggErL, my Erlang client for
loggr. In case you do not know, loggr is a sweet piece of SaaS that offers a
great deal of compelling log-related features wrapped in beautiful UI.loggErL
offers direct API calls to the loggr API, including support for optional
fields: loggErL comes complete with a Log4Erl appender that allows sending
log events to loggr, again optionally supporting extra fields: Feel free to
fork this project on GitHub: https://github.com/ddossot/loggErL.
... (more)
To be able to do anything useful, an ESB must be configured with all sorts of
parameters, from endpoint connection URIs to message transformation scripts
to content-based routing definitions. Moreover, ESBs like Mule can host
custom components, which will process messages and perform user-specific
actions on them.
Deploying a new version of an ESB configuration raises the question of
whether it will break anything. How can we build confidence that everything
will be just fine? If unit testing did it for standard software development,
what can it do in the realm of the ESB? Since... (more)
If you want to load Resque's web server on a URL path alongside your main
Ruby on Rails 3 application, no need to mess with config.ru or Rack::URLMap,
as shown in different places.
The solution is way simpler and consists in using the RoR3's capacity to
mount Rack applications directly in the routes table, as shown here:
Yep, it's that simple. Enjoy!
... (more)
One of the very first CTO-grade decision I had to take in the making of
Snoget was to pick what would become our main transactional persistence
engine. Since we're using Erlang exclusively for our production servers, the
solution seemed easy: use Mnesia. But I settled for PostgreSQL.
At this point, anyone who's been dealing with O/R mapping (like Ted Neward
who said: "Object/relational mapping is the Vietnam of Computer Science"),
should cry fool: Mnesia would offer me persistence without any impedence
mismatch with the application runtime environment and I preferred a SQL
databa... (more)