---
layout: default
title:  Backends - Code
lang: en
permalink: "/services/backends/code_en/"
lang_ref: services_backends_code
---

# {{ page.title }}
Broadly speaking, in the context of my work, the backend is everything that lies behind the curtain of your web site, mobile game, not mobile game, or anything else that interacts with a user and is connected to the internet.
Building a full scale (and scalable) backend is quite the commitment and you will want a fully integrated, full-time developer on that.
Failing that, there are a few ways we can work together in a modular way that can get you what you need. I can:
- Prototype some options to help you make decisions
- Create a minimally viable system to get your started
- Make some technical design suggestions on paper
- Create a module inside your already modularized system
- Modularize your system
- Build the whole system - This will highly depend on how much time I have.

Here are some technologies I work with:
- Java, NodeJS, Erlang, Ruby, Python, Shell
- PostgreSQL, MySQL, MongoDB, Mnesia
- Amazon Web Services (EC2, RDS, ElastiCache, Lambda, S3, CloudFront, AWS CLI)
- Old fashioned Linux servers
- Ansible (for deployment and some provisioning)
- Puppet
- Jenkins (as a user and as an admin)
- Git, Github, Perforce (as a user and as an admin)

Anything else you fancy, let me know and I will go and bone up on it.

---
layout: default
title:  Backends - Code
lang: en
permalink: "/services/backends/code_en/"
lang_ref: services_backends_code
---

# {{ page.title }}
Broadly speaking, in the context of my work, the backend is everything that lies behind the curtain of your web site, mobile game, not mobile game, or anything else that interacts with a user and is connected to the internet.
Building a full scale (and scalable) backend is quite the commitment and you will want a fully integrated, full-time developer on that.
Failing that, there are a few ways we can work together in a modular way that can get you what you need. I can:
- Prototype some options to help you make decisions
- Create a minimally viable system to get your started
- Make some technical design suggestions on paper
- Create a module inside your already modularized system
- Modularize your system
- Build the whole system - This will highly depend on how much time I have.

Here are some technologies I work with:
- Java, JavaScript, Erlang, Ruby, Python, Shell
- Apache Tomcat, NodeJS, Erlang OTP
- PostgreSQL, MySQL, MongoDB, Mnesia
- Amazon Web Services (EC2, RDS, ElastiCache, Lambda, S3, CloudFront, AWS CLI)
- Old fashioned Linux servers
- Ansible (for deployment and some provisioning)
- Puppet
- Jenkins (as a user and as an admin)
- Git, Github, Perforce (as a user and as an admin)

Anything else you fancy, let me know and I will go and bone up on it.

Make a distinction between javascript and node; Add extra line for server tech
Make a distinction between javascript and node; Add extra line for server tech
