Alternatives to Relay Framework logo

Alternatives to Relay Framework

Fuse, Switch, Apollo, jQuery, and React are the most popular alternatives and competitors to Relay Framework.
159
166
+ 1
1

What is Relay Framework and what are its top alternatives?

Never again communicate with your data store using an imperative API. Simply declare your data requirements using GraphQL and let Relay figure out how and when to fetch your data.
Relay Framework is a tool in the Javascript UI Libraries category of a tech stack.
Relay Framework is an open source tool with 16.6K GitHub stars and 1.7K GitHub forks. Here’s a link to Relay Framework's open source repository on GitHub

Top Alternatives to Relay Framework

  • Fuse

    Fuse

    It is a set of user experience development tools that unify design, prototyping and implementation of high quality, native apps for iOS and Android. ...

  • Switch

    Switch

    Ring your mobile phone, computer, and desk phone at the same time. Answer calls and switch seamlessly between devices. Use your personal device with a business phone number so you're always reachable. ...

  • Apollo

    Apollo

    Build a universal GraphQL API on top of your existing REST APIs, so you can ship new application features fast without waiting on backend changes. ...

  • jQuery

    jQuery

    jQuery is a cross-platform JavaScript library designed to simplify the client-side scripting of HTML. ...

  • React

    React

    Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project. ...

  • AngularJS

    AngularJS

    AngularJS lets you write client-side web applications as if you had a smarter browser. It lets you use good old HTML (or HAML, Jade and friends!) as your template language and lets you extend HTML’s syntax to express your application’s components clearly and succinctly. It automatically synchronizes data from your UI (view) with your JavaScript objects (model) through 2-way data binding. ...

  • Vue.js

    Vue.js

    It is a library for building interactive web interfaces. It provides data-reactive components with a simple and flexible API. ...

  • jQuery UI

    jQuery UI

    Whether you're building highly interactive web applications or you just need to add a date picker to a form control, jQuery UI is the perfect choice. ...

Relay Framework alternatives & related posts

Fuse logo

Fuse

