Domain Driven Design: The Good Parts
The greenfield project started out so promising. Instead of devolving into big ball of mud, the team decided to apply domain-driven design principles. Ubiquitous language, proper boundaries, encapsulation, it all made sense.
But along the way, something went completely and utterly wrong. It started with arguments on the proper way of implementing aggregates and entities. Arguments began over project and folder structure. Someone read a blog post that repositories are evil, and ORMs the devil incarnate. Another read that relational databases are last century, we need to store everything as a stream of events. Then came the actor model and frameworks that sounded like someone clearing their throat. Instead of a nice, clean architecture, the team chased the next new approach without ever actually shipping anything.
Beyond the endless technical arguments it causes, domain-driven design can actually produce great software. We have to look past the hype into the true value of DDD, what it can bring to our organizations and how it can enable us to build quality systems. With the advent of microservices, DDD is more important than ever - but only if we can get to the good parts.
Oracle's Java 11 دیگر رایگان نیست
Mono 4 منتشر شد
سری مقدماتی ASP.NET Core
Introduction to ASP.NET Core part 15: starting with tag helpers
Introduction to ASP.NET Core part 14: the view start and the layout files
Introduction to ASP.NET Core part 13: the view imports file
Introduction to ASP.NET Core part 12: data annotation of view models
Introduction to ASP.NET Core part 11: inserting a new Book in a form
Introduction to ASP.NET Core part 10: the details page and more on view models
Introduction to ASP.NET Core part 9: MVC continued with routing
Introduction to ASP.NET Core part 8: MVC continued with controller actions and our first view
Introduction to ASP.NET Core part 7: starting with MVC
Introduction to ASP.NET Core part 6: environments and settings
Introduction to ASP.NET Core part 5: static files
Introduction to ASP.NET Core part 4: middleware and the component pipeline
Introduction to ASP.NET Core part 3: the configuration file
Introduction to ASP.NET Core part 2: dependencies and dependency injection
Introduction to ASP.NET Core part 1: anatomy of an empty web project
چند زبانگی در برنامههای Angular
Simple i18n support for your Angular apps
Easy ways to create a translation mechanism for your Angular and Ionic applications that does not rely on third-party libraries.
In this article, I am going to show a quick and easy way to provide a translation (aka i18n) support for your Angular and Ionic applications.
فیلتر کردن IP ها در ASP.NET Web API
class App extends Component { state = {}; componentDidMount() { const currentUser = userService.getCurrentUser(); this.setState({ currentUser }); console.log("CUUSer", currentUser); } render() { const { currentUser } = this.state; return ( <React.Fragment> <ToastContainer /> <Switch> <Route path="/dashboard" render={props => { console.log("CCCCCCCCC", currentUser); if (!currentUser) { return <Redirect to="/account/login" />; } return <DashboardPage {...props} />; }} /> <Route path="/account/registercode" component={RegisterCode} /> <Route path="/account/login" component={LoginForm} /> <Route path="/notfound" component={NotFound} /> <Route path="/logout" component={Logout} /> <Route path="/" exact component={HomePage} /> <Redirect to="/notfound" /> </Switch> </React.Fragment> ); } } export default App;
کتابخانه jquery-sortable-lists
Sortabl elists also contains an export functions toArray, toHierarchy, toString.