The Repository Pattern in JavaScript

PeopleRepository.js

function PeopleRepository() {
//when using constructor functions like this one to create objects in js,
//always make sure you're doing so with the new keyword
//or the scope will be off
//
//like so:
    if(!(this instanceof PeopleRepository) {
         return new PeopleRepository();
         //we just enforced new
    }
    
    //create a get function on the member
    this.Get=function(callback) {
        $.getJSON("some url",callback);
    };

}

//instance the repo like so (of course using new)
var repo = new PeopleRepository();
//call a get
repo.Get(function(data) {
     //we could do something with the data that gets returned here
});

@micahasmith

It doesn't look like idiomatic implementation of the Repository Pattern.

http://martinfowler.com/eaaCatalog/repository.html

A Repository mediates between the domain and data mapping layers, acting like an in-memory domain object collection. It is not responsible for data retrieving from an external resource. That is DAO's implementation details.

HTH

also, rather than taking a callback, you should probably use Promises.