MOKA Analytics

Decision at MOKA Analytics about Microsoft Azure

Avatar of twschiller
Head of Engineering at MOKA Analytics
Microsoft AzureMicrosoft Azure

We use Microsoft Azure because many of our clients are already Azure for their private cloud. Additionally, Azure supports App Service Environments (ASE), which isolates the application resources and gives us a static IP for securely accessing external resources

Additionally, MSSQL supports columnstore tables which is critical for running fast analytics over large datasets Microsoft Azure

1 upvote19 views

Decision at MOKA Analytics about Django

Avatar of twschiller
Head of Engineering at MOKA Analytics
DjangoDjango

Django takes the hassle out of building an enterprise web application using Python.

  • admin app for administration
  • ORM for deploying against different database vendors
  • social auth package for authentication with enterprise IdP
  • guardian package for authorization

Django

1 upvote10 views

Decision at MOKA Analytics about Confluence

Avatar of twschiller
Head of Engineering at MOKA Analytics
ConfluenceConfluence

We use Confluence for specifications and knowledge sharing. We chose Confluence over other wikis primarily because of its integration with JIRA Confluence

1 upvote4 views

Decision at MOKA Analytics about Heroku

Avatar of twschiller
Head of Engineering at MOKA Analytics
HerokuHeroku

We use Heroku because it eliminates the hassle of managing our user acceptance testing and sales demo environments Heroku

1 upvote3 views

Decision at MOKA Analytics about Celery

Avatar of twschiller
Head of Engineering at MOKA Analytics
CeleryCelery

We maintain a fork of Celery 3 that adds HTTPS support for Redis brokers. The Winning Model currently uses Celery 3 because Celery 4 dropped support for Windows.

We plan on migrating to Celery 4 once Azure ASE supports Linux apps Celery

1 upvote3 views

Decision at MOKA Analytics about IntelliJ IDEA

Avatar of twschiller
Head of Engineering at MOKA Analytics
IntelliJ IDEAIntelliJ IDEA

We use IntelliJ IDEA because it has great support for both Python and JS. In particular, its type-based code analyses, refactoring tools, and debugger are world class IntelliJ IDEA

1 upvote3 views

Decision at MOKA Analytics about Webpack

Avatar of twschiller
Head of Engineering at MOKA Analytics
WebpackWebpack

We use Webpack for its bundling, code splitting, dev server, and hot module replacement capabilities Webpack

1 upvote2 views

Decision at MOKA Analytics about JIRA

Avatar of twschiller
Head of Engineering at MOKA Analytics
JIRAJIRA

We use JIRA because it's a single tool that can be customized to each of our business processes: product development, customer on-boarding, and internal operations JIRA

1 upvote2 views

Decision at MOKA Analytics about Zendesk

Avatar of twschiller
Head of Engineering at MOKA Analytics
ZendeskZendesk

We use Zendesk for customer support and hosting documentation. Additionally, we provide documentation search from within our application using Zendesk's API Zendesk

1 upvote2 views

Decision at MOKA Analytics about Bitbucket

Avatar of twschiller
Head of Engineering at MOKA Analytics
BitbucketBitbucket

We use Bitbucket and Bitbucket Pipelines because of its tight integration with JIRA and code authorization features.

The primary drawback is that its extension ecosystem (e.g., PR review tools) is miles behind Github Bitbucket

1 upvote2 views