Here we look at installing DreamFactory on DigitalOcean servers. Essentially the main purpose of DreamFactory is to make it easy to provide and manage a REST Gateway that can act as a proxy to a wide range of microservices.
# Aims
So with regard to DreamFactory the aim is to start to gather a bunch of interesting tech. Things like: - DreamFactory IPFS Service - DreamFactory Nginx Config - DreamFactory Wiki - Dreamfactory Wiki Assets - DreamFactory Wiki Files - Ethereum - CEPTR - IPFS - Fedwiki - Livecode - Fetchh
and reveal these as DreamFactory Services - moving towards microservices as we develop. Importantly we want to be able to structure things using Reusable APIs.
Then we can package various integrations as “apps” - that we can engage communities and developers with - apps that can scale, federated hosting, polyglot programming, mobile first etc
# Tutorials and examples
- cURL Examples - dreamfactory.com
- Uploading files - dreamfactory.com ![]()
# Installation
# See also - Microservices - DreamFactory - DreamFactory Security - Reusable APIs - DreamFactory Wiki - Reusable APIs
# Howto
# Open Data Example
There is a nice and fairly full example fo creating Open Data api's with DreamFactory over at dreamfactory.com ![]()
# Other sites
DreamFactory automatically generates a comprehensive REST API for every popular SQL database, NoSQL document store, and file storage system - html
.
We look to enable coders to programme in their language of choice, by providing a robust RESTful Microservice Architecture.
Microservices is a variant of the service-oriented architecture (SOA) architectural style that structures an application as a collection of loosely coupled services.
Using microservices on AWS. Is this to wiki's advantage? Can we exploit it without becoming it? See Computational Habitat