These are the reasons because we say that this tech is elastic:

  • Code maintainability = greater flexibility to design [...]
  • Components [...]
  • Massively Parallel Development [...]
  • Enables a Design <—> Development Workflow [...]
  • Fast prototyping [...]
  • NativeScript [...]
  • SEO Friendly [...]
  • Community [...]

The concept of elasticity comes from solid mechanics and designates the mechanical property of certain materials to experience reversible deformation when they are under the action of external forces and to recover the original form if these external forces are removed. As an adjective can be used to describe those flexible materials, i.e. that can accommodate different circumstances.

The concept of elasticity or the adjective elastic can also be used to describe technologies. We will say that a technology is elastic when it:

  • adapts to growth, popularity and use of systems built with it (scalability [ISO 9126]).
  • can be extended to meet specific needs of niche markets.
  • is identified as the most versatile for a specific activity (not necessarily the newest).
  • has high visibility, mature communities, support and industry demand it.
  • is modern, sophisticated and advanced but not with high risk associated.
  • agrees very well with cloud computing, containerization of environments, IoT and DevOps.
  • used alongside good processes delivers
    • excellent results and speed to market in short cycle times.
    • add, modify or remove functionalities quickly with low (or null) quality impact

In conclusion, there are many technologies that can be described as elastic although, currently, we decided to work with the following:


Unit testing as the name implies is about testing individual units of code. Unit tests try to answer questions such as "Did I think about the logic correctly?" or "Does the sort function order the list in the right order?" This is a small, short and ugly step by step of doing unit testing in AngularJS.

The sample have two important components, the first is an AngularJS client and the second is a service implemented in NodeJS. The second part will be explained in a future article, but the important thing here is that both parts can work (and be implemented) separately.

In this article we have explored the create, update and delete operations, but the read method wasn’t implemented, so we don't completed the whole CRUD operations. The team decided study and document a sample that represents entities of ATMs. This entity has name, address and state as string attributes plus two booleans that set if the ATM accept deposits and if it has restricted services (called mini).


Code of the view:

<h3>Add/Edit ATMs</h3>
<form class="form" role="form">
<div class="form-group">
<label class="sr-only"...

How to contact us

Our Location

DireccionArismendi 1420 Of. 102 Telefono(+598) 2409 15 66

Follow us

Want to contact us?