Complicated patterns aren’t always that complicated. Usually it’s the “simple” ones that bite you.
A story of how a codebase became complicated while intending the opposite, the importance of language, and examples of EventSourcing/DDD with the Repository Pattern for Node.js!
SEEKING WORK - New York, NY - available for remote work
I love living on the bleeding edge of web development.
Most recently I've been using a combination of Node.js, ES6/ES2015, React, Redux, RethinkDB, SocketCluster, Express, and GraphQL with Continuous Integration (CI) for builds and deployments.
I am a full-stack engineer, who excels at the front-end, and am fully competent building, deploying, and maintaining from end to end.
In the past I have extensively used Meteor, MongoDB, was CTO for one of the first companies invited to use Meteor's Galaxy DevOps platforms.
Before that I built trading platforms in Node.js using Backbone.js.
Even further back, I used to be really into .NET. We all make mistakes ;) jk!
I'm really interested in building scalable, maintainable systems and have studied DDD related architectures such as CQRS and Event Sourcing, which work wonderfully with microservices!
I am available individually, or with my business partner who specializes in high scale microservices architectures.
The data store on the client side isn't the whole data store, it's the things you've published and subscribed to, which can change easily based on authentication, your userId, or however else you program it.
Meteor has an "insecure" mode that is active by default where everything is published. Don't use that in production.
A story of how a codebase became complicated while intending the opposite, the importance of language, and examples of EventSourcing/DDD with the Repository Pattern for Node.js!