How Pitney Bowes uses modern development and testing tools, such as CA Service Virtualization, to drive early API development and enable parallel development, with a simple purpose: go faster.
Why speed with quality are so important and what is parallel development and its implications for Pitney Bowes’ success in bringing innovation to market faster.
For more information, please visit http://cainc.to/Nv2VOe
FULL ENJOY 🔝 8264348440 🔝 Call Girls in Diplomatic Enclave | Delhi
Pitney Bowes Uses Development and Testing Tools to Drive Early API Development and Enable Parallel Development
1. Pitney Bowes Uses Development and Testing Tools
to Drive Early API Development and Enable Parallel
Development
Sam Detweiler
DevOps: API Management and Application Development
Pitney Bowes
Sr. SDLC Architect
DO3X119S
@TwitterHandle
#CAWorld
5. Shipping
& Mailing
Global
Ecommerce
Customer
Engagement
Location
Intelligence
Customer Information
Management
We enable transactions in commerce across five key areas.
6
Using trusted data
to drive insights
and intelligence
Transforming
location and
business data into
enhanced insight
Delivering relevant
and engaging
interactions across
the customer
lifecycle
Driving parcel
handling and mailing
efficiency with end-to-
end innovation
Simplifying a
complex global
marketplace
6. • 15 PB SaaS products on Amazon
• $1.5B web postage for 300M
Ecommerce shipping labels
• $7B total postage funded
• 18B Big Data elements geospatially
analyzed
• 30B hits to our Ecommerce APIs
PB’s Physical and Digital Capabilities Have Been Rapidly Expanding
• 200M geocodes
• 1B address validations
• 3B tracking events
• 1,100 staff trained
Solutions/Business Outcomes
Hardware & Software
Products
Data and Analytics
• 21,000 letters per hour
• 15M parcels
• 800Mstatements
7. Pitney Bowes is a worldwide development organization
Labs in multiple US locations
• Europe
• India
• Australia
Distributed teams work on different parts of the projects and process
• Design done one place
• Development and Test done in others.
Always challenging to coordinate all the process together
8. Creating new APIs to consolidate services
As our customers need more and more global solutions, our APIs need to
expand to support more services
But
Have fewer distinct implementations and more capability.
In the past we would write the code to match the spec, then let our users test it,
and take change requests.
• maybe 1 in 10 would get approved, as we would have to rewrite code.
How can we go faster, reduce rework and improve the overall experience?
9. Development and Test to the rescue
Create an API simulator from the spec, no code yet
Create a toolkit of sample transactions
Deploy to Amazon
EBAY
SaaS app
development
API development team
API test team
10. API Simulation system design criteria
API Designers don’t know DevTest, how to go fast?!
Maximize API knowledge
developers and testers update excel spreadsheet
Make service data driven
generic service reads spreadsheet data to
verify input, construct output.
Service developer doesn’t know product API
Build deployment machine with Apache server apps to upload
new files. Service detects changes in files and reloads
changed configs.
DevTest handles all the communications, logic control,
message construction, error recovery
12. Community feedback early was significant
Having the simulator allowed us to experience the API details
before the solution was locked
We were able to integrate our code with the simulator for the
defined test cases and show working prototypes early
The Development and User community conversation around
the API semantics, verbs, data placement, optional data and
provider centric specifics happened almost immediately in the
cycle and we were able to modify the API definition quickly.
Development of the product code was streamlined, because
all the changes had been worked out in advance.
Testing team was ready for 1st line of actual code
13. Summary
Development and Test platform provided
• A stable environment for service construction and execution
• Very easily understood and extendable environment
• Good performance (sub second) for the test environment
• new users complain all the time about ‘new’ system
• Easy extendibility for debugging
• Easy deployment
Future uses planned for
• a product sales demo environment to eliminate backend dependencies
• enable performance testing of a complex package tracking application
• provide performance based simulations for our financial systems