4 ms·
Completely agree! We build our .NET projects in a similar way too. My current SaaS company has 8 web projects and 1 core project. Some of the web projects are
by vyrotek 4y ago
Completely agree! We build our .NET projects in a similar way too.
My current SaaS company has 8 web projects and 1 core project. Some of the web projects are SPAs using BFF and others are APIs for customers or our mobile app. They aren't tiny sites. We're up to ~500 controllers. All in a single repo and automatically deployed as a monolith. We have a super small but very productive team which we attribute to this simple design.
- jjtheblunt 4y agoBFF ?
- kroken 4y agoBackend for frontend
- jjtheblunt 4y agothanks
- vyrotek 4y agoBackends for Frontends. An alternative to making "one API to rule them all". Far less time spent trying to model an API in an abstract way that makes sense to many consumers. Instead, an API and the endpoints are designed for a specific client. (e.g. A Mobile App or SPA) For us, this also meant a more RPC based API where and reusability is managed after the network hop. https://samnewman.io/patterns/architectural/bff/ https://samnewman.io/patterns/architectural/bff/
- jjtheblunt 4y agothanks
- gombosg 4y agoBackend for frontend! Specialized microservices that serve some frontend-consumable APIs e.g. when other internal APIs are too cumbersome to use or change too frequently.