Bio: Todd Biske is an enterprise architect with a global publishing company, working out of their office in the St. Louis Metro Area. He writes a blog about BPM and SOA and is the author of SOA Governance from PackT publishing. Previous employers in Biske's career, which spans more than twelve years, include Monsanto, as part of their Enterprise Architecture team; MomentumSI, as a Principal Enterprise Architect, helping organizations with SOA Strategy, Architecture, Infrastructure and similar concerns; A.G. Edwards (now Wachovia Securities) in St. Louis, starting out as part of their Java Mentoring team and finishing as part of their Enterprise Architecture team with responsibilities for SOA and Integration technologies; and Lawrence Livermore National Lab as a computer scientist as part of the National Atmosphere Release Advisory Center.
Areas of expertise: Enterprise architecture, SOA strategy, BMP and BPMN
Contributions from Todd Biske
- Why interfaces are a vital part of API design
- Why data, reporting are valuable for API management
- API tools: Focus on integration, policy management
- Don't overlook portals, SLM when selecting an API tool
- Capabilities integration point technologies should have
- SOA architecture: Why you need API management
- Integration methods: Pros and cons of REST integration
- Why, when to use messaging middleware
- Using an XML appliance for governance, versioning
- Important customizations for SOA governance
- SOA governance: Versioning tools and best practices
- Why you should use REST instead of SOAP for mobile apps
- Centers of Excellence: Managing organizational skills
- How to minimize delays with project governance
- What role does an ESB play in RESTful integration?
- How can I better connect EA with business capabilities?
- Working with SOA in an Agile environment
- Thinking beyond 2012 and even beyond SOA
- The difference between EAI and an ESB
- How to make an enterprise service bus work for your SOA