DEV Community

Cover image for Choosing Technologies, APIs and Languages
Gwen (Chen) Shapira
Gwen (Chen) Shapira

Posted on

Choosing Technologies, APIs and Languages

There is a vast difference between choosing a technology or a language for one person or a small team, choosing for a large engineering organization, and choosing for a platform with potentially tens of thousands of users.

Choosing a technology for yourself or a small team is usually about personal taste, whether or not you are interested in learning something new, available tools, integration into an existing project, and perhaps performance/scale considerations.

When you choose a technology for a larger engineering organization, perhaps an entire company, it's a different story. In that case, you need to think about hiring, training, use-cases, testing, all the other parts of the CI/CD pipelines, and try to imagine three years into the future - is this technology growing or dying?

Choosing a technology for a platform should be about the people who will use it. What will they find natural? What will make their life easier? What will create the best experience? It is very tempting to build something for yourself and hope that others will like it, but I think we can do better. We can connect to our potential users and try to emphasize, listen to them and see things from their perspective so you can build a fantastic experience for them.

This isn't easy, especially if you hope that front-end engineers will use your product and you only know two.

Can you help me out by sharing your thoughts in a quick survey? https://0sri4j4i8ze.typeform.com/to/IWI56Zkk I ask about your favorite languages and APIs as I make decisions about the platform I'm building. I really appreciate all the help! Feel free to comment below with more feedback, I'll appreciate this even more.

P.S
Chris Ricominni has a great blog post on how to introduce new technologies to an organization - for the more practical aspects.

Top comments (1)

Collapse
 
gklijs profile image
Gerard Klijs • Edited

Frontenders seem to like GraphQL a lot, your already looking into it. Most advanced GraphQL backends are also js unfortunately.
For JVM backends, Netflix DGS integrates nice with Apollo, and Spring GraphQL with the things The Guild is building.