Sviluppare in cloud con M.E.A.N.: il caso Crowdcore

Sviluppare in cloud con

M.E.A.N.: il caso

Crowdcore.

MILAN november 28th/29th 2014


BUSINESS CASE

Juri di Natale

LINKME

agile development

ENTER CLOUD SUITE

cloud computing

CROWDCORE (powered by FOLKFUNDING)

crowd economy


THE “PROTAGONISTS”





SOME DEFINITIONS,

BEFORE WE START

-reward crowdfunding

-equity crowdfunding

-donation crowdfunding

-pre-order crowdfunding

-social lending


CROWDFUNDING

Internet based

Access inside the enterprise

User Experience


INTRANET

A framework to develop crowd

economy tools and platforms


CROWDCORE =INTRANET CROWDFUNDING


CROWCORE: example

A platform to grow, inside the

enterprise, innovative projects based

on crowdfunding and gamification


CROWDCORE for NTT DATA


CROWDECONOMY

Customers are creating new business models


PLATFORM

CHARACTERISTICSMultiplatform

Multiproject

Set of tools specific to different types of

crowdfunding

Custom application

How cloud computing and M.E.A.N.

supported the development of a

framework for a crowd economy

platform


BUSINESS CASE

1. Scalability

2. Agile new feature implementation

3. Component re-use


THE CHALLANGE


CROWDCORE

APPLICATION


BACK END

Giovanni Lela

• I/O intensive REST APIs

• horizontal scalability

• leverage existing javascript know-

how

• huge community


WHY

• (mostly) non relational data

• horizontal scalability (again)

• mongoose ODM


WHY

• Unopinionated

• VERY modular

• Mature


WHY


6 MONTHS LATER…

• You need something to fight the

callback hell (Bluebird)

• Needs static typing

• Too many community packages

are too many


nodeJS IS OK BUT…

• Mongoose Schemas are great

o Validation

o Referencing other documents

o Schema inheritance

o Plugins


Mongo DB and mongoose

ARE OK BUT…

• Easy to extend

• Maybe too much unopinionated


EXPRESS IS OK BUT…

• Typescript

• ES6 generators - koa


WHAT HAPPENS NEXT


FRONT END

Matteo Scandolo

MILAN november 28th/29th 2014 – Speaker's name

Spread, Dependency Injection and

Directive

WHY ANGULAR

Every components is assembled with a

Directive and a Service

STANDALONE MODULES


Every Module has some configuration parameters

and the possiblity to pick up a custom template

Directive

Template

MODULE CONFIGURATION

GruntJs let us build

portable environment and

to tailor them to the

developer needings.


DEV ENVIRONMENT

Every Module has his own repository,

that is importend in the main project

as a Git SubTree


VERSION CONTROL


6 MONTHS LATER…


Modules Web Components


Grunt Vagrant

Subtree Private Bower Registry


HOW WE DESIGNED

THE INFRASTRUCTURE

Giorgio Bonfiglio

• Cost effectiveness

• Ability to scale-up


WHAT THE CUSTOMER

ASKED FOR…

• (Very) short deployment time

• Standardized processes

• Ability to clone the infrastructure


…AND WHAT ABOUT

DEVELOPERS?

• Designed for the cloud

• Easier distribution of components


NEW FRAMEWORKS,

BETTER POSSIBILITIES


HERE IT IS

“deploy and scale in seconds

easily manageable

building blocks”


IT’S ALL ABOUT AGILITY

• Easy disaster recovery, replica

and versioning: NO limits!


DREAMS… AS A SERVICE

• Infrastructure awareness for the

application

• Platform APIs enable it to control

the underlying layer


WHAT’S NEXT?


KEY FINDINGS

• Technology supports the crowd

economy

• MEAN provide high scalability and

flexibility

• Cloud native applications do

“manage” cloud infrastructures

(deployment, autoscaling, …)


3 LESSONS

A social lending platform is also

coming!


GOOD NEWS


WORK WITH US!

[email protected]

REQUEST A DEMO!

[email protected]

Presentations & Public Speaking

Sviluppare in cloud con M.E.A.N.: il caso Crowdcore