This a multi-purpose personal playground, focused on a personal budget application, to experiment and have as a reference for new projects.
I intend to use this as a repo for whatever I discover somehow to be a "best practice", or decide by my own it's one.
I had the honor to do the Spanish translation of the e-book .NET Microservices: Architecture for containerized .NET applications from Cesar De La Torre, so I had the chance to explore in great detail multiple facets of the microservices architecture.
Having worked some significant time on the e-book's reference application: eShopOnContainers on GitHub, continuing with the e-book's content revision and some experience as the co-founder of a Venezuelan ISV (in my former life), I feel confident enough to say that microservices are not for everyone.
You should apply a Microservices Architecture when it's completely justified from a business point of view, for sure, as it solves some real life problems of large code bases and deployments. But it also adds significant complexity for both development and administration. So, be thoughtful and don't get caught in fashion moves.
So I decided to create this personal budget sample application, beginning with a monolith approach, but architected in a way that could be "easily" and progressively migrated to microservices when it becomes so successful it gets to compete with Intuit 😉.
You can get the "Microservices e-book" from several sources, being the English PDF the most up-to-date release, as of 14-OCT-2018:
-
PDF
- English (The original): .NET Microservices: Architecture for containerized .NET applications
- Spanish (Hand-translated): Microservicios .NET: Arquitectura para aplicaciones .NET contenerizadas
-
ON-LINE
- English/Automatic translation: .NET Microservices: Architecture for containerized .NET applications
If you find some problem or have any suggestion, please create an issue on this repo.
If this helps you somehow, I'd appreciate you to spread the word and let me know on Twitter.