Introducing Tasker

I find having an example useful when learning about technology, and this book is no exception. The code package for this book contains an example enterprise application representing each of the following four tiers: the database, business logic, web service API, and presentation layer.

Tasker is intentionally designed to be a very simple app, far simpler than many enterprise apps. This isn't a bad thing; it enables us to worry about the critical issues related to enterprise app development without having a complex application that defies understanding. Instead, Tasker is largely what it sounds like: a simple task management app.

Of course, a to-do list doesn't sound very enterprise-y. As such, Tasker isn't about managing a single task list, but about managing and delegating many tasks to many users. The app is built with the idea that the entire organization will be using this app to track their work. As such, tasks are owned by their creator, and they can also be assigned to other individuals. The owner or the assignee can update the task status or add comments as well. Finally, individuals can only see the tasks they are assigned or the tasks that they own, which adds a level of security.