Glad You're Ready. Let's Get Started!

Let us know how we can contact you.

Thank you!

We'll respond shortly.

Pivotal Perspectives—Pivotal Cloud Foundry 1.4: A Potted Tour

A platform is only useful to developers if it is kept up to date. This week, host Simon Elisha updates us on the new features and capabilities in the PCF 1.4 release. Goodies include logging changes, security updates, AutoScaling and many more.

Pivotal Conversations–So Isn’t Microservices Just SOA With JSON?

In this podcast, Coté speaks with Founder and CEO, Jakub Nešetřil. Jakub's company is all about APIs. The two discuss the shifts to microservices in terms of architecture and development, approaches to governance, API design, and the API economy's evolution.

3 Killer Ways To Up Your Mobile Game in 2015

Mobile application development is hitting a tipping point in 2015, and most companies are planning on stepping up their development investment in the area by at least 36% next year. But spending more on mobile app development isn’t enough—the approach must be smarter. Teams tasked with building or evolving a company’s mobile app strategy should heed tips and best practices like those in Pivotal's infographic, covered in this post along with the top three ways to up your mobile game.

Quick abstracts of YAML or JSON documents

When I work with unfamiliar YAML files specifying deployment manifests, product metadata, serialized records, etc. I want to quickly get a sense of a few things:

What is the set of keys in this data structure? If the structure(nested keys) of the document changed over time, what is the quick summary of changes structure_digest

Given the following long YAML file, I don’t really want to read through all of it to learn what keys and paths are available in it:

{ "receipt": "Oz-Ware Purchase Invoice", "date": "2012-08-06", "customer": { "given": "Dorothy", "family": "Gale" }, "items": [ { "part_no": "A4786", "descrip": "Water Bucket (Filled)", "price": 1.47, "quantity": 4 }, { "part_no": "E1628", "descrip": "High Heeled "Ruby" Slippers", "size": 8, "price": 100.27, }, …(many many more items ) ] }

Lets remove the value content, focus on structure, summarizing array entries as one:

>structure_digest order1.yml order2.yml ...

Read more »

Have you tested your tests lately?

Summary: If you are using the rspec_api_documentation gem to test and document your API, you can use this code to test that you have a spec for each of your routes. Check out the gist here:

If you’re building an app with a public API, accurate and clear documentation is a blessing for both you and your third-party developers.

Read more »

New Pivotal Tracker API Now in Public Beta

The new Pivotal Tracker developer API (V5) is now open to everyone! It’s completely new, all-JSON, much more comprehensive, and full of goodies. Keep reading for highlights and an example to get started.

The recently rewritten Tracker application has been running against this new API since earlier in the year, and some of you may have already started developing against it as part of the private beta.

Read more »

API Versioning

How to version an API has been a thoroughly discussed topic in the last several years regardless of protocol or approach, be that SOAP, REST or Hypermedia. Why contribute another post to the topic? My last post on avoiding breaking changes through better design led to conversations in the office and online about versioning.

Read more »

Playing with Ember.js and Devise

I have been playing with Ember in and out since the beginning of 2012, you may have seen my two (obsolete?) libraries ember-facebook and ember-formbuilder. I wrote them out of real needs I had on projects back then.

I was away from ember since version 0.9.8 and ember-data I don’t even remember if it had a version number yet, and I started playing around with it again this last few weeks.

Read more »

Designing an API in Hell

Minitest, Ruby’s built-in testing library, has some great out-of-the-box features. One of these is test parallelization. Parallel testing is often added after a suite gets slow enough to hurt. That can be achieved using the parallel_tests gem, which takes advantage of today’s multi-core processors, or using custom solutions for dividing chunks of a suite across several machines.

Read more »

Stop leaky APIs

There are many blogs about how to expose an API for a Rails application and many times I look at this and am concerned about how these examples often leak the application design and the schema out through the API. When this leak occurs a change to the application internals can ripple out and break clients of an API, or force applications to namespace URI paths which I feel is unnecessary and ugly.

Read more »