API development for mobile + web app

[Chris McCann]

It amazes me how quickly the landscape is evolving with regard to mobile development.  It seems like a new server-side technology for building an API pops up every week.

I'd like to know what frameworks or libraries SD Rubyists find valuable for building back-end APIs for front-end mobile and web applications.  What made you pick the tool you're using?

This isn't intended to incite a religious war on the topic -- I'm surveying the landscape and am sure many of you are doing cutting-edge development as well as maintaining "legacy" APIs.  What's survived the test of time?  What did you try but found seriously lacking at some point?

Thanks!

Chris

[Matt Aimonetti]

Golang if you need high performance, small footprint and robust code.

--
--
SD Ruby mailing list
sdr...@googlegroups.com
http://groups.google.com/group/sdruby
---
You received this message because you are subscribed to the Google Groups "SD Ruby" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sdruby+un...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Marvin Humphrey]

On Mon, Jan 13, 2014 at 11:36 PM, Chris McCann <testf...@gmail.com> wrote:

> It amazes me how quickly the landscape is evolving with regard to mobile
> development. It seems like a new server-side technology for building an API
> pops up every week.

Let's assume that this trend will continue, and that thus tools will continue
to turn over at a rapid rate.

> I'd like to know what frameworks or libraries SD Rubyists find valuable for
> building back-end APIs for front-end mobile and web applications. What made
> you pick the tool you're using?
>
> This isn't intended to incite a religious war on the topic -- I'm surveying
> the landscape and am sure many of you are doing cutting-edge development as
> well as maintaining "legacy" APIs. What's survived the test of time? What
> did you try but found seriously lacking at some point?

Nothing survives the test of time.

To maximize the ability to evolve your codebase, taking advantage of new tools
as they emerge and discarding old ones with minimal backward compatibility
pain, consider a service-oriented architecture where major components are
encapsulated and communicate only via stable, standard networking
technologies (HTTP, TCP, UDP, JSON, etc. depending on what's being
communicated).

Marvin Humphrey

[John Lynch]

If you <3 the JVM, http://dropwizard.codahale.com is a great framework for building API services (from the Yammer folks)

- john

On Mon, Jan 13, 2014 at 11:36 PM, Chris McCann <testf...@gmail.com> wrote:

--

[Chris McCann]

Thanks all, for your input.  Dropwizard does look pretty cool -- will have to investigate it more.

Chris

You received this message because you are subscribed to a topic in the Google Groups "SD Ruby" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sdruby/QtpYq2RuS0s/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sdruby+un...@googlegroups.com.

[Dan Simpson]

+1 for Dropwizard