Wednesday, March 23, 2011
San Francisco Ruby on Rails Meetup Tomorrow Night
Thursday, March 3, 2011
Cloud + M2M = Disruption of Things
Articles on the Internet of Things (or Web of Things) are increasingly finding their way into mainstream news. Executives of large companies (such as the CEO of Sprint) and even government officials (such as the Chinese Premier) are speaking about the possibilities and opportunities of having ubiquitous sensors connected to the Internet.
The use of the cloud - in combination with the advent of low-cost sensors and high-availability M2M data transmission - will transform old industries and modify many business models. Almost every major electronic device, vehicle, building component, and piece of equipment has the ability to become "smart" by connecting sensors to it. Most devices already do. The difference though is that moving data to the cloud and being able to process it in infinite combinations provides new capabilities in very low cost, transparent ways.
Thursday, February 10, 2011
The Importance of Workers - Part 1
The best part?
Our developers don't need to know anything about queues (even though they do), or elastic servers, or runners, or schedulers, or even where our SimpleWorker servers live..... they simply know that the Ruby Compute Cloud is alive and waiting for their every request.
So why SimpleWorker?
First, we need to understand a bit about the current landscape of worker systems. Here is a great writeup of Github's path through the various worker systems available today. They ended up rolling their own. Pay attention to how much effort they put into rolling their own, and how much potential effort any would-be user of Resque (or DJ, or any of them) has to go through to implement the system and infrastructure requirements.
https://github.com/blog/542-
Don't get me wrong, the current open source worker systems out there are fantastic, and each has a place in this world. They have enabled hundreds if not thousands of websites to do amazing things. But 95% of the world does not need to go through the trouble of rolling their own system and managing their own infrastructure.
In the next post, we'll talk about workers-as-a-service....
Chad
Tuesday, January 18, 2011
Cloud Computing Meetup tonight
Friday, January 7, 2011
Facebook to Email, a new Appoxy Production
Check it out and let us know what you think in the comments below!
For the techies out there, the core part of this service is sending emails to a large number of people on a schedule and this was made easy by using SimpleWorker to schedule and send out all the emails. The Facebook connection part was made using the mini_fb gem.
Friday, December 17, 2010
Automated Gawker DB Lookup/Reset Script
Thursday, December 16, 2010
IBM DeveloperWorks Features Appoxy's SimpleJPA
This whirlwind tour of SimpleDB [shows] you how to manipulate objects in the non-relational datastore using both the Amazon Web services API and SimpleJPA. Simple JPA implements a subset of the Java Persistence API to make object persistence in SimpleDB easier. One of the conveniences of using SimpleJPA...is that it automatically converts primitive types to the string objects that SimpleDB recognizes. SimpleJPA also handles SimpleDB's no-join rules for you automatically, making it easier to model relationships. SimpleJPA's extensive listener interfaces also make it possible to implement logical data integrity rules, which you've probably come to expect from the relational world.
Amazon promotes SimpleJPA as one of the primary Java interfaces to SimpleDB, using it in sample code and evangelizing its use. Having it also appear in IBM's developerWorks section is just another validation of Appoxy strong. Here's the concluding sentence to the post: