• Corpus ID: 32781215

Treating Microservices as a Unifed, Distributed Database

@inproceedings{Saeta2017TreatingMA,
  title={Treating Microservices as a Unifed, Distributed Database},
  author={Brennan Saeta},
  booktitle={CIDR},
  year={2017}
}
Microservices have become a popular application architecture,[2] allowing multiple teams within an organization to efficiently build a complex system. Additionally, the rise of native mobile apps and interactive javascript web apps bring sophisticated business logic into the client. A principled approach–inspired by database architectures–enables frontend developers to treat the backend as if it were a database, resulting in efficient bandwidth use, and avoids “chatty” APIs, without sacrificing… 

References

SHOWING 1-5 OF 5 REFERENCES

Microservices: a definition of this new architectural term

  • http://martinfowler.com/articles/microservices.html
  • 2014

Pattern: Backends for frontends. http://samnewman.io/patterns/architectural/bff

  • Pattern: Backends for frontends. http://samnewman.io/patterns/architectural/bff
  • 2015

Pattern: Backends for frontends

  • http://samnewman.io/patterns/architectural/bff/
  • 2015

Graphql specification

  • http://facebook.github.io/graphql/
  • 2016

Graphql specification. http://facebook.github.io/graphql

  • Graphql specification. http://facebook.github.io/graphql
  • 2016