New Evolution Digital — Developer Blog — Entry One
Talk about exciting! New Evolution Digital has recruited our first team to begin work on a massive project, we will be promoting all of them over the coming weeks, but first I want to go over a rough scope, and the tech stack that we will be working with!
First, the scope. This is going to be a substantial web application that includes a public facing presentation layer, while having a robust dashboard for multiple administrators for a large number of clients. This will include a CRM, or Customer Relations Management tool, analytics, and will be pulling from a ton of different data sources. Simply put: This is going to be a wild ride taming this monster!
At the time of writing this entry the team includes a product owner, an engineering lead, a UI/UX developer, 2 Back End developers, 2 Full Stack Developers, a Front End developer & a Data Scientist, hopefully a second this week.
It is a large project for sure.
Let’s talk about the tech stack:
Front End
- TypeScript
- Next.js
- TailwindCSS
- Apollo Client
- Formik & Yup
Back End
- TypeScript
- Express
- Apollo Federation (Yes, the one to make micro systems)
- PostgreSQL
We will be utilizing Apollo Federation to create micro services to ensure more stable uptime, and separate different services to ensure the best possible user experience, while building a scalable, and solid application.
GraphQL is a critical need with the micro services architecture, while at the same time ensuring a predictable, and simple interface to a large number of external APIs.
Next.js was chosen to ensure that we have a highly performant front end, while minimizing a ton of tedious tasks throughout the front end and the presentation layer of our application.
Next up is TailwindCSS, honestly one of the coolest pieces to me in this stack beyond creating an application with microservices… It allows us to rapidly build components that conform to both mobile and desktop views without a ton of boilerplate code.
Now let’s be crystal clear. TypeScript was a must here. We are without question going to be throwing data around a ton between the front & back end, and external sources. Having the type protection of TS will ensure that we are throwing the right data, and will ensure cleaner, more concise code.
PostgreSQL was the choice of database because we will be using the relational side of things all day, every day. A NoSQL DB was not an option that made sense, and it was personal preference to utilize Postgres over MySQL.
In closing we have a monster application in process with an amazing group of people working on it, with a ton of hopes and dreams long into the future. As we publish who our team is, and more about our project please keep in mind that most of us are looking for our next long term job while creating what we think is a fun, powerful application. So if you want more information into the team feel free to touch base and I would be happy to get you in touch with our team regarding job opportunities.
Thank you for checking out the first entry in the blog, and until next time, keep hacking at that code!
