There’s been an explosion of new architectures; there are almost too many to keep up with. But is this because engineers love new things or is there a good business reason for these changes?
As an exec, you may be tempted to pass these new architectures off as engineers reinventing the wheel. Engineers just love changing things around and trying out new technologies. However, the reality is that these new architectures are solving real business problems. Most teams, for example, are spending 40%–90% of their time just dealing with their current architectural problems. Even small to medium improvements with new architectures can provide massive efficiency gains for teams.
The problem is that technical teams don’t know how to talk about these architectures in business terms. Jesse Anderson explores new architectures and the actual business problems they solve. You may find out that your team would be far more productive if you moved to these architectures.
Jesse Anderson is a data engineer, creative engineer, and managing director of the Big Data Institute. Jesse trains employees on big data—including cutting-edge technology like Apache Kafka, Apache Hadoop, and Apache Spark. He’s taught thousands of students at companies ranging from startups to Fortune 100 companies the skills to become data engineers. He’s widely regarded as an expert in the field and recognized for his novel teaching practices. Jesse is published by O’Reilly and Pragmatic Programmers and has been covered in such prestigious media outlets as the Wall Street Journal, CNN, BBC, NPR, Engadget, and Wired. You can learn more about Jesse at Jesse-Anderson.com.
©2018, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • firstname.lastname@example.org