A Sane Approach to (Micro)services

A Sane Approach to (Micro)services


Service-oriented architecture looks good in theory, as boxes and lines on a whiteboard, but how does it work in practice?

“There are a lot of benefits in flexibility, but then you have a lot of overhead with administration. You have to track more metrics and all sorts of different things can fail in interesting ways,” describes Toby Matejovsky, introducing his talk at this year's Northeast Scala Symposium.

Toby works at Tapad Engineering, a Scala shop that built a framework on top of Finagle, which enables a pretty simple approach to building and deploying microservices. Here are his insights.

Further Resources

About the Author

This post is part of Northeast Scala Symposium 2015

If you liked this post you'll probably be interested in these: