AEC API
Backend-APIs
When I posted about coming up with the initial idea for AEC API, it was just a concept in my head. Since then, I've been heads-down actually building an MVP version and wanted to share the journey.
I knew I wanted to create a developer platform focused on authentication and security. So I started small - just the core login, register and token capabilities. No fancy dashboards or analytics yet.
Using Python and the FastAPI framework, I built out the initial REST APIs.
It's been an exhilarating experience bringing this from idea to reality. I learned a ton about APIs, OAuth 2.0, hashing passwords properly, JWTs, etc. The docs are sparse for now, but the platform actually works!
I still have a long way to go in terms of features, docs, stability, etc. But releasing this MVP feels like a major milestone. I'd love any feedback from the community on how I can improve and what capabilities to focus on next.
My goal is to build AEC API into a robustIdentity-as-a-Service platform like Auth0. It's ambitious but seeing the first version working has motivated me to keep pushing towards that vision. I welcome any and all advice!
As a cybersecurity enthusiast, I was exploring APIs and discovered endpoints and REST APIs that needed better security. This led me to OAuth 2.0 and JWT tokens, inspiring an idea - an API management platform with robust authentication built-in.
I wanted to turn this into a real company, so I came up with a name using my own - rearranging the letters of my name (A)LI (E)FE (C)AKICI formed AEC API.
My aim became designing a platform for developers to easily create secure back-end APIs, without dealing with complex authentication and other tools themselves.
This interest sparked the idea for AEC API - taking care of authentication complexities so developers can focus on core API functionality.
Comment