45
46
0
Mobile interfaces for your IT systems
45
46
+ 1
0
PROS OF FUSE
    Be the first to leave a pro
    CONS OF FUSE
      Be the first to leave a con

      related Fuse posts

      Switch logo

      Switch

      4
      11
      0
      Cloud-based phone system built for Google Apps users
      4
      11
      + 1
      0
      PROS OF SWITCH
        Be the first to leave a pro
        CONS OF SWITCH
          Be the first to leave a con

          related Switch posts

          Apollo logo

          Apollo

          1.9K
          1.5K
          18
          GraphQL server for Express, Connect, Hapi, Koa and more
          1.9K
          1.5K
          + 1
          18
          PROS OF APOLLO
          • 12
            From the creators of Meteor
          • 3
            Great documentation
          • 2
            Real time if use subscription
          • 1
            Open source
          CONS OF APOLLO
            Be the first to leave a con

            related Apollo posts

            Nick Rockwell
            SVP, Engineering at Fastly · | 44 upvotes · 1.8M views

            When I joined NYT there was already broad dissatisfaction with the LAMP (Linux Apache HTTP Server MySQL PHP) Stack and the front end framework, in particular. So, I wasn't passing judgment on it. I mean, LAMP's fine, you can do good work in LAMP. It's a little dated at this point, but it's not ... I didn't want to rip it out for its own sake, but everyone else was like, "We don't like this, it's really inflexible." And I remember from being outside the company when that was called MIT FIVE when it had launched. And been observing it from the outside, and I was like, you guys took so long to do that and you did it so carefully, and yet you're not happy with your decisions. Why is that? That was more the impetus. If we're going to do this again, how are we going to do it in a way that we're gonna get a better result?

            So we're moving quickly away from LAMP, I would say. So, right now, the new front end is React based and using Apollo. And we've been in a long, protracted, gradual rollout of the core experiences.

            React is now talking to GraphQL as a primary API. There's a Node.js back end, to the front end, which is mainly for server-side rendering, as well.

            Behind there, the main repository for the GraphQL server is a big table repository, that we call Bodega because it's a convenience store. And that reads off of a Kafka pipeline.

            See more
            Adam Neary

            At Airbnb we use GraphQL Unions for a "Backend-Driven UI." We have built a system where a very dynamic page is constructed based on a query that will return an array of some set of possible “sections.” These sections are responsive and define the UI completely.

            The central file that manages this would be a generated file. Since the list of possible sections is quite large (~50 sections today for Search), it also presumes we have a sane mechanism for lazy-loading components with server rendering, which is a topic for another post. Suffice it to say, we do not need to package all possible sections in a massive bundle to account for everything up front.

            Each section component defines its own query fragment, colocated with the section’s component code. This is the general idea of Backend-Driven UI at Airbnb. It’s used in a number of places, including Search, Trip Planner, Host tools, and various landing pages. We use this as our starting point, and then in the demo show how to (1) make and update to an existing section, and (2) add a new section.

            While building your product, you want to be able to explore your schema, discovering field names and testing out potential queries on live development data. We achieve that today with GraphQL Playground, the work of our friends at #Prisma. The tools come standard with Apollo Server.

            #BackendDrivenUI

            See more
            jQuery logo

            jQuery

            169.5K
            51.2K
            6.5K
            The Write Less, Do More, JavaScript Library.
            169.5K
            51.2K
            + 1
            6.5K
            PROS OF JQUERY
            • 1.3K
              Cross-browser
            • 957
              Dom manipulation
            • 805
              Power
            • 660
              Open source
            • 610
              Plugins
            • 457
              Easy
            • 395
              Popular
            • 350
              Feature-rich
            • 281
              Html5
            • 227
              Light weight
            • 91
              Simple
            • 84
              Great community
            • 79
              CSS3 Compliant
            • 69
              Mobile friendly
            • 67
              Fast
            • 43
              Intuitive
            • 42
              Swiss Army knife for webdev
            • 35
              Huge Community
            • 10
              Easy to learn
            • 3
              Clean code
            • 2
              Just awesome
            • 2
              Powerful
            • 2
              Nice
            • 2
              Because of Ajax request :)
            • 1
              Easy Setup
            • 1
              Open Source, Simple, Easy Setup
            • 1
              It Just Works
            • 1
              Improves productivity
            • 1
              Industry acceptance
            • 1
              Allows great manipulation of HTML and CSS
            • 1
              Used everywhere
            • 1
              Widely Used
            • 0
              Javascript
            CONS OF JQUERY
            • 5
              Large size
            • 5
              Encourages DOM as primary data source
            • 4
              Sometimes inconsistent API
            • 2
              Live events is overly complex feature

            related jQuery posts

            Kir Shatrov
            Engineering Lead at Shopify · | 20 upvotes · 585.3K views

            The client-side stack of Shopify Admin has been a long journey. It started with HTML templates, jQuery and Prototype. We moved to Batman.js, our in-house Single-Page-Application framework (SPA), in 2013. Then, we re-evaluated our approach and moved back to statically rendered HTML and vanilla JavaScript. As the front-end ecosystem matured, we felt that it was time to rethink our approach again. Last year, we started working on moving Shopify Admin to React and TypeScript.

            Many things have changed since the days of jQuery and Batman. JavaScript execution is much faster. We can easily render our apps on the server to do less work on the client, and the resources and tooling for developers are substantially better with React than we ever had with Batman.

            #FrameworksFullStack #Languages

            See more
            Ganesa Vijayakumar
            Full Stack Coder | Module Lead · | 19 upvotes · 2.6M views

            I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

            I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

            As per my work experience and knowledge, I have chosen the followings stacks to this mission.

            UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

            Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

            Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

            Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

            Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

            Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

            Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

            Happy Coding! Suggestions are welcome! :)

            Thanks, Ganesa

            See more
            React logo

            React

            116K
            94.5K
            3.8K
            A JavaScript library for building user interfaces
            116K
            94.5K
            + 1
            3.8K
            PROS OF REACT
            • 762
              Components
            • 651
              Virtual dom
            • 563
              Performance
            • 488
              Simplicity
            • 436
              Composable
            • 175
              Data flow
            • 160
              Declarative
            • 124
              Isn't an mvc framework
            • 113
              Reactive updates
            • 111
              Explicit app state
            • 34
              JSX
            • 23
              Learn once, write everywhere
            • 19
              Uni-directional data flow
            • 16
              Easy to Use
            • 14
              Works great with Flux Architecture
            • 10
              Great perfomance
            • 8
              Built by Facebook
            • 7
              Javascript
            • 5
              Speed
            • 5
              TypeScript support
            • 4
              Easy to start
            • 4
              Hooks
            • 4
              Awesome
            • 4
              Feels like the 90s
            • 4
              Scalable
            • 3
              Props
            • 3
              Server side views
            • 3
              Functional
            • 3
              Fancy third party tools
            • 2
              Obama
            • 2
              Has arrow functions
            • 2
              Strong Community
            • 2
              Beautiful and Neat Component Management
            • 2
              Sdfsdfsdf
            • 2
              Great migration pathway for older systems
            • 2
              SSR
            • 2
              Fast evolving
            • 2
              Simple, easy to reason about and makes you productive
            • 2
              Allows creating single page applications
            • 2
              Excellent Documentation
            • 2
              Rich ecosystem
            • 2
              Scales super well
            • 2
              Just the View of MVC
            • 2
              Simple
            • 2
              Closer to standard JavaScript and HTML than others
            • 2
              Super easy
            • 2
              Very gentle learning curve
            • 2
              Server Side Rendering
            • 2
              Cross-platform
            • 2
              Has functional components
            • 1
              Start simple
            • 1
              Every decision architecture wise makes sense
            • 1
              Permissively-licensed
            • 1
              Split your UI into components with one true state
            • 1
              Sharable
            • 1
              Fragments
            CONS OF REACT
            • 35
              Requires discipline to keep architecture organized
            • 23
              No predefined way to structure your app
            • 21
              Need to be familiar with lots of third party packages
            • 8
              JSX
            • 7
              Not enterprise friendly
            • 4
              One-way binding only
            • 2
              State consistency with backend neglected
            • 2
              Bad Documentation

            related React posts

            Vaibhav Taunk
            Team Lead at Technovert · | 31 upvotes · 1.7M views

            I am starting to become a full-stack developer, by choosing and learning .NET Core for API Development, Angular CLI / React for UI Development, MongoDB for database, as it a NoSQL DB and Flutter / React Native for Mobile App Development. Using Postman, Markdown and Visual Studio Code for development.

            See more
            Adebayo Akinlaja
            Engineering Manager at Andela · | 26 upvotes · 849.2K views

            I picked up an idea to develop and it was no brainer I had to go with React for the frontend. I was faced with challenges when it came to what component framework to use. I had worked extensively with Material-UI but I needed something different that would offer me wider range of well customized components (I became pretty slow at styling). I brought in Evergreen after several sampling and reads online but again, after several prototype development against Evergreen—since I was using TypeScript and I had to import custom Type, it felt exhaustive. After I validated Evergreen with the designs of the idea I was developing, I also noticed I might have to do a lot of styling. I later stumbled on Material Kit, the one specifically made for React . It was promising with beautifully crafted components, most of which fits into the designs pages I had on ground.

            A major problem of Material Kit for me is it isn't written in TypeScript and there isn't any plans to support its TypeScript version. I rolled up my sleeve and started converting their components to TypeScript and if you'll ask me, I am still on it.

            In summary, I used the Create React App with TypeScript support and I am spending some time converting Material Kit to TypeScript before I start developing against it. All of these components are going to be hosted on Bit.

            If you feel I am crazy or I have gotten something wrong, I'll be willing to listen to your opinion. Also, if you want to have a share of whatever TypeScript version of Material Kit I end up coming up with, let me know.

            See more
            AngularJS logo

            AngularJS

            46K
            33.6K
            5.2K
            Superheroic JavaScript MVW Framework
            46K
            33.6K
            + 1
            5.2K
            PROS OF ANGULARJS
            • 887
              Quick to develop
            • 587
              Great mvc
            • 571
              Powerful
            • 521
              Restful
            • 503
              Backed by google
            • 348
              Two-way data binding
            • 343
              Javascript
            • 328
              Open source
            • 305
              Dependency injection
            • 197
              Readable
            • 75
              Fast
            • 64
              Directives
            • 63
              Great community
            • 56
              Free
            • 38
              Extend html vocabulary
            • 29
              Components
            • 26
              Easy to test
            • 24
              Easy to learn
            • 23
              Great documentation
            • 23
              Easy to templates
            • 21
              Easy to start
            • 17
              Light weight
            • 17
              Awesome
            • 14
              Javascript mvw framework
            • 14
              Angular 2.0
            • 13
              Great extensions
            • 13
              Efficient
            • 10
              Easy to prototype with
            • 8
              Coffeescript
            • 8
              High performance
            • 7
              Lots of community modules
            • 7
              Two-way binding
            • 7
              Mvc
            • 6
              Clean and keeps code readable
            • 6
              Easy to e2e
            • 5
              One of the best frameworks
            • 5
              Easy for small applications
            • 4
              Works great with jquery
            • 4
              Fast development
            • 2
              Be a developer, not a plumber.
            • 2
              Hierarchical Data Structure
            • 2
              I do not touch DOM
            • 2
              The two-way Data Binding is awesome
            • 2
              Dart
            • 2
              Typescript
            • 2
              Community
            • 2
              Declarative programming
            • 1
              Programming fun again
            • 1
              Acoperișul
            • 1
              The powerful of binding, routing and controlling routes
            • 1
              Fkin awesome
            • 1
              Opinionated in the right areas
            • 1
              Supports api , easy development
            • 1
              Common Place
            • 1
              Great
            • 1
              Very very useful and fast framework for development
            • 1
              Amazing community support
            • 1
              Readable code
            • 1
              Linear learning curve
            • 1
              Scopes
            • 0
              Httpș//Acoperișul 0757604335
            • 0
              Google.com
            • 0
              Bot Ionescu
            • 0
              Angular js
            • 0
              Js
            • 0
              Oautho loc
            • 0
              Shvzjn
            • 0
              Acoperișul 0757604335
            CONS OF ANGULARJS
            • 10
              Complex
            • 3
              Dependency injection
            • 2
              Learning Curve
            • 2
              Event Listener Overload
            • 1
              Hard to learn

            related AngularJS posts

            Simon Reymann
            Senior Fullstack Developer at QUANTUSflow Software GmbH · | 25 upvotes · 2.2M views

            Our whole Node.js backend stack consists of the following tools:

            • Lerna as a tool for multi package and multi repository management
            • npm as package manager
            • NestJS as Node.js framework
            • TypeScript as programming language
            • ExpressJS as web server
            • Swagger UI for visualizing and interacting with the API’s resources
            • Postman as a tool for API development
            • TypeORM as object relational mapping layer
            • JSON Web Token for access token management

            The main reason we have chosen Node.js over PHP is related to the following artifacts:

            • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
            • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
            • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
            • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
            See more
            Simon Reymann
            Senior Fullstack Developer at QUANTUSflow Software GmbH · | 20 upvotes · 889.7K views

            Our whole Vue.js frontend stack (incl. SSR) consists of the following tools:

            • Nuxt.js consisting of Vue CLI, Vue Router, vuex, Webpack and Sass (Bundler for HTML5, CSS 3), Babel (Transpiler for JavaScript),
            • Vue Styleguidist as our style guide and pool of developed Vue.js components
            • Vuetify as Material Component Framework (for fast app development)
            • TypeScript as programming language
            • Apollo / GraphQL (incl. GraphiQL) for data access layer (https://apollo.vuejs.org/)
            • ESLint, TSLint and Prettier for coding style and code analyzes
            • Jest as testing framework
            • Google Fonts and Font Awesome for typography and icon toolkit
            • NativeScript-Vue for mobile development

            The main reason we have chosen Vue.js over React and AngularJS is related to the following artifacts:

            • Empowered HTML. Vue.js has many similar approaches with Angular. This helps to optimize HTML blocks handling with the use of different components.
            • Detailed documentation. Vue.js has very good documentation which can fasten learning curve for developers.
            • Adaptability. It provides a rapid switching period from other frameworks. It has similarities with Angular and React in terms of design and architecture.
            • Awesome integration. Vue.js can be used for both building single-page applications and more difficult web interfaces of apps. Smaller interactive parts can be easily integrated into the existing infrastructure with no negative effect on the entire system.
            • Large scaling. Vue.js can help to develop pretty large reusable templates.
            • Tiny size. Vue.js weights around 20KB keeping its speed and flexibility. It allows reaching much better performance in comparison to other frameworks.
            See more
            Vue.js logo

            Vue.js

            39.3K
            31.4K
            1.4K
            A progressive framework for building user interfaces
            39.3K
            31.4K
            + 1
            1.4K
            PROS OF VUE.JS
            • 278
              Simple and easy to start with
            • 218
              Good documentation
            • 186
              Components
            • 123
              Simple the best
            • 95
              Simplified AngularJS
            • 81
              Reactive
            • 69
              Intuitive APIs
            • 48
              Javascript
            • 45
              Changed my front end coding life
            • 40
              Configuration is smooth
            • 28
              Easy to learn
            • 26
              So much fun to use
            • 21
              Progressive
            • 17
              Virtual dom
            • 13
              Faster than bulldogs on hot tarmac
            • 9
              It's magic
            • 8
              Component is template, javascript and style in one
            • 8
              Best of Both Worlds
            • 7
              Without misleading licenses
            • 7
              Perfomance
            • 7
              Application structure
            • 7
              Elegant design
            • 6
              Intuitive and easy to use
            • 5
              Light Weight
            • 4
              Easy to integrate to HTML by inline-templates
            • 4
              Good command line interface
            • 3
              Small learning curve
            • 3
              Like Angular only quicker to get started with
            • 3
              Customer Render ending eg to HTML
            • 2
              One-way data flow
            • 2
              Single file components
            • 2
              Intuitive
            • 2
              Lots of documentation
            • 2
              Component based
            • 2
              Bridge from Web Development to JS Development
            • 2
              Concise error messages
            • 2
              Logicless templates
            • 2
              Supports several template languages
            • 2
              High performance
            • 1
              GUI
            CONS OF VUE.JS
            • 6
              Less Common Place
            • 3
              YXMLvsHTML Markup
            • 1
              Don't support fragments
            • 1
              Only support programatically multiple root nodes

            related Vue.js posts

            Johnny Bell
            Shared insights
            on
            Vue.jsVue.jsReactReact

            I've used both Vue.js and React and I would stick with React. I know that Vue.js seems easier to write and its much faster to pick up however as you mentioned above React has way more ready made components you can just plugin, and the community for React is very big.

            It might be a bit more of a steep learning curve for your friend to learn React over Vue.js but I think in the long run its the better option.

            See more
            Shared insights
            on
            Vue.jsVue.jsReactReact

            I find using Vue.js to be easier (more concise / less boilerplate) and more intuitive than writing React. However, there are a lot more readily available React components that I can just plug into my projects. I'm debating whether to use Vue.js or React for an upcoming project that I'm going to use to help teach a friend how to build an interactive frontend. Which would you recommend I use?

            See more
            jQuery UI logo

            jQuery UI

            36.4K
            9.9K
            896
            Curated set of user interface interactions, effects, widgets, and themes built on top of the jQuery JavaScript Library
            36.4K
            9.9K
            + 1
            896
            PROS OF JQUERY UI
            • 213
              Ui components
            • 155
              Cross-browser
            • 121
              Easy
            • 100
              It's jquery
            • 81
              Open source
            • 57
              Widgets
            • 48
              Plugins
            • 46
              Popular
            • 39
              Datepicker
            • 23
              Great community
            • 7
              DOM Manipulation
            • 6
              Themes
            • 0
              Some good ui components
            CONS OF JQUERY UI
            • 1
              Does not contain charts or graphs

            related jQuery UI posts

            Ganesa Vijayakumar
            Full Stack Coder | Module Lead · | 19 upvotes · 2.6M views

            I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

            I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

            As per my work experience and knowledge, I have chosen the followings stacks to this mission.

            UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

            Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

            Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

            Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

            Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

            Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

            Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

            Happy Coding! Suggestions are welcome! :)

            Thanks, Ganesa

            See more
            Khauth György
            CTO at SalesAutopilot Kft. · | 12 upvotes · 389.2K views

            I'm the CTO of a marketing automation SaaS. Because of the continuously increasing load we moved to the AWSCloud. We are using more and more features of AWS: Amazon CloudWatch, Amazon SNS, Amazon CloudFront, Amazon Route 53 and so on.

            Our main Database is MySQL but for the hundreds of GB document data we use MongoDB more and more. We started to use Redis for cache and other time sensitive operations.

            On the front-end we use jQuery UI + Smarty but now we refactor our app to use Vue.js with Vuetify. Because our app is relatively complex we need to use vuex as well.

            On the development side we use GitHub as our main repo, Docker for local and server environment and Jenkins and AWS CodePipeline for Continuous Integration.

            See more