Appendix. Further reading

 

Microservices

Cramon, Jeppe. “Microservices: It’s not (only) the size that matters, it’s (also) how you use them,” parts 1–5. 2014–2015. http://mng.bz/zQ2a.

Fowler, Martin. “MicroservicePrerequisites.” August 28, 2014. http://martinfowler.com/bliki/MicroservicePrerequisites.html.

———.“MonolithFirst.” June 3, 2015. http://martinfowler.com/bliki/MonolithFirst.html.

Lewis, James and Martin Fowler. “Microservices.” March 25,2014. http://martinfowler.com/articles/microservices.html.

Tilkov, Stefan. “Don’t start with a monolith.” June 9, 2015. http://martinfowler.com/articles/dont-start-monolith.html.

Newman, Sam. Building Microservices: Designing Fine-Grained Systems. O’Reilly Media, 2015.

———.“Pattern: Backends for Frontends.” November 18, 2015. http://samnewman.io/patterns/architectural/bff.

Software design and architecture in general

Beck, Kent. Test Driven Development: By Example. Addison-Wesley Professional: 2002.

Conway, Melvin E. “How Do Committees Invent?” Datamation (April 1968). www.melconway.com/research/committees.html.

“Defense in Depth.” Open Web Application Security Project (OWASP). www.owasp.org/index.php/Defense_in_depth.

Evans, Eric. Domain-Driven Design: Tackling Complexity in the Heart of Software. Addison-Wesley Professional: 2003.

Fowler, Martin. “TestPyramid.” May 1, 2012. http://martinfowler.com/bliki/TestPyramid.html.

———.“IntegrationContractTest.” January 12, 2011. http://martinfowler.com/bliki/IntegrationContractTest.html.

Technologies used