Velocity development

lightning fast, quality development for a new digital era

Velocity mode Time to market is not measured by the calendar, it is measured by the clock.

Back

The current business context draws a picture in which traditional businesses, dragged by theunstoppable stream of digital transformation, must face the change to be able to compete.

The areas of IT are becoming more important. Every new idea, every new functionality depends on technology for its launch, and companies increasingly move to the speed set by its IT area.

Companies that were born and built around the technology (Amazon, PayPal, Google, Netflix, TripAdvisor …) are now a major threat to incumbent firms in major industry sectors (banking, retail, media, telecommunications, etc.). The traditional areas of IT companies are suddenly unable to compete with these companies, which by means of their purely digital culture have found a way to work in a revolutionary way, allowing them to achieve:

  • Minimum time to market.
  • Fluidity to quickly adapt its products to customer feedback or changes in the market.
  • Products with a pure multi-channel experience.
  • Minimum time of unavailability of service.
  • Capacity for innovation, testing new ideas and discarding them quickly to find those that work.
  • Low cost of service, including demands to potentially very high loads.

To compete in equal conditions, IT departments from traditional companies need to be able to also work in this way: in velocity mode.

80% of companies develop with architectures that are obsolete today

What is Velocity Development?

Velocity mode, also called fluidity or two-speed development, is the ability to develop, evolve and try new things much faster than others. It requires:

Agile Methodologies

Methodologies such as SCRUM that, in contrast with classic waterfall methodologies, allow the product to evolve during development, reducing time and costs and offering fluidity.

Continuous Delivery

Work models that integrate developers and systems engineers into the same team, automating tests and speeding up deployment processes to the point of making them almost instantaneous.

New Architectures

Uncoupled, light, distributed and highly scalable architectures, based on low coupling (microservices, APIs REST), horizontal elasticity and scaling, fault tolerance via software and low-cost designs.

Bimodal IT

Development teams working at “the speed of Internet” that practically form independent organisations within the company and are capable, with the same resources as the parent company, of working faster and cheaper.

candle_in_the_wind

GET ON THE VELOCITY DEVELOPMENT TRAIN

Time to Market · Flexibility · Scalability · Quality · Customer Centric · TCO

Flagship architecture in the 21st century

We are faced with one of the most important disruptive moments in technology of the last twenty-five years: the third IT evolution in history, or third platform, that has rapidly rendered traditional architectures obsolete.

Paradigma bets decisively on new architectures and technologies that we consider key for developing in velocity mode.

SECOND PLATFORM
THIRD PLATFORM

Low coupling

Monolithic architectures, classical application servers, one heavy deployment

Microservices, self-executable applications, multiple light deployments

Elasticity

Traditional hardware platforms

Share nothing clusters, Cloud privada o pública, contenedores

Fault tolerance

HA mechanism complexes at hardware level

Autonomous modules programmed to survive failure of everything else, stateless models, redundancy via software architecture

Scaling

Complex, vertical, expensive and limited by the need for consistency

Horizontal scaling, hundreds of commodity machines, availability before consistency

Big data processing

SQL, ACID principles, need for structured models

NoSQL, Big Data, BASE principles

Ultra-high performance

Costly active-active solutions

Asynchronous web applications managed by events. Reactor pattern as a solution to the C10K problem

Flexibility

Inter-project dependency at different speeds, SOAP

API Management, REST services lightly uncoupled

UX user interaction technology

Classical MVC, Ajax

Seamless interaction, Single Page Application (SPA), client oriented MVC

  • Spring Boot
  • Amazon Web Services
  • Openshift
  • Mongo DB
  • Cassandra
  • Microsoft Azure
  • Spark
  • Node JS
  • Angular JS
  • VertX
  • Open Stack
  • Docker