9/6/2023 0 Comments Windows 7 web slicesWhen moving towards the vertical slices we stop thinking about layers and abstractions. Things related to given features are placed close together. When the code is organized by feature you get the benefits of not having to jump around projects, folders and files. Goal is to stop thinking about horizontal layers and start thinking about vertical slices and organize code by Features. Typically if I need to change a feature in an application, I end up touching different layers of the application and navigating through piles of projects, folders and files. Because of this, I wanted to create a simpler API solution template that focuses on the vertical slices architecture style. Most applications start simple but they tend to change and evolve over time. This project repository is created based on Clean Architecture solution template by Jason Taylor, and it uses technology choices and application business logic from this template.Īfterwards, the projects and architecture is refactored towards the Vertical slice architecture style. Vertical slice architecture by Jimmy Bogard.Ĭheck out my blog post for more details about Vertical Slice Architecture. We can start simple (Transaction Script) and simply refactor to the patterns that emerges from code smells we see in the business logic. ![]() Vertical Slice architecture can be a starting point and can be evolved later when an application become more sophisticated: It's about an idea of grouping code according to the business functionality and putting all the relevant code close together. ![]() The Vertical Slice architecture style is about organizing code by features and vertical slices instead of organizing by technical concerns. This project is an experiment trying to create a API solution template that uses Vertical Slice architecture style.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |