3 ms·
If you're interested in our experience on starting on microservices from scratch with only 2 people, I gave a talk on it: http://www.infoq.com/presentations/que
by johns 11y ago
If you're interested in our experience on starting on microservices from scratch with only 2 people, I gave a talk on it: http://www.infoq.com/presentations/queues-proxy-microservices-automation http://www.infoq.com/presentations/queues-proxy-microservice...
I agree they're not for every team, but it definitely allowed us to move, grow and scale faster than other dev environments I've worked in.
- orthecreedence 11y agoThanks, sounds really interesting. I'm bookmarking it for later (having a long day at work). Would love to hear how you achieved this with a smaller team.
- levelist_com 11y agoGreat talk. This may be a silly question; however, how do you handle authentication between the main app and the services? Im in the middle of building a sizable application but have begun offloading some of the tasks to microservices, for many of the same reasons you gave. I currently use OAuth2 to authenticate to the main API, but dont really want to add additional overhead by having to authenticate to each service as its needed.
- levelist_com 11y agoperhaps JSON Web tokens between main API and microservice where both have a shared secret?