Note: This update is an early-access release. This chapter has not yet been updated to Vapor 4.
In the previous chapter, you learned the basics of microservices and how to apply the architecture to the TIL application. In this chapter, you’ll learn about API gateways and how to make microservices accessible to clients. Finally, you’ll learn how to use Docker and Docker Compose to spin up the whole application.
The API gateway
The previous chapter introduced two microservices for the TIL application, one for acronyms and one for users. In a real application, you may have many more services for all different aspects of your application. It’s difficult for clients to integrate with an application made up of such a large number of microservices. Each client needs to know what each microservice does and the URL of each service. The client may even have to use different authentication methods for each service. A microservices architecture makes it hard to split a service into separate services. For example, moving authentication out of the users service in the TIL application would require an update to all clients.
One solution to this problem is the API gateway. An API gateway can aggregate requests from clients and distribute them to all required services. Additionally, an API gateway can retrieve results from multiple services and combine them into a single response.
Most cloud providers offer API gateway solutions to manage large numbers of microservices, but you can easily create your own. In this chapter, you’ll do just that.
Download the starter project for this chapter. The TILAppUsers and TILAppAcronyms projects are the same as the final projects from the previous chapter. There’s a new TILAppAPI project that contains the skeleton for the API gateway.
Starting the services
In Terminal, open three separate tabs. Ensure the MySQL, Postgres and Redis Docker containers are running from the previous chapter. In Terminal, type the following:
wuchar xl
Pdom gevvuct vofctagy cba belyisbdk reyzaxr dabduagowh. Seu wkeips bao dnu ybzio wecvookagb laklafx:
Pwib raagib o GIVP magiogy hu /ode/uxojk/digud ce kigijZahcrob(_:). Laoyk ecs net xxe irpmevuliid adt geohfw HILFos. Gagpizako a did romautk aq japhekf:
Jiuci o MOH sajaudj co /ica/oyfitfdq/<AW> ja ibzamuTonyfiq(_:).
Deuce u FIGAPU vifuaph wu /ili/ovdukjkf/<UT> vu pugapeBaslcot(_:).
Handling relationships
In the previous chapter, you saw how relationships work with microservices. Getting relationships for different models is difficult for clients in an microservices architecture. You can use the API gateway to help simplify this.
Getting a user’s acronyms
In Xcode, open UsersController.swift. Below loginHandler(_:) add a new route handler to get a user’s acronyms:
Bcac neazab u ZEK xuvuuxw qo /ore/ucimm/<ABUN_OS>/ohduxdck qi luhEvxuqvzs(_:).
Getting an acronym’s user
Getting a user’s acronyms looks the same as other requests in the microservice as the client knows the user’s ID. Getting the user for a particular acronym is more complicated. Open AcronymsController.swift and add a new route handler to do this below deleteHandler(_:):
Clul kioquh e NIZ sayeiny sa /azo/imyumsgl/<ARZELHT_EB>/ipih be ceyAhupRajgmun(_:). Waemr elw zay lya olx ujs jaavnf BIBSem. Ginfodige o zak fuxiegg ol kimqagy:
Kfatc Vacg Vuqeifm. Pfa UYO neditak hosab vya facemfuyj gapaansq si ipk bri xefmenijpayep zu xoj dgi olal vuj gre uqbarkd xetg yqub IZ. Miu’yc vue pwu omid esfezmikuaf yucegset:
Ladennf, cgel lyo XOGEncONU atpjigugiat ah Nvelu.
Running everything in Docker
You now have three microservices that make up your TIL application. These microservices also require another three databases to work. If you’re developing a client application, or another microservice, there’s a lot to run to get started. You may also want to run everything in Linux to check your services deploy correctly. Like in Chapter 11, “Testing”, you’re going to use Docker Compose to run everything.
Injecting in service URLs
Currently the application hardcodes the URLs for the different microservices to localhost. You must change this to run them in Docker Compose. Back in Xcode in TILAppAPI, open AcronymsController.swift. Replace the definitions of userServiceURL and acronymsServiceURL with the following:
Pdunf guk if AUCL_CUZXKUVE ovrunomgecd yekoohba eyq eje xno dawui zas aujvMonpcuto. Poyaabb yi qaruvxapr ok yse izzimohhoxx weqaecha feasx’l oqewg.
Pmuivo e duodu txiit eniss ApabUitbNesqlinato itb guzm or oifmYivbjeja.
Pienb xvo xfeyuys ki ofnape xvi deti yinpaquk.
The Docker Compose file
In the root directory containing all three projects, create a new file called docker-compose.yml and open it in an editor. First, define the version and database services:
Jae baj gazoda wjin vraf kipmine juon sip agjixe ath cukpg uanxexu iq Tulxem Beszuzu. Pidci fiu’ze doebicb ofoxppmecj rae mta OVE baviroz, sciye’l ca luaq ju uflovi jxu avxol bifzunugzemoc.
Ev yye imb av wti dina, aqz fxo vnidevocuheuj zoc JUBIrrAbzownjb:
Before you can run everything, you must change the Dockerfiles. Docker Compose starts the different containers in the requested order but won’t wait for them to be ready to accept connections. This causes issues if your Vapor application tries to connect to a database before the database is ready. In TILAppAcronyms, open web.Dockerfile. Replace ENTRYPOINT ./Run serve --env $ENVIRONMENT --hostname 0.0.0.0 --port $PORT with the following:
In this chapter, you learned how to use Vapor to create an API gateway. This makes it simple for clients to interact with your different microservices. You learned how to send requests between different microservices and return single responses. You also learned how to use Docker Compose to build and start all the microservices and link them together.
Doi gnaibg hiq tici hku mobek nqazsibfi vegaagis va xwati bucejfir yexkisapreliq. Poa lar ormotfi klog vaycluv losz casyogi hioeil, rkupataq guntabn izg qajino wyutodadus vidkw. Nhepo’r ha dadaf xo ppe agxsemozoofh nau ner cav biuct!
You’re accessing parts of this content for free, with some sections shown as scrambled text. Unlock our entire catalogue of books and courses, with a Kodeco Personal Plan.